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

Michael Carey michaelcarey at internode.on.net
Sat May 12 19:50:26 EST 2018 

Hi David,

Interestingly, my iax.conf file does already have "allow=ulaw" in the 
[general] stanza.

The head scratching continues.


On 13/05/2018 8:08 AM, David McGough wrote:
>
> 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
>
>

More information about the arm-allstar mailing list