[asterisk-bugs] [Asterisk 0018837]: Deadlock with attended transfer of SIP call

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18837 
====================================================================== 
Reported By:                alecdavis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18837
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.2.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-17 19:25 CST
Last Modified:              2011-02-17 19:41 CST
====================================================================== 
Summary:                    Deadlock with attended transfer of SIP call
Description: 
3 SIP phones.

A calls B, and B answers.
B puts A on hold by selecting line2.
B calls C, and C answers.
B initiates transfer of line1 to line2, phone uses REFER.


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

---------------------------------------------------------------------- 
 (0132106) alecdavis (manager) - 2011-02-17 19:41
 https://issues.asterisk.org/view.php?id=18837#c132106 
---------------------------------------------------------------------- 
summary: of SIP-refer-deadlock.txt

=== Thread ID: -1292625008 (do_monitor           started at [24470]
chan_sip.c restart_monitor())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_sip.c): MUTEX
23964 handle_request_do &netlock
0xb6796e80 (1)
=== ---> Lock https://issues.asterisk.org/view.php?id=1 (channel.c): MUTEX 6211
ast_do_masquerade channels
0x8d4e0c8 (1)
=== ---> Lock https://issues.asterisk.org/view.php?id=2 (channel.c): MUTEX 6214
ast_do_masquerade original
0xbd98f48 (1)
=== ---> Lock https://issues.asterisk.org/view.php?id=3 (channel.c): MUTEX 6234
ast_do_masquerade clonechan
<u>0xb24bf7d0</u> (1)
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=4
(chan_sip.c): MUTEX 6164 sip_fixup p
<u>0xb24bab10</u> (1)
=== --- ---> Locked Here: chan_sip.c line 27632 (sip_set_rtp_peer)

=== -------------------------------------------------------------------
===
=== Thread ID: -1315861616 (pbx_thread           started at [ 5035] pbx.c
ast_pbx_start())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_sip.c): MUTEX
27632 sip_set_rtp_peer p
<u>0xb24bab10</u> (1)
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=1 (pbx.c):
MUTEX 9467 pbx_builtin_getvar_helper
chan <u>0xb24bf7d0</u> (1)
=== --- ---> Locked Here: channel.c line 6234 (ast_do_masquerade)

=== -------------------------------------------------------------------
===
=== Thread ID: -1316602992 (pbx_thread           started at [ 5035] pbx.c
ast_pbx_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0 (channel.c):
MUTEX 6211 ast_do_masquerade
channels 0x8d4e0c8 (1)
=== --- ---> Locked Here: channel.c line 6211 (ast_do_masquerade)
=== -------------------------------------------------------------------
===
======================================================================= 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-17 19:41 alecdavis      Note Added: 0132106                          
======================================================================