I am still having the issue. Very specifically it reads:
ERROR[4275]: chan_echolink.c:2393 do_el_directory: Error in parsing header on server1.echolink.org
So, looking in the code for chan_echolink.c at the specific line 2393 it looks like the information gets downloaded, then it performs some check on the information received and exits if there is an error.
I have no idea what has changed to make my machine thrown an error...
Is there someone good with asterisk and or echolink that can tell me what the error is looking for so I can start looking at what my system is doing?
Or, has there been a recent change with the echolink directory servers that have somehow changed the way the data comes in?
I can tell you that my echolink station registers and shows up in the directory, so most of the echolink channel is working.
WL7NI
Mark
I experimented and find that these seems to work, though there frequently seems to be one of the servers not working. But it has been this way since I started with this a couple of years ago.GeorgeCW2DB 2360,2428, 28599----- Original Message -----From: Mark HuelskoetterSent: Friday, July 06, 2012 12:13 AMSubject: [App_rpt-users] Echolink issues?So, I maintain node 27597 which is the connection to IRLP reflector 9070. For no apparent reason I am now getting the :"Error in parsing header on nawest.echolink.org"Error. I have the servers set to nawest, nasouth and naeast. Same error on all three servers. Anyone else having problems parsing echolink headers?Thanks in advance.WL7NIMark