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

[Asterisk Bug Tracker]

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 16:50 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0135695) jkister (reporter) - 2011-06-03 16:50
 https://issues.asterisk.org/view.php?id=19407#c135695 
---------------------------------------------------------------------- 
i asked the same question on asterisk-users - there's a devcycle that
sometimes takes an abnormally long time to get fixes released.

since the patch was not checked in/approved *before* 1.8.4-rc1 was
released, it waits until 1.8.5-rc1.

see
http://blogs.asterisk.org/2010/09/02/the-monthly-asterisk-release-cycle/
for the exact details. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-06-03 16:50 jkister        Note Added: 0135695                          
======================================================================