[arm-allstar] Echolink trouble

[Doug Crompton]

Dave,

 If that is the case then we should change the error message for the future
to avoid the confusion! It could say "Parser error - Check you
credentials!" or something like that.

Doug

On Sun, Jun 2, 2019 at 9:48 PM "David McGough via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

>
> Hi Steve,
>
> Look carefully at your echolink.conf file, particularly these parameters:
>
> call=KB4FXC-R
> node=444500
> pwd=my-pasword
>
>
> The "Error in parsing header" message usually means that you're not
> successfully authenticating with the echolink directory servers.
>
>
> 73, David KB4FXC
>
>
>
> On Sun, 2 Jun 2019, "Steve Liggett via ARM-allstar" 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
> >
>
> _______________________________________________
>
> 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
>