[arm-allstar] Question to those using Echolink

[Neil Mooney]

Thank you Doug, I'll have a read

Regards,

Neil
________________________________
From: arm-allstar <arm-allstar-bounces at hamvoip.org> on behalf of "Doug Crompton via arm-allstar" <arm-allstar at hamvoip.org>
Sent: 05 March 2018 05:26
To: ARM Allstar
Cc: Doug Crompton
Subject: Re: [arm-allstar] Question to those using Echolink

Neil,

 An update to the code last year allows the creation of specific courtesy
tones based on the node that is connected. So for instance you could make
the Echolink node give the morse character E or EC, some programmable tone,
or even voice. This is a particularly nice feature that tells local user
where something is coming from. In the case of a repeater you could
identify remote links to the repeater, etc.

See the howto on this at the hamvoip.org web page.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*



On Sun, Mar 4, 2018 at 3:23 PM, "Neil Mooney via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi Doug,
>
> In reply to your suggestion about having echolink on its own node that you
> connect to whichever node you want echolink access on.  I do that on a hub
> node but if I do it on my repeater the users will always think the repeater
> is linked to other nodes from the courtesy tones they hear. That is the way
> I've told people they can tell if the repeater is in standalone mode or
> linked. Is it possible for my repeater to use unlinked courtesy tones if
> only a certain node is connected?
>
> Regards,
>
> Neil
> ________________________________
> From: arm-allstar <arm-allstar-bounces at hamvoip.org> on behalf of "Doug
> Crompton via arm-allstar" <arm-allstar at hamvoip.org>
> Sent: 01 March 2018 05:44
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] Question to those using Echolink
>
> Thank you all for your input on Echolink. The hangup issues need to be
> addressed at some point as there are no settable timers to avoid this in
> our end of Echolink. This is a user error leaving PTT on and for now at
> least proper education is the best fix or if someone continues to do it
> when you give them a warning they can be denied from your Echolink in the
> config file.
>
> It is also a good idea to run Echolink on a node by itself that is in
> pseudo mode. This way you can easily isolate it from other nodes if need
> be. It also allows you the flexibility to connect it to any node you may
> have.
>
> You also have to remember that Echolink is not as reliable as Allstar and
> since it has no permanent connect feature if you lose a connection it will
> not come back and would have to be re-established.
>
> We will continue to address any issues in Echolink but they will generally
> depending on severity have less priority than Allstar issues.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
> On Wed, Feb 28, 2018 at 8:13 PM, "Vince Buono via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Doug,
> >
> > I have not had any incoming or outgoing issues with EchoLink/Hamvoip
> > AllStar.
> >
> > Additionally, the new version of the iPhone EchoLink app that was
> released
> > last week seems to be even more stable than previous versions.
> >
> > 73, Vince
> > WA3ADI
> >
> > > On Feb 28, 2018, at 6:44 PM, Neil Mooney via arm-allstar <
> > arm-allstar at hamvoip.org> wrote:
> > >
> > > I've also had the lock up in TX issue a few times on two different
> nodes
> > on different RPi's and different ISP's. When they lock up it's impossible
> > to disconnect using Allmon or DTMF and the only way I've found to unlock
> > the node is a RPi restart.
> > >
> > > One of the nodes radioless with echolink that I connect to another node
> > to give Echolink connectivity. The other is a repeater which sat in TX
> for
> > a few hours. When things are going good Echolink works really well. I
> think
> > the issue might be a poor internet connection on the remote user who
> loses
> > connection while he/she was talking but I've never been able to prove
> that.
> > >
> > > Unfortunately, I've had to disable Echolink on the repeater as I can't
> > have it locking the radio in TX.
> > >
> > > Regards,
> > >
> > > Neil
> > >
> > >
> > > Regards,
> > >
> > > Neil
> > > ________________________________
> > > From: arm-allstar <arm-allstar-bounces at hamvoip.org> on behalf of "Doug
> > Crompton via arm-allstar" <arm-allstar at hamvoip.org>
> > > Sent: 28 February 2018 20:55
> > > To: ARM Allstar
> > > Cc: Doug Crompton
> > > Subject: [arm-allstar] Question to those using Echolink
> > >
> > > Awhile back in early 2017 we fixed some significant long standing bugs
> in
> > > Echolink that had been causing crashes. I am curious if anyone that is
> > > using Echolink with hamvoip Allstar has experienced any problems since
> > > then. I cannot say I use Echolink extensively but I have not seen any
> > > issues here and so far in the last 9 months or more only one person has
> > > recently reported a problem that his system is crashing which we cannot
> > > reproduce. While this could be due to many other factors we would like
> to
> > > get any input from others that might shed some light on this. I am not
> > > talking about connectivity or setup issues but rather things like
> crashes
> > > that actually cause an Asterisk restart.
> > >
> > > Echolink in general is secondary to Allstar and there as a convenience.
> > We
> > > have no control over the Echolink system in general so it is what it is
> > in
> > > both audio quality and reliability but it is a useful tool to reach
> those
> > > not on Allstar or away from their Allstar systems.
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org