[asterisk-bugs] [Asterisk 0014859]: [patch] lock is not released on channel masquarade
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Aug 9 02:16:56 CDT 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=14859
======================================================================
Reported By: atis
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 14859
Category: Functions/func_lock
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.4.19
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-04-08 10:39 CDT
Last Modified: 2009-08-09 02:16 CDT
======================================================================
Summary: [patch] lock is not released on channel masquarade
Description:
Scenario:
Queue -> Local channel -> answer_macro -> TRYLOCK -> bridge (masquarade)
-> TRYLOCK
First TRYLOCK creates lock correctly, but unlock is called outside of the
same thread, so it gives permission denied. Respectively lock remains even
if channel is dead or masqueraded, and second attempt to TRYLOCK gives
failure.
======================================================================
----------------------------------------------------------------------
(0108822) tilghman (administrator) - 2009-08-09 02:16
https://issues.asterisk.org/view.php?id=14859#c108822
----------------------------------------------------------------------
atis: a repeatable case or testing on your part would be most helpful.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-09 02:16 tilghman Note Added: 0108822
2009-08-09 02:16 tilghman Status ready for testing =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list