[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
Fri Jan 18 13:49:20 CST 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=10885
======================================================================
Reported By: Alric
Assigned To: qwell
======================================================================
Project: Asterisk
Issue ID: 10885
Category: Applications/app_queue
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
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:
Resolution: suspended
Fixed in Version:
======================================================================
Date Submitted: 10-04-2007 09:57 CDT
Last Modified: 01-18-2008 13:49 CST
======================================================================
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.
======================================================================
----------------------------------------------------------------------
qwell - 01-18-08 13:49
----------------------------------------------------------------------
I believe the issue here is related to the soxmix vs sox -m differences
that existed at one point.
I'm going to go ahead and close this report, but if this is still an issue
in the latest version of 1.4, please feel free to reopen.
Issue History
Date Modified Username Field Change
======================================================================
01-18-08 13:49 qwell Status feedback => resolved
01-18-08 13:49 qwell Resolution open => suspended
01-18-08 13:49 qwell Assigned To => qwell
01-18-08 13:49 qwell Note Added: 0080870
======================================================================
More information about the asterisk-bugs
mailing list