[arm-allstar] Echolink trouble

Doug Crompton wa3dsp at gmail.com
Sun Jun 2 21:51:10 EDT 2019


Steve,

 Nothing has been changed in Echolink that would make it not work. It is
working for others which leads me to believe it is an issue at your end.
The server 5 reject is not a problem. You need three servers defined in the
config and only one has to work, Why you would be getting the parsing error
I am not sure. I know you have rebooted.  Is it possible that something has
gotten corrupted in your current build? Have you tried running it on other
servers on your LAN? It looks like it is trying to build a database but not
being successful. I know you have a good Internet connection there so I
doubt that is the problem.


*73 Doug*

*WA3DSP*

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


On Sun, Jun 2, 2019 at 9:43 PM "Steve Liggett via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I have been having trouble getting Echlin to work on the HAMVOIP build. It
> was rock stable for years and now is not functional.
>
> I have looked at the echo link.conf file and it seems correct. I even
> started over with the .xxx file and filled in the usual information.
>
> In the CLI, I get these sorts of messages
>
> [Jun  2 20:46:00] ERROR[366]: chan_echolink.c:1946 sendcmd: connect()
> failed to connect to the Echolink server server5.echolink.org
> [Jun  2 20:46:00] ERROR[364]: chan_echolink.c:1946 sendcmd: connect()
> failed to connect to the Echolink server server5.echolink.org
> [Jun  2 20:48:13] ERROR[366]: chan_echolink.c:2130 do_el_directory: Unable
> to connect to directory server server5.echolink.org
> [Jun  2 20:48:23] ERROR[366]: chan_echolink.c:2199 do_el_directory: Error
> in parsing header on server3.echolink.org
>   == Refreshing DNS lookups.
>   == Refreshing DNS lookups.
> [Jun  2 20:48:42] ERROR[366]: chan_echolink.c:2199 do_el_directory: Error
> in parsing header on server1.echolink.org
> [Jun  2 20:48:49] ERROR[364]: chan_echolink.c:1946 sendcmd: connect()
> failed to connect to the Echolink server server5.echolink.org <
> http://server5.echolink.org/>
>
> If I do echolink dbdump, I get nothing back (no error message or anything)
> such as here:
>
> W3YT*CLI> echolink dbdump
> W3YT*CLI>
>
> Ports are forwarded as usual. Any help would be appreciated. I will be
> doing some traveling this summer and would like to take advantage of all
> ways to get to my repeater.
>
> steve
> W3RX
>
> Allstar 28325
> echolink 86768
>
>
> _______________________________________________
>
> 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
>


More information about the ARM-allstar mailing list