[arm-allstar] Echolink Error Code

Mon Jul 18 11:51:39 EST 2016

Thanks for the update, Doug. Hadn't considered the ping being turned off.

I've run out of troubleshooting time for today - got to make my way across
the state for a medical appointment. Dave isn't on the list yet, so I've
forwarded your email to him so he can compare echolink.conf files. I've
looked at it so many times that I probably won't see an error anyway
<grin>. I did not realize that there could be different passwords for -L
and -R. That's the first thing to check. I'm depending on Dave for that
information.

We had to wrestle with his router to get it to reserve a certain IP for the
Allstar Node. After several node reboots, that seems to be working OK. The
router is an Apple Airport Extreme.

BTW, I had the same issue with Echolink not loading until I changed the
delay value in /usr/local/etc/allstar.env

It certainly increases what was a speedy boot time, but Echolink seems to
load without error now on my node. Oh, and in both cases (K5FOY's node and
mine), we have actived the alpha-test version in the 1.02 code using your
instructions from RPi2/3 version 1.02 Install Notes.

Thanks for the help!

John

On Mon, Jul 18, 2016 at 11:12 AM, Doug Crompton via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> John,
>
>  I forgot they must have ping turned off on their servers which is stupid
> from a troubleshooting point of view.
>
> So the fact that you are not getting ping returns is not necessarily an
> indication of a problem.
>
> Assuming you are using the same call and password you used with the IRLP
> node and it worked there then those should be correct. If you are using -L
> or -R then those can have different passwords for the same call. CALL-L or
> CALL-R are uppercase.
>
> Here is a copy of my echolink.conf with password removed. Make sure your
> echolink node number matches the echolink call from the echolink database.
> Also their servers are screwy. Some work some do not. You MUST have three
> defined whether any one works or not.
>
> [el0]
> confmode=no
> call=WA3DSP-L       ; Change this!
> pwd=xxxxxxx          ; Change this!
> name=Doug           ; Change this to your real name!
> qth=Richboro, PA    ; Change this to your actual QTH!
> email=doug at crompton.com ; Change this!
> maxstns=20
> rtcptimeout=10
> node=147090         ; Echolink node number - Change this!
> recfile=/tmp/recorded.gsm
> astnode=40561       ; 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=
>
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Mon, 18 Jul 2016 09:50:22 -0500
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink Error Code
> From: arm-allstar at hamvoip.org
> CC: wb5nfc at gmail.com
>
> Doug,
>
> "I am assuming you have the Echolink port forwarding set up?"
> Yes. Set up, router rebooted, entries deleted then added again and
> rebooted.
>
> "Did this node ever work on Echolink?"
> Yes. Dave M. (K5FOY) also has an IRLP/Echolink node. IRLP/Echolink node
> disabled, ports to IRLP/Echolink disabled and re-entered in the router for
> Allstar/Echolink. Router restarted.
>
> "Did you test it before you deployed it?"
> Not really. Dave downloaded the image, I helped him configure it
> (remotely), we got Allstar working, then started on Echolink. Got stumped
> when it didn't load, changed the delay and Echolink appears to load but
> will not parse database.
>
> "If not perhaps your config file is not setup correctly - password etc."
> Dave has entered and re-entered password and node numbers, but no go.
>
> "Is there any other Echolink running at this site?" No. IRLP/Echolink node
> shut down (and ports sent to Allstar/Echolink).
>
>
> *"Can you ping reliably the Echolink servers from the site?" *
> *Aha....ping returns the echolink server IP but NOTHING else. None of the
> hops appear. *
>
> John
>
> On Mon, Jul 18, 2016 at 9:32 AM, Doug Crompton via arm-allstar <
> arm-allstar at hamvoip.org> wrote:
>
> John,
>
>  I am assuming you have the Echolink port forwarding set up? Did this node
> ever work on Echolink? Did you test it before you deployed it?  If not
> perhaps your config file is not setup correctly - password etc. Is there
> any other Echolink running at this site? Can you ping reliably the Echolink
> servers from the site?
>
> If setup correctly Echolink should just work. There is a possibility you
> have a bad image load but that is not likely.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Mon, 18 Jul 2016 09:01:47 -0500
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink Error Code
> From: arm-allstar at hamvoip.org
> CC: wb5nfc at gmail.com
>
> Doug,
>
> The delayed start suggestion came from an earlier arm-allstar thread I dug
> up looking for clues and previous suggestions. (The thread starts here:)
> http://lists.hamvoip.org/pipermail/arm-allstar/2016-June/003279.html
>
> The echolink dbdump command produces no output, so I'm guessing there's no
> database to read. After running all night, the same errors are popping up
> on the node this morning. We have rebooted several times just to be sure
> there wasn't a temporary glitch. I'm across the state from the node we're
> trying to bring up, but I have remote access (and we've been using
> TeamViewer to share our desktop for some of the troubleshooting). The Pi3
> is on WiFi.
>
> John
>
> John
>
> --------
>
> Doug Crompton via arm-allstar
> 10:34 PM (9 hours ago)
> to Doug
> John,
>
>  I guess the big question is are you getting the database? Sometimes these
> errors are short term due to Internet or actual source database problems.
>
> In the client do -
>
> echolink dbdump
>
> or better yet at the Linux prompt -
>
> asterisk -rx "echolink dbdump" > /tmp/echo.txt
>
> Then look through the file and see how it looks -
>
> less /tmp/echo.txt
>
> Also in the client look up a known call or node -
>
> CLI> echolink dbget c WA3DSP-L
> 147090|WA3DSP-L|73.30.112.57
>
> wa3dsp-27225-hub*CLI> echolink dbget n 147090
> 147090|WA3DSP-L|73.30.112.57
>
> If that looks good then things should be OK. If you continually see these
> errors for days on end then maybe we need to dig further. Nothing has been
> changed in the Echolink code and it does work.
>
> The fact that you need to delay in the boot indicates a possible Internet
> problem. I have never had a situation where a delay was needed for an
> RPi2/3. That delay was primarily for the Beaglebone Black.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
> On Sun, Jul 17, 2016 at 7:05 PM, John <wb5nfc at gmail.com> wrote:
>
> I'm helping a friend configure his new RPi3 Allstar node. We're using the
> most current build for the Pi3 and have Allstar functions working properly.
> Initially, Echolink was not loading, but upon changing the load time to 30
> in the allstar.env file, Echolink now loads at boot, but with "Error in
> parsing header" errors:
>
>     -- Received OK from Echolink server server3.echolink.org
> [Jul 17 18:55:24] ERROR[295]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server3.echolink.org
>
>     -- Received OK from Echolink server server1.echolink.org
> [Jul 17 18:55:43] ERROR[295]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server1.echolink.org
>
> Any thoughts on how to troubleshoot this error will be greatly appreciated.
>
> John / WB5NFC
>
>
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB and RPi2 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 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 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 web page - http://hamvoip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160718/2e5fe2ea/attachment.html>