[asterisk-bugs] [JIRA] (ASTERISK-24798) MixMon saves to the incorrect filename

[Michael L. Young (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224962#comment-224962 ] 

Michael L. Young commented on ASTERISK-24798:
---------------------------------------------

Okay, thanks for confirming.

Yes, the documentation could be improved upon.  As I mentioned above, this has been the behavior of MixMonitor for as long as I can remember.

> MixMon saves to the incorrect filename
> --------------------------------------
>
>                 Key: ASTERISK-24798
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24798
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.1.1
>            Reporter: xrobau
>            Assignee: Michael L. Young
>
> I'm not sure how far back this one goes, but running mixmon with these params:
> {code}
> MixMonitor("2015/02/17/internal-300-303-20150217-051706-1424114226.982.wav49,ai(LOCAL_MIXMON_ID),/tmp/post.sh")
> {code}
> Results in the file being SAVED as internal-300-303-20150217-051706-1424114226.982.WAV
> Note the different suffix.  Mixmon itself seems unaware of this, however, as $\{MIXMONITOR_FILENAME\} reports it correctly:
> {code}
>  Set("SIP/303-00000070", "__REC_FILENAME=/var/spool/asterisk/monitor/2015/02/17/internal-300-303-20150217-051706-1424114226.982.wav49") in new stack
> {code}
> {code}
> [root at localhost callrecording]# ls -al /var/spool/asterisk/monitor/2015/02/17/internal-300-303-20150217-051706-1424114226.982.*
> -rw-rw---- 1 asterisk asterisk 3765 Feb 17 05:17 /var/spool/asterisk/monitor/2015/02/17/internal-300-303-20150217-051706-1424114226.982.WAV
> [root at localhost callrecording]#
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)