asterisk users - Aug 2009 - Post recording command to be executed after the end of recording

Hi all

Does anybody know where this command is supposed to go?
Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MONITOR_FILENAME}
/tmp/^{MONITOR_FILENAME})

In the queues.conf file it talks about it. So I naturally thought
after I set up my monitor with

monitor-format = wav
monitor-type = MixMonitor

That I could put a lame command in there to convert and move the file
elsewhere for backup with these:

(as explained in the queues.conf file)

; ----------------------- TYPE MIXMONITOR OPTIONS -----------------------------
;
;
; You can specify the options supplied to MixMonitor by calling
;   Set(MONITOR_OPTIONS=av(<x>)V(<x>)W(<x>))
; The 'b' option for MixMonitor (only save audio to the file while
bridged) is
; implied.
;
; You can specify a post recording command to be executed after the end of
; recording by calling
;   Set(MONITOR_EXEC=mv
/var/spool/asterisk/monitor/^{MONITOR_FILENAME}
/tmp/^{MONITOR_FILENAME})
;
; 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.

However my script was never being ran.

I thought it was a big and logged:
https://issues.asterisk.org/view.php?id=15742

They then got back saying it wasn't a bug at all and that it needs to be set
the extensions.ael / conf / dialplan.

This is weird to me, as where does one set this as we want it to run post
recording not before recording. So is it just before you enter the queue on
the dial plan? as if this is true and it is some global setting then surely
it will mean that you can't run this by queue or context and that it will be
the same for all queues.

I'm confused :-)

It seems like a great option as you can nicely convert it to MP3 and move it
into a backup and have it run when the file is saved by asterisk rather than
a shell script ran by a cron job that is a bit nasty but would work too. I
would prefer to do it all at the asterisk level though as it is cleaner.

What say the experts :) does anybody agree with me that having the options
mentioned in the queue.conf is a documentation bug if not a software? I am
not sure if I should reopen it as so or maybe to suggest the doc in the
queues.conf says "you need to set this in the dial plan not here" or
something.

Dave
-- 
_________________________________________

Mr. David Anthony O'Reilly, M.Sc, B.Sc

Researcher @ MISL Group, University College Cork (Current)

M.Sc MOB Postgraduate @ University College Cork - M.Sc (Mobile Networking
and Computing) - 2009

Computer Science Graduate of The University of Dublin, Trinity College -
B.Sc (Computer Science) 2008

Email: oreillda at tcd.ie    /    dor3 at student.cs.ucc.ie

_________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090820/fd983892/attachment-0001.htm

On 21/08/09 1:35 AM, D?ibh?ad Antoine O'Reilligh M.Sc B.Sc
wrote:
> Hi all
>
> Does anybody know where this command is supposed to go?
> Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MONITOR_FILENAME}
/tmp/^{MONITOR_FILENAME})
The idea is that you set the variable called MONITOR_EXEC before you go 
into the queue.

It will check for the presence of this and if there is one it will run 
it after the call has finished.

So, for example:

exten => s,1,Answer()
exten => s,n,Set(MONITOR_EXEC=something)
exten => s,n,Queue(support)

-- 
Cheers,

Matt Riddell
Director
_______________________________________________

http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer)
http://www.venturevoip.com/c3.php (ConduIT3 PABX Systems)