[asterisk-bugs] [Asterisk 0015345]: SIP deadlock in 1.4 revision 199472

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15345 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15345
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.26-rc1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 199472 
Request Review:              
====================================================================== 
Date Submitted:             2009-06-17 13:11 CDT
Last Modified:              2009-06-18 09:50 CDT
====================================================================== 
Summary:                    SIP deadlock in 1.4 revision 199472
Description: 
After some brief time SIP will lock and no calls will process.
====================================================================== 

---------------------------------------------------------------------- 
 (0106630) aragon (reporter) - 2009-06-18 09:50
 https://issues.asterisk.org/view.php?id=15345#c106630 
---------------------------------------------------------------------- 
I find this very easy to reproduce in my lab.
I'm able to pass a lot of calls through 4 PRI interfaces in a non
production environment...
The basis of my tests is to load 4 PRI interfaces and pass multiple calls
to an ACD queue to logged agents. As a result some calls are answered and
some are held with MOH. A percentage of ACD calls answered by agents are
transferred to other extensions using Asterisk blind transfer.

I uploaded CLI output with sip debug enabled and each time I ran into the
lock I issued the core show locks command.  At least one of the outputs of
core show locks appears to show the same output as my first capture.  The
main difference being that in this CLI trace session I did not have to
restart Asterisk to recover from the lock.  Therefore I did not include
output from gdb thread apply all bt in this attachment.  This is a pretty
big text file but it only spans about a 10 minute test period.  I ran into
at least 7 deadlocks in that time span.

My previous attachment 06172009deadlock.txt includes gdb thread apply all
bt and core show locks output.

I do not use re-invites in my configuration. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-18 09:50 aragon         Note Added: 0106630                          
======================================================================