[asterisk-bugs] [Asterisk 0019407]: When using chanspy on a monitored channel the file is never closed.

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jun 3 14:36:53 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19407 
====================================================================== 
Reported By:                akavan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19407
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-06-03 12:54 CDT
Last Modified:              2011-06-03 14:36 CDT
====================================================================== 
Summary:                    When using chanspy on a monitored channel the file
is never closed.
Description: 
When you use chanspy to listen in on a channel that is being recorded by
Monitor, when the call is finished Asterisk does not close the recording. 
If you have a cleanup script from monitor_exec it never gets called, and
asterisk leaves the file open so it continues to use up disk space.
====================================================================== 

---------------------------------------------------------------------- 
 (0135690) akavan (reporter) - 2011-06-03 14:36
 https://issues.asterisk.org/view.php?id=19407#c135690 
---------------------------------------------------------------------- 
Actually I take that back.  This looks like it was fixed months ago, but it
isn't in any version of asterisk yet?  At least looking at the patch from
back then it is not in 1.8.4.2.

Does anyone know when this patch will actually be included? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-06-03 14:36 akavan         Note Added: 0135690                          
======================================================================




More information about the asterisk-bugs mailing list