[asterisk-bugs] [Asterisk 0016624]: [regression] soxmerge arguments broken if Monitoring to absolute path

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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:                       SWP-741 
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 22:07 CST
====================================================================== 
Summary:                    [regression] 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0116872) kkm (reporter) - 2010-01-18 22:07
 https://issues.asterisk.org/view.php?id=16624#c116872 
---------------------------------------------------------------------- 
Yes, it seems to me that the issue should have been fixed by the patch
[235943] merged from [235941] on ^/branches/1.4 from [235940]. Perhaps my
report is duplicate, see https://issues.asterisk.org/view.php?id=16376,
https://issues.asterisk.org/view.php?id=16377. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-18 22:07 kkm            Note Added: 0116872                          
======================================================================