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

Steve Agee irlp8720 at yahoo.com
Sat May 12 16:52:20 EST 2018


Can you ping 2560?

ping 173.82.59.253

N5ZUA

On 5/12/2018 4:43 PM, "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



More information about the arm-allstar mailing list