[asterisk-bugs] [Asterisk 0015618]: Channel not locked when it should in local_attended_transfer
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Aug 2 20:20:55 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15618
======================================================================
Reported By: lmsteffan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15618
Category: Channels/chan_sip/Transfers
Reproducibility: always
Severity: block
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 209615
Request Review:
======================================================================
Date Submitted: 2009-07-30 18:58 CDT
Last Modified: 2009-08-02 20:20 CDT
======================================================================
Summary: Channel not locked when it should in
local_attended_transfer
Description:
Right after performing the transfer, the target channel (target.chan1) is
unlocked. It is not locked again before performing the masquerade (although
aa comment says so).
Performing a relock of this channel leads to a deadlock with
¤t->chan1. Trying to solve that deadlock led me to a bunch of astobj2
errors.
======================================================================
----------------------------------------------------------------------
(0108521) lmsteffan (reporter) - 2009-08-02 20:20
https://issues.asterisk.org/view.php?id=15618#c108521
----------------------------------------------------------------------
Speaking of ast_cel_report, you may want to note that I had filed a report
(bug https://issues.asterisk.org/view.php?id=15512) concerning a deadlock that
appears between the channel
handling during a transfer (ast_do_masquerade) and the ast_cel_report_event
function. This deadlock occurs (randomly but frequently) even when not
using the CEL logging functions. My workaround (not submitted as it
probably does not solve the main problem) is to test whether CEL is enabled
right at the start of the ast_cel_report_event function.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-02 20:20 lmsteffan Note Added: 0108521
======================================================================
More information about the asterisk-bugs
mailing list