[arm-allstar] IAX2 calltoken timestamp Message Floods - Dropping connections

[Lu Vencl]

Interesting. I wonder if this other issue I just uncovered is related? If I make a direct iax connection to my node with this app, in other words, not through AllStar portal, allmon will stop reporting while I’m connected.  
Example:
When not connected
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image0.jpeg
Type: image/jpeg
Size: 527814 bytes
Desc: not available
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20221015/7c45b709/attachment.jpeg>
-------------- next part --------------


And when I connect directly to my node:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image1.jpeg
Type: image/jpeg
Size: 69400 bytes
Desc: not available
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20221015/7c45b709/attachment-0001.jpeg>
-------------- next part --------------


It seems as allmon is unable to gather data during my connection. 


> On Oct 14, 2022, at 5:08 PM, David McGough via ARM-allstar <arm-allstar at hamvoip.org> wrote:
> 
> 
> Hi Lawrence,
> 
> These messages are coming from a new client application which has been 
> recently released.  There is a bug in how it initiates connections.
> 
> I believe this problem can be at least partly mitigated by adjusting some
> parameters in your /etc/asterisk/iax.conf file. In the [general] stanza,
> add:
> 
> iaxthreadcount=100
> iaxmaxthreadcount=200 
> maxcallnumbers=16
> maxcallnumbers_nonvalidated=32
> 
> 
> ...And, restart asterisk.
> 
> 73, David K4FXC
> 
>> On Fri, 14 Oct 2022, "Lawrence Roney via ARM-allstar" wrote:
>> 
>> On our HamVoIP Pi 4 hub we have started seeing the following in the Asterisk message log about once a week.   The IP's are typically coming from various visiting nodes connecting to the hub; not from our established club repeaters.
>> 
>> [Oct 14 09:18:04] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> [Oct 14 09:18:04] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> [Oct 14 09:18:04] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> [Oct 14 09:18:05] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> [Oct 14 09:18:05] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> [Oct 14 09:18:05] WARNING[368] chan_iax2.c: Too much delay in IAX2 calltoken timestamp from address 174.195.xxx.xxx
>> 
>> When the message flood occurs (> 200 per second), it causes all the connections to drop.  While most permalinks reestablish, other connections need to be manually reconnected.   This appears to be a recent manifestation and not related to any observed network issues at the hub site.  Any ideas on a root cause?
>> 
>> We are running:
>> Hamvoip Firmware Version - RPi2-3-4 Version 1.7-03 Allstar - September 12, 2022 - K4FXC
>> Hamvoip Allstar Version - Asterisk 1.4.23-pre.hamvoip-V1.7.1-04 app_rpt-0.327-01/22/2022
>> Linux Kernel Version - Linux version 4.19.65-1-ARCH (builduser at leming) gcc version 8.3.0 (GCC)) #1 SMP PREEMPT Fri Aug 9 23:29:04 UTC 2019
>> 
>> Thanks,
>> 
>> Lawrence - N6YFN
>> Henderson Amateur Radio Club
>> www.w7hen.org<http://www.w7hen.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/4 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/4 web page - http://hamvoip.org