[arm-allstar] ERROR[403] chan_echolink.c:

[Doug Crompton]

Mike,

 Yes that is correct. We had a discussion about this last week. There must
be three servers defined in echolink.conf but only one has to actually
work. Server5 has been down for awhile now.  You can use server1, 2, and 3
and that message will go away. That is as long as all of those are working.
But the bottom line is that as long as one is working and you are getting
the data from it all is fine.  You can check that in the client with  -
echolink dgdump or dbget.


*73 Doug*

*WA3DSP*

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

On Sat, Jun 15, 2019 at 11:47 AM "Mike Besemer via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Been receiving the error below for several days in AST Log.  Echolink works
> fine, so I'm assuming that this is just an issue with a specific Echolink
> server being unavailable; is that correct?
>
> "ERROR[403] chan_echolink.c: connect() failed to connect to the Echolink
> server server5.echolink.org"
>
> 73,
>
> Mike
> WM4B
>
>
>
> _______________________________________________
>
> 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
>