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 <mailto:wadeo@charter.net>>
Date: Sun, December 22, 2013 3:39 pm
To: App_rpt-users@ohnosec.org <mailto: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 <mailto:App_rpt-users@ohnosec.org> ohnosec.org
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
it should be remembered that due to the architecture...starting up and logging in with your elink app and when the asterisk endpoint knows about it is not instantaneous if direct app to server connection, due to the fact the asterisk box only updates its list of auth'd endpoints every 10 minutes or so. try going thru a well-known proxy, they should be persistent.
and change the servers in the config file as below.
···
--
Bryan
Sent from my iPhone 5...small
keyboard, big fingers...please
forgive misspellings...
On Dec 22, 2013, at 19:28, Buddy Brannan <buddy@brannan.name> wrote:
I think server2 is the server that doesn’t work. Try this…it’s what’s in my echo link.conf file:
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
It will likely sync with one of the servers. Mine connects to server1 only,
and shows it is online at Echolink.org.
Bob
KK6ECM
···
-----Original Message-----
From: app_rpt-users-bounces@ohnosec.org
[mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Bryan D. Boyle
Sent: Sunday, December 22, 2013 4:40 PM
To: Buddy Brannan
Cc: App_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] EchoLink issue
it should be remembered that due to the architecture...starting up and
logging in with your elink app and when the asterisk endpoint knows about it
is not instantaneous if direct app to server connection, due to the fact the
asterisk box only updates its list of auth'd endpoints every 10 minutes or
so. try going thru a well-known proxy, they should be persistent.
and change the servers in the config file as below.
--
Bryan
Sent from my iPhone 5...small
keyboard, big fingers...please
forgive misspellings...
On Dec 22, 2013, at 19:28, Buddy Brannan <buddy@brannan.name> wrote:
I think server2 is the server that doesn't work. Try this.it's what's in
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
Leave us not forget how a year ago I was "blacklisted" by Echolink for using non-echolink software. First they blocked me for using tbd on a server here then another round of attitude over using app_rpt. I also run a deny everyone except list, had to include three of their callsigns in the list to make them happy again. I had been pulling what's left of my hair out trying to figure why I could not connect.
Now it has also happened as a result of what can only be "odd" routing with my dear friends at AT&T.
Also, yes a good time to chip in to support Jim's efforts here.
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
I was able to go back into my router and RE-enter all the port forwarding settings. This fixed my end of things and I can now get incoming connects, for now. As for my friend, he has a different router and has not had such luck. I will be heading over to his place in the next few days to see if I can resolve this in his router or not. Just for the record my servers are now listed as below:
Leave us not forget how a year ago I was "blacklisted" by Echolink for using non-echolink software. First they blocked me for using tbd on a server here then another round of attitude over using app_rpt. I also run a deny everyone except list, had to include three of their callsigns in the list to make them happy again. I had been pulling what's left of my hair out trying to figure why I could not connect.
Now it has also happened as a result of what can only be "odd" routing with my dear friends at AT&T.
Also, yes a good time to chip in to support Jim's efforts here.
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
I just wanted to get this information out there for future reference.
Original issue was no incoming echolink connections possible, outbound connections worked with no issue.
After adjusting many different items in the echolink.conf file and settings in the router, we finally did a complete reinstall. No luck. We decided to change computers, still no luck. With my friend ready to throw in the towel, a local guy who is pretty fluent in Linux finally found the issue.
Some file, i do not know what one yet, needed to be set to accept the ULAW audio codec. Then incoming connections worked perfect also. I don't know if this was something in the original configuration setup and downloaded or what it is. But it is some good information to have handy or think about if anyone experiences an issue with this in the future.
Thanks for all the help and suggestions along the way. They are very much appreciated!
Wade
KC0MLT
AllStar node 28757
···
On 12/23/2013 9:34 PM, wade wrote:
Ok for an update.
I was able to go back into my router and RE-enter all the port forwarding settings. This fixed my end of things and I can now get incoming connects, for now. As for my friend, he has a different router and has not had such luck. I will be heading over to his place in the next few days to see if I can resolve this in his router or not. Just for the record my servers are now listed as below:
Leave us not forget how a year ago I was "blacklisted" by Echolink for using non-echolink software. First they blocked me for using tbd on a server here then another round of attitude over using app_rpt. I also run a deny everyone except list, had to include three of their callsigns in the list to make them happy again. I had been pulling what's left of my hair out trying to figure why I could not connect.
Now it has also happened as a result of what can only be "odd" routing with my dear friends at AT&T.
Also, yes a good time to chip in to support Jim's efforts here.
On Dec 22, 2013, at 7:12 PM, wade <wadeo@charter.net> wrote:
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 ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org ohnosec.org