AllStar - Incoming/Outgoing EchoLink connections not possible
Hi All, after so many years (installed 2011) of using the AllStar system flawlessly, now the EchoLink side of it has stopped. I see this error when someone tries to connect... "Connected to Asterisk currently running on hub (pid = 2110) Verbosity is at least 3 [Oct 27 17:54:41] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:42] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:44] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:46] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139" I can't think of anything that has changed on my network, or router. AS node 28052 EL node 244279 ZS5PMB-R Is anyone able to assist please? We can even pay for your time if necessary. Teamviewer session? Shaun ZR5S
Yup, unable to connect via EL, but could through AS. Both AS and EL sites show you as registered. I'm wondering if something happened to your software load to get corrupted. I used to have that issue until I went with the RPi a couple of years ago. A reboot would often correct the issue. I later discovered a USB issue that caused asterisk to not be happy, and seemed to be corrupting my load. This is a mystery to me. The IP address below is reported as computer.amazonws.com. Does this make sense to you? Not seeing any connection with your issue, but curious. Bob k6ecm Sent from my iPhone
On Oct 27, 2017, at 9:52 AM, Shaun Rudling <shaun@pmbnet.co.za> wrote:
Hi All, after so many years (installed 2011) of using the AllStar system flawlessly, now the EchoLink side of it has stopped. I see this error when someone tries to connect... "Connected to Asterisk currently running on hub (pid = 2110) Verbosity is at least 3 [Oct 27 17:54:41] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:42] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:44] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:46] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139"
I can't think of anything that has changed on my network, or router. AS node 28052 EL node 244279 ZS5PMB-R
Is anyone able to assist please? We can even pay for your time if necessary. Teamviewer session?
Shaun ZR5S
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Thanks for your help, Bob. After a couple of reboots (about 6) it just started working again. Shaun ZR5S On 10/27/2017 19:33, Bob Pyke wrote:
Yup, unable to connect via EL, but could through AS. Both AS and EL sites show you as registered. I'm wondering if something happened to your software load to get corrupted. I used to have that issue until I went with the RPi a couple of years ago. A reboot would often correct the issue. I later discovered a USB issue that caused asterisk to not be happy, and seemed to be corrupting my load. This is a mystery to me.
The IP address below is reported as computer.amazonws.com <http://computer.amazonws.com>. Does this make sense to you? Not seeing any connection with your issue, but curious.
Bob k6ecm
Sent from my iPhone
On Oct 27, 2017, at 9:52 AM, Shaun Rudling <shaun@pmbnet.co.za <mailto:shaun@pmbnet.co.za>> wrote:
Hi All, after so many years (installed 2011) of using the AllStar system flawlessly, now the EchoLink side of it has stopped. I see this error when someone tries to connect... "Connected to Asterisk currently running on hub (pid = 2110) Verbosity is at least 3 [Oct 27 17:54:41] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:42] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:44] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139 [Oct 27 17:54:46] ERROR[2221]: chan_echolink.c:2578 do_new_call: Cannot find DB entry for IP addr 107.23.146.139"
I can't think of anything that has changed on my network, or router. AS node 28052 EL node 244279 ZS5PMB-R
Is anyone able to assist please? We can even pay for your time if necessary. Teamviewer session?
Shaun ZR5S
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org <mailto:App_rpt-users@lists.allstarlink.org> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Very good. It likely didn't require 6, but could easily required that much time to get reregistered with the server. Thanks, Bob K6ECM 73
On Oct 28, 2017, at 9:43 AM, Shaun Rudling <shaun@pmbnet.co.za> wrote:
244279
participants (2)
-
Bob Pyke -
Shaun Rudling