[asterisk-bugs] [Asterisk 0013084]: Once enabled the recording/monitoring will not disable
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jul 15 16:16:41 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13084
======================================================================
Reported By: elbriga
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13084
Category: Applications/app_queue
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.4.21
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 07-15-2008 15:55 CDT
Last Modified: 07-15-2008 16:16 CDT
======================================================================
Summary: Once enabled the recording/monitoring will not
disable
Description:
The field "monitor-format" is used to control weather or not to record the
queue calls. When I start my asterisk (tested on the last version,
1.4.21-1) with this field empty (in pgsql realtime) it wil not record the
queue call. OK.
Then I set the monitor-format field to 'wav49', make a call, and it will
record the call with the MixMonitor App. OK.
Now it's the problem! When I reset the field (empty string value) and make
the same call, the MixMonitor App still starts and record the call, and
will keep recording, no matter the value of the monitor-format field, until
I unload/load the app_queue module or restart the Asterisk.
======================================================================
----------------------------------------------------------------------
putnopvut - 07-15-08 16:16
----------------------------------------------------------------------
I see what the problem is. If an option is a zero-length string, then
app_queue will not attempt to set the value. There are a few potential ways
to accomplish this. I need to investigate which is the least likely to
cause issues.
Thanks for the bug report!
Issue History
Date Modified Username Field Change
======================================================================
07-15-08 16:16 putnopvut Note Added: 0090312
======================================================================
More information about the asterisk-bugs
mailing list