[asterisk-bugs] [Asterisk 0011529]: One recording file empty for calls in queue with callback agents
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Dec 12 18:10:08 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11529
======================================================================
Reported By: atis
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 11529
Category: Core/Channels
Reproducibility: always
Severity: major
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.15
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 12-12-2007 11:35 CST
Last Modified: 12-12-2007 18:10 CST
======================================================================
Summary: One recording file empty for calls in queue with
callback agents
Description:
After upgrade from 1.4.10 to 1.4.14 there's a problem with recording of
queue calls. Only agent's voice is recorded, the recording of customer
voice has 0 size.
Agents are logged in trough AgentCallbackLogin, and Monitor() is issued
within answer macro of Dial().
I pinpointed that the problem starts with r85158 - where sound is
completely lost between agent and customer (that's fixed in
http://bugs.digium.com/view.php?id=0011071), but
after that fix (r88931), recording is still lost. Applying patch of
http://bugs.digium.com/view.php?id=0011071 to r85158 shows that recording is
also lost exactly in that
commit.
======================================================================
----------------------------------------------------------------------
putnopvut - 12-12-07 18:10
----------------------------------------------------------------------
eliel: That sounds like a good idea to me. If atis reports that the patch
fixes the problem, I'll add in a debug message there and in __ast_read
(which has a very similar deadlock avoidance scheme) to indicate if we have
attempted to lock more than 10 times when I commit the change.
Issue History
Date Modified Username Field Change
======================================================================
12-12-07 18:10 putnopvut Note Added: 0075319
======================================================================
More information about the asterisk-bugs
mailing list