[arm-allstar] Echolink.conf

Sat Jan 16 11:16:25 EST 2021

This does happen however the simplest solution is this conf file. Delete
the current echolink.conf text entry and replace with the following. MAKE
SURE TO EDIT YOUR CREDENTIALS

[el0]
confmode=no
call=XXXXXX-R       ; Change this!
pwd=XXXXXXX         ; Change this!
name=Aaron Groover           ; Change this to your real name!
qth=Palmerton, PA    ; Change this to your actual QTH!
email=XXXXXX ; Change this!
maxstns=20
rtcptimeout=10
node=XXXXXX         ; Echolink node number - Change this!
recfile=/tmp/recorded.gsm
astnode=XXXXX       ; Change this to your active Allstar node number!
context=radio-secure
server1=server1.echolink.org
;server2=server5.echolink.org
server3=server3.echolink.org
server2=naeast.echolink.org
;nasouth.echolink.org
;servers.echolink.org
;backup.echolink.org
; Change following setting to your parameters
freq=446.1
tone=88.5
lat=40.223976
lon=-75.008529
power=20
height=50
gain=6
dir=0
;deny=
;permit=

On Sat, Jan 16, 2021 at 11:09 AM "John Morandi via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> My server list looks like this:
>
> server1=server2.echolink.org
> server2=server3.echolink.org
> server3=server6.echolink.org
>
> This is taken right out of our echolink.conf file and ours is currently
> working fine.
>
> - NI4JM
>
>
> On 1/16/21 7:31 AM, "Anthony (N2KI) via ARM-allstar" wrote:
> > 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
> >>
> > _______________________________________________
> >
> > 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
> _______________________________________________
>
> 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
>

-- 
Thank You,

Aaron Groover
(610) 379-6148
W3NTT.repeater at gmail.com
www.KC3PMB.club