[asterisk-bugs] [Asterisk 0016590]: Monotor resumes recording after SIP transfer despite StopMonitor() having been called
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jan 12 14:17:51 CST 2010
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=16590
======================================================================
Reported By: kkm
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16590
Category: Resources/res_monitor
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 239389
Request Review:
======================================================================
Date Submitted: 2010-01-12 14:17 CST
Last Modified: 2010-01-12 14:17 CST
======================================================================
Summary: Monotor 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-01-12 14:17 kkm New Issue
2010-01-12 14:17 kkm Asterisk Version => SVN
2010-01-12 14:17 kkm Regression => No
2010-01-12 14:17 kkm SVN Branch (only for SVN checkouts, not tarball
releases) => trunk
2010-01-12 14:17 kkm SVN Revision (number only!) => 239389
======================================================================
More information about the asterisk-bugs
mailing list