[arm-allstar] Echolink Validation Difficulties

[Doug Theriault]

Thank you David and Patrick.

I installed Echolink client on my Linux machine, configured and sure enough
PINGTEST for NO1D-R worked.  This brought me to the next page on the
echolink.org validation site.

I shutdown the Linux client, back to the Allstar node, PINGTEST still
failed.

Patrick mentioned password so back to the desktop client, forced a change
of password, PINGTEST again passed.  Back to Allstar, updated password in
.conf, PINGTEST now works fine.

Unclear what exactly resulted in the fix, however your suggestions helped
me solve the issue.


On Mon, Mar 27, 2023 at 8:52 PM David McGough <kb4fxc at inttek.net> wrote:

>
> Hi Doug,
>
> I've always validated the -L and -R echolink nodes using the echolink
> windows software.  Then, once I've got the node number, migrating the
> config to chan_echolink.  This approach is easy to do....There likely is
> some way to pull this off strictly using chan_echolink, but I never needed
> too.
>
>
> 73, David K4FXC
>
>
> On Mon, 27 Mar 2023, 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.
> >
> >
>
>

-- 
73
NO1D - Doug