<html><head></head><body class="hmmessage" data-blackberry-caret-color="#00a8df" style="background-color: rgb(255, 255, 255); line-height: initial;"><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br name="BB10" caretmarkerset="INVALID" class="markedForCaretMarkerRemoval"></div> <div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br style="display:initial"></div> <div style="font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.</div> <table width="100%" style="background-color:white;border-spacing:0px;"> <tbody><tr><td colspan="2" style="font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"> <div id="_persistentHeader" style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in; font-family: Tahoma, 'BB Alpha Sans', 'Slate Pro'; font-size: 10pt;"> <div><b>From: </b>Doug Crompton</div><div><b>Sent: </b>Saturday, May 23, 2015 19:10</div><div><b>To: </b>ARM Allstar</div><div><b>Reply To: </b>ARM Allstar</div><div><b>Subject: </b>Re: [arm-allstar] no inbound connections</div></div></td></tr></tbody></table><div style="border-style: solid none none; border-top-color: rgb(186, 188, 209); border-top-width: 1pt; font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"></div><br><div id="_originalContent" style="">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font style="" color="#000000" face="Tahoma,sans-serif">How are you doing the inbound connections? Are you having someone connect to you? What are they getting when they try to connect? Failure or nothing happens? If nothing happens then you may not be in their database. It takes 10 minutes at boot to update all local databases. What is your node number?<br><br>Assuming they are getting a failure you need to go into your client -<br><br> asterisk -rvvv<br><br>and look to see if there is an attempt to connect. At the moment they try the connect you should see logging activity. If you see nothing that you can be failry sure there is a routing problem. If it is getting through and there is an error take not and let us know.<br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">Also make sure you are registered. In the client -</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">iax2 show registry</font><br><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div>> From: ku6v@pacbell.net<br>> To: arm-allstar@hamvoip.org<br>> Date: Sat, 23 May 2015 21:30:43 -0700<br>> Subject: [arm-allstar] no inbound connections<br>> <br>> Thanks Cory<br>> I do have it set for UDP port 4569. I reset the router to factory defaults<br>> and restored the set up and still no luck.<br>> <br>> 73<br>> KU6V<br>> <br>> -----Original Message-----<br>> From: arm-allstar-bounces@hamvoip.org<br>> [mailto:arm-allstar-bounces@hamvoip.org] On Behalf Of<br>> arm-allstar-request@hamvoip.org<br>> Sent: Saturday, May 23, 2015 5:46 PM<br>> To: arm-allstar@hamvoip.org<br>> Subject: arm-allstar Digest, Vol 12, Issue 59<br>> <br>> Send arm-allstar mailing list submissions to<br>> arm-allstar@hamvoip.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> or, via email, send a message with subject or body 'help' to<br>> arm-allstar-request@hamvoip.org<br>> <br>> You can reach the person managing the list at<br>> arm-allstar-owner@hamvoip.org<br>> <br>> When replying, please edit your Subject line so it is more specific than<br>> "Re: Contents of arm-allstar digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: No inbound connections (Corey Dean)<br>> 2. Cannot Connect to Echolink (John)<br>> 3. Re: Cannot Connect to Echolink (John)<br>> 4. Re: Cannot Connect to Echolink (Doug Crompton)<br>> 5. Local monitor speaker for the RPi2 (Steve Zingman)<br>> 6. Re: Cannot Connect to Echolink (John)<br>> 7. Re: Cannot Connect to Echolink (jim.pilgram@gmail.com)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Sat, 23 May 2015 13:20:17 -0400<br>> From: Corey Dean <n3fe@repeater.net><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] No inbound connections<br>> Message-ID: <3C50F76F-D101-46A8-A9FD-21E255FE13C8@repeater.net><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> Most routers by default when port forwarding use tcp by default which ssh<br>> uses. Asterisk uses udp so make sure your asterisk port is udp forwarding<br>> and not tcp.<br>> <br>> Corey<br>> <br>> > On May 23, 2015, at 12:27 PM, ku6v <ku6v@pacbell.net> wrote:<br>> > <br>> > Howdy all<br>> > I can not get inbound connections.<br>> > I have a Netgear router.<br>> > Port 4569 is forwarded but no inbounds are connecting.<br>> > I do connect via SSH to my Pi2 from the internet.<br>> > Is there something in the extensions.conf conflicting perhaps?<br>> > <br>> > 73<br>> > KU6V<br>> > _______________________________________________<br>> > <br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> > <br>> > Visit the BBB web page - <br>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sat, 23 May 2015 13:35:32 -0500<br>> From: John <wb5nfc@gmail.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: [arm-allstar] Cannot Connect to Echolink<br>> Message-ID:<br>> <CALfzjYTL7v8D01QyUL1L+ggzmsDrLW2T7q+JRiU_Jw0duwSyOQ@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Once again, I've run out of things to try.<br>> New rebuild<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/3d2bd7f<br>> 4/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Sat, 23 May 2015 13:51:03 -0500<br>> From: John <wb5nfc@gmail.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> Message-ID:<br>> <CALfzjYSt3T=MWcHYkK+7C6jZi0ZhAB0hBjmRKDgMbAZD96VQMw@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Trying that again on a bigger keyboard...<br>> <br>> Still unable to connect to Echolink.<br>> New rebuild of RPi2<br>> New SSD card<br>> Switched routers<br>> VPN connection of the node verified with curl ipecho ping and traceroute<br>> work properly DMZ'd the node IP Allstar node shows to be registered echolink<br>> dbdump downloads node list, but "connection failed" each time<br>> <br>> Any suggestions?<br>> <br>> John<br>> <br>> <br>> <br>> <br>> <br>> On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc@gmail.com> wrote:<br>> <br>> > Once again, I've run out of things to try.<br>> > New rebuild<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/c3f3d12<br>> 8/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Sat, 23 May 2015 18:40:11 -0400<br>> From: Doug Crompton <doug@crompton.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> Message-ID: <BLU171-W40802163B9D2D86EF2812BACF0@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Connection failed coming in or going out? You know you have to do *3 and<br>> pad with 0's to 7 digits.<br>> <br>> http://ohnosec.org/drupal/node/56<br>> <br>> 73 Doug<br>> WA3DSP<br>> http://www.crompton.com/hamradio<br>> <br>> <br>> From: wb5nfc@gmail.com<br>> Date: Sat, 23 May 2015 13:51:03 -0500<br>> To: arm-allstar@hamvoip.org<br>> Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> <br>> Trying that again on a bigger keyboard...<br>> Still unable to connect to Echolink. New rebuild of RPi2New SSD cardSwitched<br>> routersVPN connection of the node verified with curl ipechoping and<br>> traceroute work properlyDMZ'd the node IPAllstar node shows to be<br>> registeredecholink dbdump downloads node list, but "connection failed" each<br>> time Any suggestions? <br>> John <br>> <br>> <br>> <br>> <br>> On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc@gmail.com> wrote:<br>> Once again, I've run out of things to try. New rebuild <br>> <br>> <br>> <br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB web page -<br>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/7ffce95<br>> c/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Sat, 23 May 2015 18:57:45 -0400<br>> From: Steve Zingman <szingman@msgstor.com><br>> To: app_rpt-users@ohnosec.org, arm-allstar@hamvoip.org<br>> Subject: [arm-allstar] Local monitor speaker for the RPi2<br>> Message-ID: <556105E9.8020500@msgstor.com><br>> Content-Type: text/plain; charset=windows-1252; format=flowed<br>> <br>> Since I put up the information to add chan_alsaradio to be used as a local<br>> speaker for the RPI2 I have been asked if there is a simpler way to achieve<br>> a local monitor speaker.<br>> After thinking about it for a while I came up with the following:<br>> <br>> Do we really need to add alsa just for a speaker?<br>> Do we need to add a channel driver from a outside source?<br>> What else can we do?<br>> <br>> We are already using oss for audio on Asterisk. Asterisk has a stock channel<br>> driver called chan_oss.<br>> It can be used as a simple way to listen to the node on a external speaker.<br>> This does not require much other then a way to adjust the speaker level.<br>> <br>> I've posted the basics on git.<br>> <https://github.com/N4IRS/AllStar/tree/master/platforms/rpi/rpi2/monitor><br>> <br>> Thanks to everyone that is feeding back comments. The best way I know of to<br>> improve things.<br>> <br>> 73, Steve N4IRS<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Sat, 23 May 2015 18:26:53 -0500<br>> From: John <wb5nfc@gmail.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> Message-ID:<br>> <CALfzjYQqAMqBXvayC-N9mhc9J=f64N=Mh2bkP4MS6e6o=mQ04A@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>> <br>> Yep, good to go on the *3 part, thanks.<br>> <br>> Think I've tracked my problems down to a self-inflicted VPN issue. When I<br>> changed VPN servers, I failed to modify the openvpn client.conf file<br>> properly. This caused some really strange behavior. Sometimes Echolink would<br>> work, other times it would not. Similar issues with Allstar connections.<br>> Fingers crossed, but so far so good after a couple reboots.<br>> <br>> John<br>> <br>> <br>> <br>> On Sat, May 23, 2015 at 5:40 PM, Doug Crompton <doug@crompton.com> wrote:<br>> <br>> > Connection failed coming in or going out? You know you have to do *3 <br>> > and pad with 0's to 7 digits.<br>> ><br>> > http://ohnosec.org/drupal/node/56<br>> ><br>> ><br>> ><br>> ><br>> > *73 DougWA3DSPhttp://www.crompton.com/hamradio<br>> > <http://www.crompton.com/hamradio>*<br>> ><br>> ><br>> > ------------------------------<br>> > From: wb5nfc@gmail.com<br>> > Date: Sat, 23 May 2015 13:51:03 -0500<br>> > To: arm-allstar@hamvoip.org<br>> > Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> ><br>> > Trying that again on a bigger keyboard...<br>> ><br>> > Still unable to connect to Echolink.<br>> > New rebuild of RPi2<br>> > New SSD card<br>> > Switched routers<br>> > VPN connection of the node verified with curl ipecho ping and <br>> > traceroute work properly DMZ'd the node IP Allstar node shows to be <br>> > registered echolink dbdump downloads node list, but "connection <br>> > failed" each time<br>> ><br>> > Any suggestions?<br>> ><br>> > John<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc@gmail.com> wrote:<br>> ><br>> > Once again, I've run out of things to try.<br>> > New rebuild<br>> ><br>> ><br>> ><br>> > _______________________________________________ arm-allstar mailing <br>> > list arm-allstar@hamvoip.org <br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit <br>> > the BBB web page - <br>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> ><br>> > _______________________________________________<br>> ><br>> > arm-allstar mailing list<br>> > arm-allstar@hamvoip.org<br>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> ><br>> > Visit the BBB web page -<br>> > http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/8e676d0<br>> 1/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Sat, 23 May 2015 14:46:14 -1000<br>> From: jim.pilgram@gmail.com<br>> To: arm-allstar@hamvoip.org<br>> Subject: Re: [arm-allstar] Cannot Connect to Echolink<br>> Message-ID: <20150524004614.6017173.46174.2919@gmail.com><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/c9f1507<br>> 7/attachment.html><br>> -------------- next part --------------<br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB web page -<br>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> <br>> End of arm-allstar Digest, Vol 12, Issue 59<br>> *******************************************<br>> <br>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> arm-allstar@hamvoip.org<br>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>> Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> <br></div> </div>
<br><!--end of _originalContent --></div></body></html>