[asterisk-bugs] [Asterisk 0016847]: [patch] Deadlock between dahdi_exception and dahdi_indicate

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16847 
====================================================================== 
Reported By:                shin-shoryuken
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   16847
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Target Version:             1.6.2.15
Asterisk Version:           SVN 
JIRA:                       SWP-927 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-16 15:16 CST
Last Modified:              2010-10-12 14:49 CDT
====================================================================== 
Summary:                    [patch] Deadlock between dahdi_exception and
dahdi_indicate
Description: 
I've encountered a deadlock situation between dahdi_exception and
dahdi_indicate, running Asterisk 1.6.1.6 (confirmed as well in 1.6.1.14) on
Debian Lenny x86_64.  Deadlock occurs roughly once a week, usually under
lower call volume (strangely enough).  The issue seems to arise mostly when
swapping between call-waiting lines on a DAHDI channel.
====================================================================== 

---------------------------------------------------------------------- 
 (0127904) alecdavis (manager) - 2010-10-12 14:49
 https://issues.asterisk.org/view.php?id=16847#c127904 
---------------------------------------------------------------------- 
I couldn't get trunk to deadlock before the patch.

using issue_16847_v1.8.patch: Not yet tested later patch.

IIRC this never deadlocked when swapping between calls after the call was
sucessfully answered.

The key to getting this to deadlock in earlier versions, is to hook flash
on the FXS port just as you hear the CW beep.


---

Not sure if this is releated, to one of the changes, but the following
senario didn't give MOH when I answered.

Established call from SIP -> FXS 
Call 2 from FXO -> (SIP & FXS) used DIAL(SIP/xyz&DAHDI/35)
Both SIP phone and FXS port received CW beeps, but when answered by
flashing with the FXS port, the SIP phone didn't have MOH.

I need to check 'trunk' without the patch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-12 14:49 alecdavis      Note Added: 0127904                          
======================================================================