[arm-allstar] Echolink Error

[John]

Thanks, Doug. Good info to remember.Yes, all ports forwarded. Problem may
have been with Allstar portal Echolink configuration. Still playing with
setup. Got a lot of great help tonight from Dave on some config tweaks. The
major hurtle cleared this weekend was figuring out the proper configuration
of Wifi hotspot and router. My system does not work and play well together
when tethered. I changed from tether mode to wifi connection. With a little
tweaking, things started falling into place. I may have had a static IP
configuration problem from my Internet provider as well. They won't admit
to anything, but after a trouble call, things started working.

It should be noted that all of the problems I have experienced have either
been configuration problems I created or network configuration problems
specific to my nomadic lifestyle. Everything about the Beaglebone has been
rock solid. Great job! To all on the list: many thanks for sharing your
expertise and your willingness to help.

John


On Sun, Aug 3, 2014 at 9:14 PM, Doug Crompton <doug at crompton.com> wrote:

> John,
>
> I assume you have renamed and setup the echolink.conf file in
> /etc/asterisk and you have the echolink udp ports directed to the BBB ip
> address in your router? That is really all you have to do.
>
> One thing to remember when using a cell phone. If you are using wireless
> and you are wireless to your own router you will be using the private lan
> IP address to BBB. If you are using the cell network or wireless outside of
> your local router for Internet then you have to use your public IP address
> or domain name.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Sun, 3 Aug 2014 17:12:07 -0500
> From: wb5nfc at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] Echolink Error
>
>
> Getting closer to having a working node thanks to the help of many on this
> list and hams not directly involved with the BBB (yet). Outbound seems to
> be working OK, but I still have kinks to work out on incoming connections.
>
> When an Echolink station attempts to connect to my node, they time out. On
> an iPhone, the message is: Connect Failed. Cannot connect to WB5NFC-L
> UNAUTHORIZED. If I watch the CLI during the incoming call attempt, I see
> repeated ERROR[410]: chan_echolink.c:2578 do_new_call: Cannot find DB
> entry for IP addr 10.159.66.1.10.159.66.1 is the internal IP of my router
> rather than my external, static IP.
>
> Troubleshooting suggestions?
>
> John
>
>
>
>
> --
> John Kenney
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>



-- 
John Kenney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140803/5090b56f/attachment.html>