[arm-allstar] Echolink Error

Wed Aug 6 13:54:10 EST 2014

Great idea, thanks. I'll give it a go!

J.

Sent from my iPhone

> On Aug 6, 2014, at 11:10 AM, Doug Crompton <doug at crompton.com> wrote:
> 
> John,
> 
>   Yes the port checking routines would only report TCP as UDP ports would give no response. It sounds crazy but one way you could check the ports is to turn off echolink - comment it out - and set your ssh port on the BBB to 5198 or 5199 and see if you can ssh in using those ports. That would test if they are blocked for some reason. You would have to forward TCP or both in your router though as ssh is TCP.
> 
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
> 
> 
> Date: Wed, 6 Aug 2014 09:05:49 -0500
> From: wb5nfc at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink Error
> 
> Yes, Echolink was working via the hotspot with an IRLP/Echolink Raspberri Pi node. Node IP was DMZ'd rather than forwarding specific ports as I recall. That's what I'm going to try next. I've had problems with data-throttling nearly every month except this one. I think they finally have things worked out with Verizon. My monthly data cap is (much) higher through Millenicom than it would be directly through Verizon. It does complicate matters considerably when there is a problem. 
> 
> Could you try this site to see if it properly reports open ports on your node?
> 
> http://www.yougetsignal.com/tools/open-ports/
> 
> When I run it on my external IP, it only reports TCP ports that are open - none of my UDP ports. Required ports (TCP and UDP) are all listed in port forwarding in my router config...
> 
> John
> 
> 
> On Tue, Aug 5, 2014 at 11:02 PM, Doug Crompton <doug at crompton.com> wrote:
> There was no echolink_permit.conf in the distribution and the permit/deny lines were commented out in the echolink.conf file. Unless you changed that it should not be the issue.
> 
> power=20
> height=50
> gain=6
> dir=0
> ;deny=
> ;permit=
> 
> John,
> 
>  Have you had echolink working with your current provider/router at your QTH with any platform?
> 
> 
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
> 
> 
> Date: Tue, 5 Aug 2014 23:28:28 -0400
> From: kp4tr.ramon at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink Error
> 
> 
> Do you have a echolink_permit.conf file in /etc/asterisk? Sounds as if you're denying all inbound connections.
> I tried to connect and seems I connect, then get kicked out.
> 
> Also check in echolink.conf if there is an entry that says:
> 
> deny = -l
> or
> deny =
> 
> Remove them.
> 
> See http://www.allstarnode.com/viewtopic.php?f=10&t=102
> 
> 
> On 8/5/2014 8:20 PM, John wrote:
> Still unable to connect to Echolink nodes nor can they         connect to me. My node shows up on Echolink station list, but stations time out without connecting. I tried today from my iPhone (LTE, not wireless connection). Echolink client says: Connection failed. Cannot connect to WB5NFC-L. UNAUTHORIZED. Double-checked port forwarding on the router. Beginning to wonder if Verizon might be doing some port filtering. Anyone else successfully using a wifi hotspot with VoIP?
> 
> John
> 
> Sent from my iPhone
> 
> On Aug 5, 2014, at 5:56 PM, Dave P <tdydave at gmail.com> wrote:
> 
> Greetings All,
> 
> John recently got setup on the BBB using a Verizon Hotspot 4Gig connection.  He also has an echolink node that I verified the configuration on the allstarlink web page and the echolink.conf file are set.  He opened up the eanmode command on rpt.conf file.  
> 
> John,
> 
> Please give us an update your echolink and allstar and advise what is your current state to resolving echolink issues and connections?  Check out this website to view AllmonII.   www.hammradio.us  go to allstarlink page 1 and 2 and you will see Bob' ALLMONII and our Hawaii Mainland network setup.  This website will give a good opportunity to gauge how we can monitor our network.
> 
> I've included Bob W6REB on this thread if your interested in learning about it.
> 
> Bob/Jim,
> 
> John is living in an RV and just installed the BBB using Verizon 4G network.  John is in Arkansas and I got his client up and running.  He doesn't have an RF link yet, however, he wants to expand to get RF.  
> 
> 73 and aloha
> 
> Dave
> 
> 
> On Mon, Aug 4, 2014 at 9:44 AM, John <wb5nfc at gmail.com> wrote:
> Dave,
> After we hung up last night, I remembered that I                     was going to ask you more about Allmon. That's a tool I definitely want in my toolbox! Perhaps next time you have some spare time...
> 
> Once again, many thanks for all the help!
> 
> John / WB5NFC
> 
> 
> On Sun, Aug 3, 2014 at 5:22 PM, Dave P <tdydave at gmail.com> wrote:
> John,
> 
> Be glad to help.  Do you have teamviewer installed on your windows computer and I can help you out.
> 
> Here is my phone number 703-794-2111 or give me a number to call and glad to be of assistance.
> 
> 73
> 
> Dave
> 
> ---------- Forwarded message ----------
> From: John <wb5nfc at gmail.com>
> Date: Sun, Aug 3, 2014 at 6:12 PM
> Subject: [arm-allstar] Echolink Error
> To: BeagleBone Black ARM Allstar <arm-allstar at hamvoip.org>
> 
> 
> 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/
> 
> 
> 
> 
> -- 
> 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/
> 
> _______________________________________________
> 
> 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
> 
> _______________________________________________ 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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140806/e35a8017/attachment.html>