asterisk users - May 2011 - Asterisk 1.6: Custom Name for Recordings file

Hi,

I have latest Elastix 64 bit setup and running fine (Asterisk 1.6.2.13)

I would like to customize the file name of call recordings:
/var/spool/asterisk/monitor/20110511-110858-1305126538.912.wav

I would like to include the extension number in the file name.

Did a lot of googling but not much help.

Pls advice.

Thx
Sans
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110513/7fb1d408/attachment.htm>

> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of
> RSCL Mumbai
> Sent: Friday, May 13, 2011 1:32 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [asterisk-users] Asterisk 1.6: Custom Name for
> Recordings file
>
> Hi,
>
> I have latest Elastix 64 bit setup and running fine (Asterisk
> 1.6.2.13)
>
> I would like to customize the file name of call recordings:
> /var/spool/asterisk/monitor/20110511-110858-1305126538.912.wav
>
> I would like to include the extension number in the file name.
>
> Did a lot of googling but not much help.
>
> Pls advice.
See the "fname_base" information below.

===============================
pbx*CLI> core show application monitor

  -= Info about application 'Monitor' =-

[Synopsis]
Monitor a channel.

[Description]
Used to start monitoring a channel. The channel's input and output voice
packets are logged to files until the channel hangs up or monitoring is stopped
by the StopMonitor application.
By default, files are stored to "/var/spool/asterisk/monitor/".
Returns
'-1' if monitor files can't be opened or if the channel is already
monitored,
otherwise '0'.

[Syntax]
Monitor([file_format[:urlbase]][,fname_base[,options]])

[Arguments]
file_format
    optional, if not set, defaults to 'wav'
fname_base
    if set, changes the filename used to the one specified.
options
    m: when the recording ends mix the two leg files into one and delete
    the two leg files. If the variable ${MONITOR_EXEC} is set, the application
    referenced in it will be executed instead of soxmix/sox and the raw leg
    files will NOT be deleted automatically. soxmix/sox or ${MONITOR_EXEC}
    is handed 3 arguments, the two leg files and a target mixed file name
    which is the same as the leg file names only without the in/out designator.
    If ${MONITOR_EXEC_ARGS} is set, the contents will be passed on as
    additional arguments to ${MONITOR_EXEC}. Both ${MONITOR_EXEC} and the
    Mix flag can be set from the administrator interface.

    b: Don't begin recording unless a call is bridged to another channel.

    i: Skip recording of input stream (disables 'm' option).

    o: Skip recording of output stream (disables 'm' option).


[See Also]
StopMonitor()