[arm-allstar] Echolink Validation Difficulties

[Patrick Perdue]

Usually, that error is due to a bad password, or sometimes a server problem.

Something of interest:

nasouth.echolink.org, naeast.echolink.org and maybe others all point to 
server3.echolink.org. There is probably some legacy stuff going on 
there, and it was changed at the DNS level to keep compatibility with 
old configs.

My working configuration's servers look like this, but they all go to 
the same place, really.


server1=nasouth.echolink.org
server2=naeast.echolink.org
server3=server3.echolink.org


I have occasionally seen things break with a different order of servers, 
even though it shouldn't matter, but the first thing I'd check is the 
password for NO1D-R.


I'm not sure if all the servers are supposed to respond to ping. server3 
does, server6, I.E. nawest.echolink.org, doesn't, and neither does 
servers.echolink.org, from either of the two valid addresses in it's A 
record. It also has another address: 3.120.159.0. I've never seen an A 
record with a 0 at the end. This is usually used to identify an entire 
network, so I'm not sure what's going on there.

servers.echolink.org points to server1 and server6, neither of which 
respond to pings, but this may be by design. I'm not sure.


On 3/27/2023 10:32 PM, Doug Theriault via ARM-allstar wrote:
> I am attempting to configure echolink on an allstar node connected to Yaesu
> repeater.  My callsign was validated in 2016, NO1D.  Echolink provides
> self-validation for -L and/or -R nodes.  I am attempting to validate NO1D-R
> on this controller.
>
> I get to a step where echolink.org wants me to perform a PINGTEST against
> the node.  I see the request coming in:
>
> [Mar 27 18:50:50] NOTICE[16303] chan_echolink.c: Cannot find DB entry for
> Callsign: *PINGTEST*. Requesting DB update.
>
> Log also contains lots of:
>
> [Mar 27 18:53:31] ERROR[16304] chan_echolink.c: Error in parsing header on
> naeast.echolink.org
> [Mar 27 18:53:51] ERROR[16304] chan_echolink.c: Error in parsing header on
> nawest.echolink.org
> [Mar 27 18:54:11] ERROR[16304] chan_echolink.c: Error in parsing header on
> servers.echolink.org
>
> I attempted to dump the Database from the Asterisk CLI,  but there are no
> entries.
>
> I logged a trouble ticket with Echolink.org however they indicated their
> servers are returning the correct response and the issue is on my node.
>
> My echolink.conf:   Yes, password is obfusticated and I left node# blank
> [el0]
> confmode=no
> call=NO1D-R
> pwd=######
> name=Doug
> qth=Prescott Valley, AZ
> email=no1d.doug at gmail.com
> maxstns=20
> rtcptimeout=10
> node=
> recfile=/tmp/recorded.gsm
> astnode=460042
> context=radio-secure
> server1=naeast.echolink.org
> server2=nawest.echolink.org
> server3=servers.echolink.org
>
> Has anyone run into this issue?
>
> Chicken/egg problem perhaps? Echolink cannot issue a node number to NO1D-R
> until the call is validated via a PINGTEST, however without the node number
> in the .conf file I never receive the database download containing the
> PINGTEST entry.
>