[asterisk-bugs] [Asterisk 0018817]: MONITOR_FILENAME should be MIXMONITOR_FILENAME in documentation of MONITOR_EXEC
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 16 08:07:13 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18817
======================================================================
Reported By: davidw
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18817
Category: Documentation
Reproducibility: N/A
Severity: text
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!): 307791
Request Review:
======================================================================
Date Submitted: 2011-02-15 11:23 CST
Last Modified: 2011-02-16 08:07 CST
======================================================================
Summary: MONITOR_FILENAME should be MIXMONITOR_FILENAME in
documentation of MONITOR_EXEC
Description:
In queues.conf.sample, both the variable used to force the filename for
MixMonitor and the variable that gets set to the actual filename are shown
as MONITOR_FILENAME. However, the latter is actually MIXMONITOR_FILENAME,
as set by this line in app_mixmonitor.c:
apps/app_mixmonitor.c: pbx_builtin_setvar_helper(chan,
"MIXMONITOR_FILENAME", args.filename);
and as indicated in the API meta-data:
<variable name="MIXMONITOR_FILENAME">
<para>Will contain the filename
used to record.</para>
</variable>
======================================================================
----------------------------------------------------------------------
(0132025) elguero (reporter) - 2011-02-16 08:07
https://issues.asterisk.org/view.php?id=18817#c132025
----------------------------------------------------------------------
Maybe I am missing something?
MONITOR_FILENAME is a variable. All it will contain is the name that you
want the recording to be saved as.
If you look above the line I posted in the last comment, the documentation
mentions setting MONITOR_FILENAME. The example on how to use the
MONITOR_EXEC variable, shows how you can set a command to be run (which
moves the recording to the tmp directory) after the recording has ended.
MIXMONITOR_FILENAME is of great use. MixMonitor is not used just for
queues.
This is turning into an asterisk-users conversation. Basically, I do not
see any bugs at all or mis-information.
Issue History
Date Modified Username Field Change
======================================================================
2011-02-16 08:07 elguero Note Added: 0132025
======================================================================
More information about the asterisk-bugs
mailing list