[arm-allstar] My node is not connecting any more - Digging deeper

David McGough kb4fxc at inttek.net
Sat May 12 20:13:31 EST 2018 

Hi Everyone,

I'll throw in my comments, too. Yes, there are registration problems that
have been rearing their heads regularly over the last few months. I'm
seeing this on my systems and regularly hearing reports from users;  both
HamVoIP and DIAL/ASL.

This has NOTHING to do with needing to upgrade your nodes, etc. The 
code in the chan_iax2 stack related to registration is the same as it has 
been for 10 years! Nothing has changed in any distro in recent history..

All I can say for the moment is try to bear with this a little longer. A
MAJOR, long term fix is on the immediate horizon and will be formally
announced before the end of May.

For now, if yours nodes were working and nothing has changed, don't try to
"fix" them---whether they're HamVoIP or DIAL/ASL. They aren't broken.  If
your node won't register, a temporary work-around can be to shut it down
completely for about 5 minutes and then bring it back up. Many times this
prolonged power cycling will give the overworked registration system time
to "reset" your node info.



73, David KB4FXC







On Sun, 13 May 2018, Mr. Possum (Bill) wrote:

> Michael, 
> 
> You are not alone...  Something "changed" and I am at a loss to figure out what...
> I can no longer connect to the 2560 or 2545 (The WIN system).  I have nodes that were connected 24/7/365 - and they can no longer connect.
> 
> I run about 18 repeaters and all of the sudden a whole bunch of mine just up and quit registering with allstarlink.org for some odd reason.  I haven't changed anything at all!  It's a mystery...
> 
> I figured it was due to the fact that I hadn't updated my nodes yet - with damn near 20 of them to do, I have been busy with life and haven't gotten around to it.  It's a LONG slow process and some of my nodes, I have to go do a site visit in order to update them.  (Read that as royal pain in the butt!)
> 
> So today, after you sent your message, I tried updating ONE of my nodes to the latest and greatest updates.  I was going to MAKE it work!  After some finagling and editing of config files I got it back up and running and can connect to MY nodes again....  But it STILL no longer registers with allstarlink.org and none of my bubble charts work anymore!  And of course, I can no longer connect with 2560 any longer...
> 
> I am beyond upset - I had almost 20 repeaters working PERFECTLY and all of the sudden, for some reason out of the blue that I can't identify, most of my stuff no longer works after these last rounds of multiple updates.
> 
> I am trying not to have a hissy fit over here!  LOL  I don't have ONE problem - I have almost 20!
> 
> You are not alone...  And after fiddling with it for days - I am at a complete loss as to what happened or what to do to fix it...
> 
> Bill - N5MBM
> 
> 
>       From: David McGough via arm-allstar <arm-allstar at hamvoip.org>
>  To: Michael Carey via arm-allstar <arm-allstar at hamvoip.org> 
> Cc: David McGough <kb4fxc at inttek.net>
>  Sent: Saturday, May 12, 2018 5:38 PM
>  Subject: Re: [arm-allstar] My node is not connecting any more
>    
> 
> 
> Hi Micheal,
> 
> I just tested connecting from my 41331 node to 27871. I was able to 
> connect using the g726aal2 CODEC, but not with ulaw....I guessing this may 
> be he problem: perhaps all the WinSystem nodes now only allow ulaw?
> 
> If this is the case, just add a statement like:
> 
> allow=ulaw
> 
> just after the allow=g726aal2  line in the [general] stanza of your 
> /etc/asterisk/iax.conf file.
> 
> 
> 73, David KB4FXC
> 
> 
> 
> 
> On Sun, 13 May 2018, "Michael Carey via arm-allstar" wrote:
> 
> > Hi David,
> 
> I just tied 2124 and 2135 (WAN Network) with the same results; :-(
> 
> [May 13 07:46:59] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char *
> [May 13 07:47:00] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 3
> [May 13 07:47:01] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 2
> [May 13 07:47:01] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 1
> [May 13 07:47:02] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 3
> [May 13 07:47:02] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 5
> [May 13 07:47:03] WARNING[30028]: channel.c:2447 ast_indicate_data: 
> Unable to handle indication 13 for 'IAX2/65.110.106.180:4569-9698'
>      -- Hungup 'DAHDI/pseudo-404715155'
>      -- Hungup 'DAHDI/pseudo-1619672502'
> [May 13 07:47:06] NOTICE[30022]: chan_iax2.c:4087 __auto_congest: 
> Auto-congesting call due to slow response
>      -- Hungup 'IAX2/65.110.106.180:4569-9698'
>      -- Hungup 'DAHDI/pseudo-880073874'
>      -- <DAHDI/pseudo-1614741108> Playing 'rpt/node' (language 'en')
>      -- <DAHDI/pseudo-1614741108> Playing 'digits/2' (language 'en')
>      -- <DAHDI/pseudo-1614741108> Playing 'digits/1' (language 'en')
>      -- <DAHDI/pseudo-1614741108> Playing 'digits/3' (language 'en')
>      -- <DAHDI/pseudo-1614741108> Playing 'digits/5' (language 'en')
>      -- <DAHDI/pseudo-1614741108> Playing 'rpt/connection_failed' 
> (language 'en')
>      -- Hungup 'DAHDI/pseudo-1614741108'
> [May 13 07:47:26] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char *
> [May 13 07:47:27] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 3
> [May 13 07:47:28] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 2
> [May 13 07:47:28] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 1
> [May 13 07:47:29] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 2
> [May 13 07:47:29] NOTICE[30028]: chan_simpleusb.c:2893 simpleusb_read: 
> Got DTMF char 4
> [May 13 07:47:30] WARNING[30028]: channel.c:2447 ast_indicate_data: 
> Unable to handle indication 13 for 'IAX2/65.110.106.180:4569-1110'
>      -- Hungup 'DAHDI/pseudo-1034229360'
>      -- Hungup 'DAHDI/pseudo-1459062826'
> [May 13 07:47:33] NOTICE[30019]: chan_iax2.c:4087 __auto_congest: 
> Auto-congesting call due to slow response
>      -- Hungup 'IAX2/65.110.106.180:4569-1110'
>      -- Hungup 'DAHDI/pseudo-339161486'
>      -- <DAHDI/pseudo-1367899883> Playing 'rpt/node' (language 'en')
>      -- <DAHDI/pseudo-1367899883> Playing 'digits/2' (language 'en')
>      -- <DAHDI/pseudo-1367899883> Playing 'digits/1' (language 'en')
>      -- <DAHDI/pseudo-1367899883> Playing 'digits/2' (language 'en')
>      -- <DAHDI/pseudo-1367899883> Playing 'digits/4' (language 'en')
>      -- <DAHDI/pseudo-1367899883> Playing 'rpt/connection_failed' 
> (language 'en')
>      -- Hungup 'DAHDI/pseudo-1367899883'
> vk5zea*CLI>
> 
> Michael.
> VK5ZEA
> On 13/05/2018 7:34 AM, David McGough wrote:
> > Hi Michael,
> >
> > This looks like a connection issue directly with node 2560, for some
> > reason??
> >
> > Are you able to connect to ANY other AllStar nodes or do you get the same
> > network congestion message?
> >
> > 73, David KB4FXC
> >
> >
> >
> >
> > On Sun, 13 May 2018, "Michael Carey via arm-allstar" wrote:
> >
> >> Hi Everybody,
> > I'm having trouble with my AllStarLink node; 27871
> >
> > It's running on a Beaglebone Black and has been virtually bulletproof
> > for three years.  I used to connect up to the WinSystem all the time for
> > their Insomniac Net until a change in my career made participating  a
> > lot harder... so my node has been sitting idle for around six months.
> >
> > The other day I tried to link up again... just for old times sake... but
> > to no avail. Initially the node refused to acknowledge any commands at
> > all.   A reboot seemed to make it more responsive but still no joy with
> > connecting.
> >
> > I've checked my router/firewall and nothing has changed there.  I have
> > no connectivity issues;
> >
> > PING register.allstarlink.org (67.215.233.178) 56(84) bytes of data.
> > 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=1 ttl=52
> > time=182 ms
> > 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=2 ttl=52
> > time=182 ms
> > 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=3 ttl=52
> > time=182 ms
> > 64 bytes from seal.lambdatel.com (67.215.233.178): icmp_seq=4 ttl=52
> > time=182 ms
> >
> > Below is a sample output from Asterisk when I try to link to node 3560;
> >
> > [May 13 06:58:57] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char *
> > [May 13 06:58:58] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char 3
> > [May 13 06:58:58] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char 2
> > [May 13 06:58:59] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char 5
> > [May 13 06:59:00] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char 6
> > [May 13 06:59:00] NOTICE[408]: chan_simpleusb.c:2893 simpleusb_read: Got
> > DTMF char 0
> > [May 13 06:59:01] WARNING[408]: channel.c:2447 ast_indicate_data: Unable
> > to handle indication 13 for 'IAX2/173.82.59.253:4569-10970'
> >      -- Hungup 'DAHDI/pseudo-1332342241'
> >      -- Hungup 'DAHDI/pseudo-324726405'
> > [May 13 06:59:04] NOTICE[402]: chan_iax2.c:4087 __auto_congest:
> > Auto-congesting call due to slow response
> >      -- Hungup 'IAX2/173.82.59.253:4569-10970'
> >      -- Hungup 'DAHDI/pseudo-275518100'
> >      -- <DAHDI/pseudo-864007839> Playing 'rpt/node' (language 'en')
> >      -- <DAHDI/pseudo-864007839> Playing 'digits/2' (language 'en')
> >      -- <DAHDI/pseudo-864007839> Playing 'digits/5' (language 'en')
> >      -- <DAHDI/pseudo-864007839> Playing 'digits/6' (language 'en')
> >      -- <DAHDI/pseudo-864007839> Playing 'digits/0' (language 'en')
> >      -- <DAHDI/pseudo-864007839> Playing 'rpt/connection_failed'
> > (language 'en')
> >      -- Hungup 'DAHDI/pseudo-864007839'
> >
> > Can anyone tell me what "Unable to handle indication 13 for
> > 'IAX2/173.82.59.253:4569-10970'" and "chan_iax2.c:4087 __auto_congest:
> > Auto-congesting call due to slow response" means?
> >
> > Regards,
> >
> > Michael.
> > VK5ZEA
> >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
> 
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> 
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> 
>

More information about the arm-allstar mailing list