The ports are forwarding to the correct IP address. There is only one connection per location for echolink.  All was working properly the first day, then the second day came and no inbound connections are possible. We can also no longer get in from our Android phones.

Thi is the message my friend gets.

ERROR [2306] chan_echolink.c: connect{} failed to connect to the echolink server server2.echolink.org

Hope this can help diagnose what going on here..

Wade
KC0MLT


On 12/22/2013 2:46 PM, mike@midnighteng.com wrote:

one thing to check...
incoming and outgoing routes in your router udp ports for echolink and allstar

then know that

echolink only allows one connection per ip address.

Hope that leads you somewhere if you have not found it.

...mike/kb8jnm


-------- Original Message --------
Subject: [App_rpt-users] EchoLink issue
From: wade <wadeo@charter.net>
Date: Sun, December 22, 2013 3:39 pm
To: App_rpt-users@ohnosec.org

Hello all,

I recently helped a friend here in town to setup his first AllStar node.
After getting everything up and running including the echolink part the
next day it stopped allowing incoming connections. After doing some
investigation mine has also stopped allowing incoming connections. Both
of ours can connect out from our nodes but no one can connect in. On my
node it comeback with a simple time out message, on his node it comes
back with unauthorized. Has anyone had this issue before and if so what
was the fix?

Our routers have all the appropriate port forwarding settings in them
and have since the echolink on windows days. This is just a very strange
occurrence to me that both of us have this problem and get two different
messages back to other users. Any help would be greatly appreciated!

Thanks
Wade
KC0MLT

AllStar node 28757
Echolink node number 223846

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users