<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">OK here is what I am getting -<br><br>wa3dsp-40961-cm*CLI> rpt fun 40961 *341971<br>[May 24 01:40:05] WARNING[406]: chan_iax2.c:9237 socket_process: Call rejected by 76.254.51.254: No such context/extension<br> -- Hungup 'IAX2/76.254.51.254:4569-8261'<br> -- Hungup 'DAHDI/pseudo-377285191'<br> -- Hungup 'DAHDI/pseudo-1392306225'<br> -- <DAHDI/pseudo-203026987> Playing 'rpt/node' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'digits/4' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'digits/1' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'digits/9' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'digits/7' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'digits/1' (language 'en')<br> -- <DAHDI/pseudo-203026987> Playing 'rpt/connection_failed' (language 'en')<br> -- Hungup 'DAHDI/pseudo-203026987'<br> -- <DAHDI/pseudo-550995073> Playing '/etc/asterisk/local/node-id' (language 'en')<br>wa3dsp-40961-cm*CLI><br><br>So this is not a routing problem but a configuration problem in Allstar.<br><br id="FontBreak"></font><font style="" face="Tahoma,sans-serif">This indicates you do not have an extension setup for the node. Is this a manual setup or did you use the automated scripts to setup your node? If you used automated it should have setup correctly. You need to have the node in extensions.conf</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">Check /etc/asterisk/extensions.conf and make sure you have this set correctly -</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">[radio-secure]</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">exten => 40961,1,rpt,40961</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">exten => 1999,1,rpt,1999</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">You need to have this context with your node entered in place on 40961 above.</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 22:24:21 -0700<br>> Subject: [arm-allstar] no inbound connections<br>> <br>> Host dnsmgr Username Perceived Refresh<br>> State<br>> 67.215.233.178:4569 Y 41971 76.254.51.254:4569 60<br>> Registered<br>> <br>> Doug - the attempt to connect is from another allstar node. I listened on<br>> the phone and heard an error message playing back on the other node.<br>> I will have to get that friend to attempt tomorrow and I will get back on<br>> the message that is heard. I will also look at the client while attempt to<br>> connect is in progress and note if there is any activity.<br>> <br>> 73<br>> KU6V<br>> <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 10:11 PM<br>> To: arm-allstar@hamvoip.org<br>> Subject: arm-allstar Digest, Vol 12, Issue 60<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. Memorial Weekend Special (Doug Crompton)<br>> 2. no inbound connections (ku6v)<br>> 3. Re: no inbound connections (Doug Crompton)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Sat, 23 May 2015 23:06:45 -0400<br>> From: Doug Crompton <doug@crompton.com><br>> To: "arm-allstar@hamvoip.org" <arm-allstar@hamvoip.org><br>> Subject: [arm-allstar] Memorial Weekend Special<br>> Message-ID: <BLU171-W1209EF8C48C961111FF6C7ABACE0@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> http://www.ebay.com/itm/111621320317<br>> <br>> 73 Doug<br>> WA3DSP<br>> http://www.crompton.com/hamradio<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/2a8de07<br>> 3/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Sat, 23 May 2015 21:30:43 -0700<br>> From: "ku6v" <ku6v@pacbell.net><br>> To: <arm-allstar@hamvoip.org><br>> Subject: [arm-allstar] no inbound connections<br>> Message-ID:<br>> <br>> <!&!AAAAAAAAAAAYAAAAAAAAAE9r4I8ueBhIvK+2WkZlDhDCgAAAEAAAAArs1rmuiSpFqQRYMHV6<br>> p9IBAAAAAA==@pacbell.net><br>> <br>> Content-Type: text/plain; charset="us-ascii"<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>> ------------------------------<br>> <br>> Message: 3<br>> Date: Sun, 24 May 2015 01:10:42 -0400<br>> From: Doug Crompton <doug@crompton.com><br>> To: ARM Allstar <arm-allstar@hamvoip.org><br>> Subject: Re: [arm-allstar] no inbound connections<br>> Message-ID: <BLU171-W717E0BF025ED0A73D0449ABACE0@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> How are you doing the inbound connections? Are you having someone connect to<br>> you? What are they getting when they try to connect? Failure or nothing<br>> happens? If nothing happens then you may not be in their database. It takes<br>> 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<br>> the connect you should see logging activity. If you see nothing that you can<br>> be failry sure there is a routing problem. If it is getting through and<br>> there is an error take not and let us know.<br>> <br>> Also make sure you are registered. In the client -<br>> <br>> iax2 show registry<br>> <br>> 73 Doug<br>> WA3DSP<br>> http://www.crompton.com/hamradio<br>> <br>> <br>> > 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>> ><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<br>> 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>> ><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<br>> 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"<br>> 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>> ><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<br>> 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<br>> channel<br>> > driver called chan_oss.<br>> > It can be used as a simple way to listen to the node on a external<br>> 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<br>> 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<br>> 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>> ><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>> ><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 -<br>> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/<br>> > <br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL:<br>> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150524/524fa9b<br>> 1/attachment.html><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 60<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></body>
</html>