Update queues.conf.sample documentation.

Update the documentation surrounding the use of MONITOR_EXEC to make it more clear
that it can be used for both Monitor() and MixMonitor() usage.

(closes issue ASTERISK-17413)
Reported by: David Woolley
Patches:
     issue18817_mixmonitor_queues_doc.diff by Michael L. Young (License #5026)

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@346472 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/configs/queues.conf.sample b/configs/queues.conf.sample
index 3c4d8e9b1061dbdbb21bfb17665ee0087bda6827..4c7f0be8cdd602c46ee9c25c89aa76c1bf5121a0 100644 (file)
--- a/configs/queues.conf.sample
+++ b/configs/queues.conf.sample
@@ -375,8 +375,17 @@ monitor-type = MixMonitor
 ;
 ; You can specify a post recording command to be executed after the end of
 ; recording by calling (from the dialplan)
+;
 ;   Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MONITOR_FILENAME} /tmp/^{MONITOR_FILENAME})
 ;
+; or
+;
+;   Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MIXMONITOR_FILENAME} /tmp/^{MIXMONITOR_FILENAME})
+;
+; If you choose to use the latter, you will not be able to switch the monitor-type back to Monitor
+; without changing this in the dialplan.
+;
+;
 ; The command specified within the contents of MONITOR_EXEC will be executed when
 ; the recording is over. Any strings matching ^{X} will be unescaped to ${X} and
 ; all variables will be evaluated just prior to recording being started.