[asterisk-bugs] [Asterisk 0016624]: soxmerge arguments broken if Monitoring to absolute path
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 18 10:42:53 CST 2010
The following issue requires your FEEDBACK.
======================================================================
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: feedback
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-18 10:42 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.
======================================================================
----------------------------------------------------------------------
(0116824) lmadsen (administrator) - 2010-01-18 10:42
https://issues.asterisk.org/view.php?id=16624#c116824
----------------------------------------------------------------------
I believe a change went in recently about paths with Monitor() -- can you
try updating to the latest 1.6.1 branch and see if it has already been
resolved? If not, please provide information about how to reproduce this
issue (extensions.conf, sip.conf, etc...) along with the console output
with debugging enabled in logger.conf showing the issue present.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-18 10:42 lmadsen Note Added: 0116824
2010-01-18 10:42 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list