[arm-allstar] no inbound connections
Doug Crompton
doug at crompton.com
Sun May 24 00:10:42 EST 2015
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?
Assuming they are getting a failure you need to go into your client -
asterisk -rvvv
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.
Also make sure you are registered. In the client -
iax2 show registry
73 Doug
WA3DSP
http://www.crompton.com/hamradio
> From: ku6v at pacbell.net
> To: arm-allstar at hamvoip.org
> Date: Sat, 23 May 2015 21:30:43 -0700
> Subject: [arm-allstar] no inbound connections
>
> Thanks Cory
> I do have it set for UDP port 4569. I reset the router to factory defaults
> and restored the set up and still no luck.
>
> 73
> KU6V
>
> -----Original Message-----
> From: arm-allstar-bounces at hamvoip.org
> [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> arm-allstar-request at hamvoip.org
> Sent: Saturday, May 23, 2015 5:46 PM
> To: arm-allstar at hamvoip.org
> Subject: arm-allstar Digest, Vol 12, Issue 59
>
> Send arm-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of arm-allstar digest..."
>
>
> Today's Topics:
>
> 1. Re: No inbound connections (Corey Dean)
> 2. Cannot Connect to Echolink (John)
> 3. Re: Cannot Connect to Echolink (John)
> 4. Re: Cannot Connect to Echolink (Doug Crompton)
> 5. Local monitor speaker for the RPi2 (Steve Zingman)
> 6. Re: Cannot Connect to Echolink (John)
> 7. Re: Cannot Connect to Echolink (jim.pilgram at gmail.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 23 May 2015 13:20:17 -0400
> From: Corey Dean <n3fe at repeater.net>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] No inbound connections
> Message-ID: <3C50F76F-D101-46A8-A9FD-21E255FE13C8 at repeater.net>
> Content-Type: text/plain; charset=us-ascii
>
> Most routers by default when port forwarding use tcp by default which ssh
> uses. Asterisk uses udp so make sure your asterisk port is udp forwarding
> and not tcp.
>
> Corey
>
> > On May 23, 2015, at 12:27 PM, ku6v <ku6v at pacbell.net> wrote:
> >
> > Howdy all
> > I can not get inbound connections.
> > I have a Netgear router.
> > Port 4569 is forwarded but no inbounds are connecting.
> > I do connect via SSH to my Pi2 from the internet.
> > Is there something in the extensions.conf conflicting perhaps?
> >
> > 73
> > KU6V
> > _______________________________________________
> >
> > 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/
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 23 May 2015 13:35:32 -0500
> From: John <wb5nfc at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] Cannot Connect to Echolink
> Message-ID:
> <CALfzjYTL7v8D01QyUL1L+ggzmsDrLW2T7q+JRiU_Jw0duwSyOQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Once again, I've run out of things to try.
> New rebuild
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/3d2bd7f
> 4/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 23 May 2015 13:51:03 -0500
> From: John <wb5nfc at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Cannot Connect to Echolink
> Message-ID:
> <CALfzjYSt3T=MWcHYkK+7C6jZi0ZhAB0hBjmRKDgMbAZD96VQMw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Trying that again on a bigger keyboard...
>
> Still unable to connect to Echolink.
> New rebuild of RPi2
> New SSD card
> Switched routers
> VPN connection of the node verified with curl ipecho ping and traceroute
> work properly DMZ'd the node IP Allstar node shows to be registered echolink
> dbdump downloads node list, but "connection failed" each time
>
> Any suggestions?
>
> John
>
>
>
>
>
> On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc at gmail.com> wrote:
>
> > Once again, I've run out of things to try.
> > New rebuild
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/c3f3d12
> 8/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 23 May 2015 18:40:11 -0400
> From: Doug Crompton <doug at crompton.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Cannot Connect to Echolink
> Message-ID: <BLU171-W40802163B9D2D86EF2812BACF0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Connection failed coming in or going out? You know you have to do *3 and
> pad with 0's to 7 digits.
>
> http://ohnosec.org/drupal/node/56
>
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
>
> From: wb5nfc at gmail.com
> Date: Sat, 23 May 2015 13:51:03 -0500
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Cannot Connect to Echolink
>
> Trying that again on a bigger keyboard...
> Still unable to connect to Echolink. New rebuild of RPi2New SSD cardSwitched
> routersVPN connection of the node verified with curl ipechoping and
> traceroute work properlyDMZ'd the node IPAllstar node shows to be
> registeredecholink dbdump downloads node list, but "connection failed" each
> time Any suggestions?
> John
>
>
>
>
> On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc at gmail.com> wrote:
> Once again, I've run out of things to try. New rebuild
>
>
>
> _______________________________________________
>
> 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/20150523/7ffce95
> c/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 23 May 2015 18:57:45 -0400
> From: Steve Zingman <szingman at msgstor.com>
> To: app_rpt-users at ohnosec.org, arm-allstar at hamvoip.org
> Subject: [arm-allstar] Local monitor speaker for the RPi2
> Message-ID: <556105E9.8020500 at msgstor.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Since I put up the information to add chan_alsaradio to be used as a local
> speaker for the RPI2 I have been asked if there is a simpler way to achieve
> a local monitor speaker.
> After thinking about it for a while I came up with the following:
>
> Do we really need to add alsa just for a speaker?
> Do we need to add a channel driver from a outside source?
> What else can we do?
>
> We are already using oss for audio on Asterisk. Asterisk has a stock channel
> driver called chan_oss.
> It can be used as a simple way to listen to the node on a external speaker.
> This does not require much other then a way to adjust the speaker level.
>
> I've posted the basics on git.
> <https://github.com/N4IRS/AllStar/tree/master/platforms/rpi/rpi2/monitor>
>
> Thanks to everyone that is feeding back comments. The best way I know of to
> improve things.
>
> 73, Steve N4IRS
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 23 May 2015 18:26:53 -0500
> From: John <wb5nfc at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Cannot Connect to Echolink
> Message-ID:
> <CALfzjYQqAMqBXvayC-N9mhc9J=f64N=Mh2bkP4MS6e6o=mQ04A at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Yep, good to go on the *3 part, thanks.
>
> Think I've tracked my problems down to a self-inflicted VPN issue. When I
> changed VPN servers, I failed to modify the openvpn client.conf file
> properly. This caused some really strange behavior. Sometimes Echolink would
> work, other times it would not. Similar issues with Allstar connections.
> Fingers crossed, but so far so good after a couple reboots.
>
> John
>
>
>
> On Sat, May 23, 2015 at 5:40 PM, Doug Crompton <doug at crompton.com> wrote:
>
> > Connection failed coming in or going out? You know you have to do *3
> > and pad with 0's to 7 digits.
> >
> > http://ohnosec.org/drupal/node/56
> >
> >
> >
> >
> > *73 DougWA3DSPhttp://www.crompton.com/hamradio
> > <http://www.crompton.com/hamradio>*
> >
> >
> > ------------------------------
> > From: wb5nfc at gmail.com
> > Date: Sat, 23 May 2015 13:51:03 -0500
> > To: arm-allstar at hamvoip.org
> > Subject: Re: [arm-allstar] Cannot Connect to Echolink
> >
> > Trying that again on a bigger keyboard...
> >
> > Still unable to connect to Echolink.
> > New rebuild of RPi2
> > New SSD card
> > Switched routers
> > VPN connection of the node verified with curl ipecho ping and
> > traceroute work properly DMZ'd the node IP Allstar node shows to be
> > registered echolink dbdump downloads node list, but "connection
> > failed" each time
> >
> > Any suggestions?
> >
> > John
> >
> >
> >
> >
> >
> > On Sat, May 23, 2015 at 1:35 PM, John <wb5nfc at gmail.com> wrote:
> >
> > Once again, I've run out of things to try.
> > New rebuild
> >
> >
> >
> > _______________________________________________ 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/20150523/8e676d0
> 1/attachment-0001.html>
>
> ------------------------------
>
> Message: 7
> Date: Sat, 23 May 2015 14:46:14 -1000
> From: jim.pilgram at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Cannot Connect to Echolink
> Message-ID: <20150524004614.6017173.46174.2919 at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
> An HTML attachment was scrubbed...
> URL:
> <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150523/c9f1507
> 7/attachment.html>
> -------------- next part --------------
> _______________________________________________
>
> 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
>
>
> End of arm-allstar Digest, Vol 12, Issue 59
> *******************************************
>
> _______________________________________________
>
> 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/20150524/524fa9b1/attachment-0001.html>
More information about the arm-allstar
mailing list