<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_1_1517536090477_69975">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...</div><div id="yui_3_16_0_1_1517536090477_69976"><br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69977">[Feb 2 08:05:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org<br id="yui_3_16_0_1_1517536090477_69928"> -- Received OK from Echolink server naeast.echolink.org<br id="yui_3_16_0_1_1517536090477_69929">[Feb 2 08:05:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org<br id="yui_3_16_0_1_1517536090477_69930"> -- Received OK from Echolink server nawest.echolink.org<br id="yui_3_16_0_1_1517536090477_69931">[Feb 2 08:06:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org<br id="yui_3_16_0_1_1517536090477_69932"> -- Received OK from Echolink server servers.echolink.org<br id="yui_3_16_0_1_1517536090477_69933">[Feb 2 08:06:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org<br id="yui_3_16_0_1_1517536090477_69934"> == Refreshing DNS lookups.<br id="yui_3_16_0_1_1517536090477_69935"> -- Received OK from Echolink server naeast.echolink.org<br id="yui_3_16_0_1_1517536090477_69936">[Feb 2 08:06:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org<br id="yui_3_16_0_1_1517536090477_69937"> -- Received OK from Echolink server nawest.echolink.org<br id="yui_3_16_0_1_1517536090477_69938"> -- Received OK from Echolink server nawest.echolink.org<br id="yui_3_16_0_1_1517536090477_69939">[Feb 2 08:07:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org<br id="yui_3_16_0_1_1517536090477_69940">RP1*CLI><br id="yui_3_16_0_1_1517536090477_69941"></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69983"><br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69984">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.<br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69985"><br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69986">Anyone else see this recently or have this problem? Or is it just a recent problem with echolink.org?</div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69987"><br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69988">Thanks,</div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69989"><br></div><div dir="ltr" id="yui_3_16_0_1_1517536090477_69990">Bill - N5MBM<br></div><div id="yui_3_16_0_1_1517536090477_69991"><br></div></div></body></html>