[asterisk-bugs] [Asterisk 0015768]: SIP qualify goes out of control and kills links

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15768 
====================================================================== 
Reported By:                bluefox
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15768
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.26.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-24 09:50 CDT
Last Modified:              2009-08-25 14:04 CDT
====================================================================== 
Summary:                    SIP qualify goes out of control and kills links
Description: 
Situation: 
- about 1200 SIP peers in realtime (onloy 5 in sip.conf)
- Most of those 1200 are configured with qualify=yes
- Servers, which is normal at 2.5Mpbs usage, suddently spikes to 6-10Mpbs
outgoing.
====================================================================== 

---------------------------------------------------------------------- 
 (0109609) dvossel (administrator) - 2009-08-25 14:04
 https://issues.asterisk.org/view.php?id=15768#c109609 
---------------------------------------------------------------------- 
I did a quick test using the default 'qualify=yes' for a peer.  I let the
peer qualify, then I disconnected the device.  I monitored qualify packets
Asterisk sent and only 5 qualifies were sent in succession.  I believe
Asterisk reattempts this every 30 seconds.  You may want to verify my
findings with your system by doing a similar test and capturing the results
with wireshark. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-25 14:04 dvossel        Note Added: 0109609                          
======================================================================