[arm-allstar] Echolink Error Code

[Doug Crompton]

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 Doug
WA3DSP
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-allstar10:34 PM (9 hours ago)to DougJohn,

 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 Doug
WA3DSP
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 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160718/3498d75d/attachment-0001.html>