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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Aug 25 12:24:13 CDT 2009


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 12:24 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0109608) bluefox (reporter) - 2009-08-25 12:24
 https://issues.asterisk.org/view.php?id=15768#c109608 
---------------------------------------------------------------------- 
I can't say I know the Asterisk code, but I think that is where the problem
lies : I think that Asterisk does much more than 5 qualify in succession
when on peer goes unreachable, which in turns floods the device's link,
which in turns make it go reachable-unreachable...and round and round we go
until traffic upstream goes up and up.

The crash is not easy to reproduce though, it usually happens but
sometimes it takes hours from the moment when the problem starts, sometimes
minutes, sometimes not at all.  Fixing the original issue would be a good
start, crash or no crash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-25 12:24 bluefox        Note Added: 0109608                          
======================================================================




More information about the asterisk-bugs mailing list