Hello Eric, I did not see anyone answer you, I had this problem as well. you need to update your echolink.conf file I put these servers in and remove the ones you have now. server1=naeast.echolink.org server2=nasouth.echolink.org server3=servers.echolink.org The default servers don't resolve correctly and you should point at the ones closest to you, You can also get away with using only the closest one to you which would keep down on the traffic I think. NA east is the closest server to us. Hope this helps. Craig VA3DTF Node Master for VE3WOM-L (allstar) & Echolink VE3WOM-R Echolink & IRLP 2255 ----- Original Message ----- From: Eric Meth To: App_rpt-users at qrvc.com Sent: Sunday, June 20, 2010 10:27 PM Subject: Problems running Echolink I operate 3 app-rpt nodes, 2344, 2425 and 2579 Node 2344 has the following problem on echolink, from the /var/log/asterisk/messages log [Jun 20 19:16:07] NOTICE[11013] chan_echolink.c: Received OK from Echolink server server2.echolink.org [Jun 20 19:16:07] ERROR[11013] chan_echolink.c: Error in parsing header on server2.echolink.org [Jun 20 19:16:27] NOTICE[11013] chan_echolink.c: Received OK from Echolink server server3.echolink.org [Jun 20 19:16:27] ERROR[11013] chan_echolink.c: Error in parsing header on server3.echolink.org Anyone able help debug this problem? Eric Meth - ve3ei