[asterisk-bugs] [Asterisk 0016590]: [patch] Monitor resumes recording after SIP transfer despite StopMonitor() having been called

Asterisk Bug Tracker noreply at bugs.digium.com
Sun Apr 25 13:14:02 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16590 
====================================================================== 
Reported By:                kkm
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16590
Category:                   Resources/res_monitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                       SWP-711 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 239389 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-01-12 14:17 CST
Last Modified:              2010-04-25 13:14 CDT
====================================================================== 
Summary:                    [patch] Monitor resumes recording after SIP transfer
despite StopMonitor() having been called
Description: 
During call setup, Monitor() with the "b" flag is called.

When a call reenters PBX after transfer, dialplan calls StopMonitor()
application. Recording is stopped, and a post-recording program (soxmerge
or other if overridden) is called. This is the expected behavior.

Unexpected part: After the call is bridged again, recording resumes with
the same file name, overwriting the previous recording.
====================================================================== 

---------------------------------------------------------------------- 
 (0120868) svnbot (reporter) - 2010-04-25 13:14
 https://issues.asterisk.org/view.php?id=16590#c120868 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 258777

_U  branches/1.6.0/
U   branches/1.6.0/res/res_monitor.c

------------------------------------------------------------------------
r258777 | tilghman | 2010-04-25 13:14:01 -0500 (Sun, 25 Apr 2010) | 20
lines

Merged revisions 258776 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r258776 | tilghman | 2010-04-25 13:12:14 -0500 (Sun, 25 Apr 2010) | 13
lines
  
  Merged revisions 258775 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r258775 | tilghman | 2010-04-25 13:09:05 -0500 (Sun, 25 Apr 2010) | 6
lines
    
    When StopMonitor is called, ensure that it will not be restarted by a
channel event.
    (closes issue https://issues.asterisk.org/view.php?id=16590)
     Reported by: kkm
     Patches: 
           resmonitor-16590-trunk.239289.diff uploaded by kkm (license
888)
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=258777 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-25 13:14 svnbot         Checkin                                      
2010-04-25 13:14 svnbot         Note Added: 0120868                          
======================================================================




More information about the asterisk-bugs mailing list