In Echolink.conf chance all the servers to the following they have been working great for me. This information is also in the Echolink website. server1=naeast.echolink.org server2=nasouth.echolink.org server3=servers.echolink.org server4=backup.echolink.org Vince VE3ELB On 2013-07-04, at 5:08 PM, Owen Campbell <owen.campbell@tanti.org.uk> wrote:
Hi,
I'm struggling with connection to Echolink. I can see similar problems have occurred to others on the list, but I can't see a solution identified.
My log contains:
[Jul 4 14:04:20] ERROR[2532] chan_echolink.c: Error in parsing header on server1.echolink.org [Jul 4 14:04:40] ERROR[2532] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [Jul 4 14:04:40] ERROR[2530] chan_echolink.c: connect() failed to connect to the Echolink server server2.echolink.org [Jul 4 14:04:40] ERROR[2532] chan_echolink.c: Unable to connect to directory server server2.echolink.org [Jul 4 14:05:00] ERROR[2532] chan_echolink.c: Error in parsing header on server3.echolink.org
UDP ports 5198 and 5199 are forwarded. TCP port 5200 is open and I can get a response via telnet from server1.echolink.org on 5200
Anyone any ideas?
Thanks,
Owen -- This email has been digitally signed. For further information, visit http://www.tanti.org.uk/index.php/blogs/owencampbell/3-tech/6-pgp
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users