[asterisk-bugs] [JIRA] (ASTERISK-22489) Document Confbridge record_file appending file name with time stamp. Behavior introduced in r381702

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-22489 at 9/11/13 5:52 PM:
------------------------------------------------------------------

I verified that the behavior you describe is accurate.

Though, it does happen with the record_file option regardless of whether you set it via the *CONFBRIDGE* function, or set it in the *confbridge.conf* file itself.

[Edit - removed some confusion here. I somehow forgot we were setting the path specifically with the CONFBRIDGE function call. :) ]

I wasn't sure that a timestamp was always appended, so I looked through some commits and after talking with Kevin Harwell I found that this behavior was added in rev [381702|http://svnview.digium.com/svn/asterisk?view=revision&revision=381702] for a bug fix.

bq. I find no evidence of this being a new feature. If it is, the confbridge.conf sample configuration file needs to be updated to include the new available features. If it is not a new feature and it is a bug I am ready to assist getting it fixed.

I don't think the code needs to change as this behavior was introduced to fix a bug, but we do need to document the behavior, both in the .conf sample file and the XML documentation in the source (for Asterisk 12).

As a note, if you need to track where the file is going to end up during your interaction with Asterisk you can read the final filename from the channel variable *MIXMONITOR_FILENAME* on the *ConfBridgeRecorder* channel created during the ConfBridge.
                
      was (Author: rnewton):
    I verified that the behavior you describe is accurate.

Though, it does happen with the record_file option regardless of whether you set it via the *CONFBRIDGE* function, or set it in the *confbridge.conf* file itself. There is a difference between the two, and that is the location the file gets recorded to, {{/var/spool/asterisk/confbridge}} from the *CONFBRIDGE* function and {{/var/spool/asterisk/monitor}} when set in the *confbridge.conf* file which adds to the confusion. I'll open a bug report for that.

I wasn't sure that a timestamp was always appended, so I looked through some commits and after talking with Kevin Harwell I found that this behavior was added in rev [381702|http://svnview.digium.com/svn/asterisk?view=revision&revision=381702] for a bug fix.

bq. I find no evidence of this being a new feature. If it is, the confbridge.conf sample configuration file needs to be updated to include the new available features. If it is not a new feature and it is a bug I am ready to assist getting it fixed.

I don't think the code needs to change as this behavior was introduced to fix a bug, but we do need to document the behavior, both in the .conf sample file and the XML documentation in the source (for Asterisk 12).

As a note, if you need to track where the file is going to end up during your interaction with Asterisk you can read the final filename from the channel variable *MIXMONITOR_FILENAME* on the *ConfBridgeRecorder* channel created during the ConfBridge.
                  
> Document Confbridge record_file appending file name with time stamp. Behavior introduced in r381702
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22489
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22489
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 11.2.2, 11.5.1
>         Environment: Centos 6.4
>            Reporter: Jonathan White
>
> I am setting the confbridge record file name with the following dial plan command
> {noformat}
> same =>n,Set(CONFBRIDGE(bridge,record_file)=/var/spool/asterisk/confbridge/${file})
> {noformat}
> The result being /var/spool/asterisk/confbridge/test.wav as seen on the console
> but the file which is produced comes out as /var/spool/asterisk/confbridge/test-1378328852.wav 
> The last part of the file name appears to be a random number.
> In previous versions of confbridge the file would have been the name I had told it to be
> /var/spool/asterisk/confbridge/test.wav
> I find no evidence of this being a new feature. If it is, the confbridge.conf sample configuration file needs to be updated to include the new available features. If it is not a new feature and it is a bug I am ready to assist getting it fixed.
> [Edit by Rusty Newton - added text below:]
> I don't think the code needs to change as this behavior was introduced to fix a bug, but we do need to document the behavior, both in the .conf sample file and the XML documentation in the source (for Asterisk 12). See comments for more info.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira