[asterisk-bugs] [Asterisk 0009327]: Manager Dropping Events Under Moderate Call Load

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9327 
====================================================================== 
Reported By:                dgarstang
Assigned To:                bweschke
====================================================================== 
Project:                    Asterisk
Issue ID:                   9327
Category:                   Core/ManagerInterface
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             03-20-2007 13:28 CDT
Last Modified:              09-12-2007 17:21 CDT
====================================================================== 
Summary:                    Manager Dropping Events Under Moderate Call Load
Description: 
Asterisk 1.4.1.

The Manager interface seems to drop events under moderate call load.

I am initiating calls to Asterisk with SIPP:
sipp tp-test5 -sn uac -m 200 -s 1xxx2423021 -d 65000 -l 200 -r 7 -rp 1

At the same time I am running an ngrep on the manager port:
ngrep -d eth1 port 5038 > foo

Seven calls per second is not an extremely high number. However, the
manager interface seems to be dropping or missing sending NewChannel
events. 

Specifically, I am monitoring Newchannnel and Hangup events. When
initiating new calls, if the number of calls per second, reaches some
thresh-hold (around 7), then the manager interface does not send all the
events over the socket. This is evidenced by the ouput of the ngrep
command.

When calls are being disconnected, SIPP always disconnects at about 10
calls per second, which just about always results in the manager interface
not sending Hangup events over the socket. In one example, I started new
calls at 5 per second, and the manager interface sent all of those.
However, on call teardown, it did not send 11 hangup events.

Under load the events should be delayed, not dropped!

The system is a single CPU 2.0Ghz machine.

====================================================================== 

---------------------------------------------------------------------- 
 jtodd - 09-12-07 17:21  
---------------------------------------------------------------------- 
FWIW, the reporter is possibly no longer in an environment where this bug
is important to track, so no response should not be considered as a "bug
fixed" result.

Hopefully, nyt is able to confirm/deny based on a more recent version of
the code. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-12-07 17:21  jtodd          Note Added: 0070452                          
======================================================================