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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jan 13 04:32:57 CST 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18403 
====================================================================== 
Reported By:                jthurman
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   18403
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Target Version:             1.8.3
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:              2011-01-13 04:32 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)

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018554 SIP channel tried to release unowned mu...
====================================================================== 

---------------------------------------------------------------------- 
 (0130445) kkm (reporter) - 2011-01-13 04:32
 https://issues.asterisk.org/view.php?id=18403#c130445 
---------------------------------------------------------------------- 
@jthurman: A production server (1.8.1 without your patch) locked up today.
Unfortunately I did not leave instructions to the ops what to do in this
case, so, lacking any guidance, they simply reset the machine. Thus I got
nether a coredump nor the lock dump.

I am going to put your patch to the server, in an assumption that the
lock-up was the same bug that we are hunting.

May I ask you to test something for me please? The lock-up today caused a
failure of AMI, and this is how it got detected in the first place. The
network monitoring pulled data from asterisks on a schedule, and, being
unable to log on, raised an alarm. As you are able to repro every time,
could you please check if AMI also stops responding during the lock-up?
That would add significant weight to the current hypothesis that we got the
same issue. The monitoring software issues the CoreShowChannels command. 

There is a convenient expect(1) script attached to
https://issues.asterisk.org/view.php?id=16908 to issue AMI
commands interactively. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-13 04:32 kkm            Note Added: 0130445                          
======================================================================




More information about the asterisk-bugs mailing list