[asterisk-bugs] [Asterisk 0010885]: Queue recording via monitor-format and monitor-join produces output different from MixMonitor
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Oct 16 17:15:39 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=10885
======================================================================
Reported By: Alric
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 10885
Category: Applications/app_queue
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.10.1
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 10-04-2007 09:57 CDT
Last Modified: 10-16-2007 17:15 CDT
======================================================================
Summary: Queue recording via monitor-format and monitor-join
produces output different from MixMonitor
Description:
I monitor both incoming and outgoing calls in my PBX. Normal calls get
recorded with MixMonitor(${UNIQUEID}.wav), Queue calls are recorded with
the monitor-format = wav and monitor-join = yes options. Both methods end
up with call files using the uniqueid, in the wav format, in
/var/spool/asterisk/monitor
Post recording I have a script that runs on the directory that basically
converts the calls to a smaller .wav format via the command "sox
recordedFile.wav -g -r 8000 -c1 recordedFileNew.wav". On the calls that
were recorded by MixMonitor, it outputs a perfectly working audio file,
smaller than the original. On the calls that were recorded through the
Queue mechanism, it outputs a file that is either 256 bytes or 320 bytes
large and is not a valid audio file, regardless of the input. I don't
think it is a problem with sox simply because it is working for all of the
MixMonitor calls, and working well.
I don't know the codebase well, and don't really know C, but the whole
issue gets really confusing to me when I look into app_queue.c and as far
as I can tell, queue monitor-join recording uses the MixMonitor
application.
======================================================================
----------------------------------------------------------------------
putnopvut - 10-16-07 17:15
----------------------------------------------------------------------
I discussed this on IRC a bit and decided that the monitor-join option is
going to be deprecated in favor of the monitor-type = mixmonitor. The plan
is still to fix this issue, though, but it seems silly to have an option
available which can be implemented in a much better way.
Issue History
Date Modified Username Field Change
======================================================================
10-16-07 17:15 putnopvut Note Added: 0072126
======================================================================
More information about the asterisk-bugs
mailing list