[arm-allstar] Echolink ?
wa3dsp at gmail.com
Sat Sep 16 09:25:02 EST 2017
Echolink woes were addressed several months ago in the V1.5 code. There
were significant problems that were fixed. I have seen no problems here on
echolink since that time, certainly nothing needing a daily reboot. My hub
has regular echolink logins and uptimes of up to several months.
If you are not running V1.5 or have not updated recently or you are using
some other version of Allstar you could certainly have echolink problems
especially with echolink updates causing crashes.
Echolink requires that three servers be defined but they are not all always
reachable. In fact some are never reachable. The bottom line is do you have
a database downloaded? You can view the entire database or check individual
entries in the Asterisk client.
There is an echolink howto on the hamvoip.org web page.
On Sat, Sep 16, 2017 at 9:41 AM, "John Huggins via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Our deployment of Allstar/HAMVOIP gets into this Echolink funk from time to
> time requiring a restart of Asterisk. Right now we just reboot the whole
> thing every morning at 3 am. No, this is not an elegant solution at all,
> but good enough given the secondary nature of HAMVOIP to our primary
> repeater controller.
> John, kx4o
> On Sat, Sep 16, 2017 at 5:03 AM, "Bob via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
> > Hi Guys
> > Anyone having problems with Echolink ?? My system which use to work fine
> > is now not allowing inbound or outbound connections
> > There has been no changes to routing or network settings ?
> > 73
> > Bob
> > VK6ZGN
> > _______________________________________________
> > 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
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the arm-allstar