[arm-allstar] Echolink.conf

[Anthony (N2KI)]

Bryan, et al

I am not sure that the IP being blocked is the issue, since I am able to
connect using the Echolink software from the same WAN IP address.

What are the current server addresses for echolink?  I have found a few
different iterations of what they are.  Currently, I am using

server1=nasouth.echolink.org
server2=naeast.echolink.org
server3=servers.echolink.org
server4=backup.echolink.org

The end result is this in my AST log.

[Jan 15 23:22:47] ERROR[347] chan_echolink.c: Error in parsing header
on nasouth.echolink.org
[Jan 15 23:23:07] ERROR[347] chan_echolink.c: Error in parsing header
on naeast.echolink.org
[Jan 15 23:23:26] ERROR[347] chan_echolink.c: Error in parsing header
on servers.echolink.org
[Jan 15 23:23:46] ERROR[347] chan_echolink.c: Error in parsing header
on nasouth.echolink.org
[Jan 15 23:24:06] ERROR[347] chan_echolink.c: Error in parsing header
on naeast.echolink.org
[Jan 15 23:24:27] ERROR[347] chan_echolink.c: Error in parsing header
on servers.echolink.org
[Jan 15 23:24:47] ERROR[347] chan_echolink.c: Error in parsing header
on nasouth.echolink.org
[Jan 15 23:25:07] ERROR[347] chan_echolink.c: Error in parsing header
on naeast.echolink.org
[Jan 15 23:25:26] ERROR[347] chan_echolink.c: Error in parsing header
on servers.echolink.org
[Jan 15 23:25:47] ERROR[347] chan_echolink.c: Error in parsing header
on nasouth.echolink.org
[Jan 15 23:26:07] ERROR[347] chan_echolink.c: Error in parsing header
on naeast.echolink.org
[Jan 15 23:26:27] ERROR[347] chan_echolink.c: Error in parsing header
on servers.echolink.org

I verified that N2KI, N2KI-L and N2KI-R are authenticated on the Echolink
site.  All of the call iterations yield the same result.  This happened
after I did a hamvoip update to the latest version.


Regards,

Anthony (N2KI)









On Sat, Jan 16, 2021 at 12:03 AM "Bryan St Clair via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I have noticed that Echolink blocks an IP for short periods of time.  If
> you logged in too many times, I suspect they block you.
>
> Of course, if you use multiple logins, I have been blocked as well.
>
> Just my observations.   How long have you been trying to log in after this
> update?
>
> On Fri, Jan 15, 2021 at 6:57 PM "Anthony (N2KI) via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I did a system update and it seems that I now can not connect to the
> > echolink servers.  I have done everything I could think of including
> > rebuilding the echolink.conf file from the template.  I still can not
> > connect to echolink.  All of the station data, password and power,
> height,
> > etc stuff is correct and uncommented where appropriate.  Router port
> > forwarding is checked and correct.
> >
> > Can someone help me troubleshoot why this has suddenly stopped working?
> >
> > Thanks!
> >
> > Regards,
> >
> > Anthony (N2KI)
> > _______________________________________________
> >
> > 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/4 web page - http://hamvoip.org
> >
>
>
> --
> Bryan
> K6CBR
> bryan at k6cbr.us
> 43918,439910
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>