[asterisk-bugs] [Asterisk 0018441]: Deadlock after failed SIP fax call
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Dec 8 17:12:14 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18441
======================================================================
Reported By: Alric
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18441
Category: Core/General
Reproducibility: always
Severity: block
Priority: normal
Status: new
Asterisk Version: 1.8.1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-12-08 17:10 CST
Last Modified: 2010-12-08 17:12 CST
======================================================================
Summary: Deadlock after failed SIP fax call
Description:
I've been testing T.38 with my SIP provider using a Linksys ATA and a fax
machine behind it.
I initiate the fax with my fax machine and it connects with the other end.
Shortly after the fax machine thinks the call disconnects. If I type a
'core show channels' at this point, I don't see any active channels. At
this point the PBX does not accept any more calls. Commands also seem to
not go through on the CLI until I 'exit' and 'asterisk -vvvvvr' again.
Asterisk is compiled with DONT_OPTIMIZE and DEBUG_THREADS. I have run
this scenario 3 to 5 times now with the same result so I am faithful I can
reproduce it as needed.
Attached is the output from 'core show locks' after the presumed deadlock.
======================================================================
----------------------------------------------------------------------
(0129474) Alric (reporter) - 2010-12-08 17:12
https://issues.asterisk.org/view.php?id=18441#c129474
----------------------------------------------------------------------
I originally ran into this on 1.8.0, and after upgrading to 1.8.1 I can
still reproduce it.
Issue History
Date Modified Username Field Change
======================================================================
2010-12-08 17:12 Alric Note Added: 0129474
======================================================================
More information about the asterisk-bugs
mailing list