[arm-allstar] I haven't seen this echolink error before...

[Mr. Possum (Bill)]

I have five servers configured in my /etc/asterisk/echolink.conf file.
server1=naeast.echolink.org
server2=nawest.echolink.org
server3=servers.echolink.org
server4=backup.echolink.org
server5=nasouth.echolink.org
And yeah, over the years I have noticed that they aren't always accessible...  But this recent view of it is a bit more than what I was used to...
Bill - N5MBM



      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
 To: ARM Allstar <arm-allstar at hamvoip.org> 
Cc: Doug Crompton <wa3dsp at gmail.com>
 Sent: Friday, February 2, 2018 9:08 AM
 Subject: Re: [arm-allstar] I haven't seen this echolink error before...
   
I believe the echolink app requires a minimum of three servers defined in the echolink.conf file or it will not run. The servers are screwy and some do not work or do not work all the time. In some cases you have to define one that does not work. It really does not matter as long as one server gets it errors can be ignored.

73 Doug
WA3DSP
http://www.crompton.com/ hamradio


On Fri, Feb 2, 2018 at 9:11 AM, "Mr. Possum (Bill) via arm-allstar" <arm-allstar at hamvoip.org> wrote:

I have something that just started...  Sort of out of the blue...  When I sit in a terminal session, watching the Asterisk CLI I keep getting these messages scrolling across my screen...
[Feb  2 08:05:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org
    -- Received OK from Echolink server naeast.echolink.org
[Feb  2 08:05:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
[Feb  2 08:06:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org
    -- Received OK from Echolink server servers.echolink.org
[Feb  2 08:06:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org
  == Refreshing DNS lookups.
    -- Received OK from Echolink server naeast.echolink.org
[Feb  2 08:06:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
[Feb  2 08:07:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org
RP1*CLI>

I hadn't noticed this before the last update...  I don't know if it has anything to do with an update...  I just started noticing it because I had an occasion to watch it happening while connected to the node in a terminal session - for hours.

Anyone else see this recently or have this problem?  Or is it just a recent problem with echolink.org?
Thanks,
Bill - N5MBM


______________________________ _________________

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 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 web page - http://hamvoip.org

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180202/380444e9/attachment.html>