[asterisk-bugs] [Asterisk 0016624]: soxmerge arguments broken if Monitoring to absolute path
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Jan 17 02:23:59 CST 2010
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=16624
======================================================================
Reported By: kkm
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16624
Category: Resources/res_monitor
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.1.12
JIRA:
Regression: Yes
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-17 02:23 CST
Last Modified: 2010-01-17 02:23 CST
======================================================================
Summary: soxmerge arguments broken if Monitoring to absolute
path
Description:
Regression - works as documented in 1.6.1.6!
When Monitor() is passed absolute file name and the m flag, the leg
channel recorded is into the specified file. After recording is done,
soxmerge (or another program specified by MONITOR_EXEC) is called with the
file name as argument.
Version 1.6.1.6 behaves as documented.
Version 1.6.1.12 is broken: all 3 soxmerge file paths are prepended with
"/var/spool/asterisk/monitor/". Since they are already absolute, the
resulting syntax is invalid.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-01-17 02:23 kkm New Issue
2010-01-17 02:23 kkm Asterisk Version => 1.6.1.12
2010-01-17 02:23 kkm Regression => Yes
2010-01-17 02:23 kkm SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list