[asterisk-bugs] [Asterisk 0018403]: [patch] Deadlock on SIP blind transfer (REFER)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18403 
====================================================================== 
Reported By:                jthurman
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18403
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-2667 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!): 296824 
Request Review:              
====================================================================== 
Date Submitted:             2010-11-30 18:25 CST
Last Modified:              2010-12-23 03:13 CST
====================================================================== 
Summary:                    [patch] Deadlock on SIP blind transfer (REFER)
Description: 
All SIP:
- A calls B
- B blind-transfers A to C (Using REFER)
- Asterisk stops responding to SIP requests (Deadlocked)

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

---------------------------------------------------------------------- 
 (0129916) kkm (reporter) - 2010-12-23 03:13
 https://issues.asterisk.org/view.php?id=18403#c129916 
---------------------------------------------------------------------- 
jthurman: Got a lock-up with your patch, see 18403-kkm-locks-1.txt.
Scenario: trunk A calls extension that ultimately rings a queue member B
(via Queue()). B transfers to extension X. As far as I can tell, the
extension X is not entered into -- a Verbose() first thing there did not
print anything. Sounds just like what you are experiencing? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-23 03:13 kkm            Note Added: 0129916                          
======================================================================