[Home]

Summary:ASTERISK-22489: Document Confbridge record_file appending file name with time stamp. Behavior introduced in r381702
Reporter:Jonathan White (londonnet)Labels:
Date Opened:2013-09-09 16:38:59Date Closed:2014-11-15 05:26:07.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:11.2.2 11.5.1 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Centos 6.4Attachments:
Description: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.
Comments:By: Rusty Newton (rnewton) 2013-09-11 17:17:25.926-0500

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.

By: Jonathan White (londonnet) 2013-09-12 04:58:34.434-0500

Being able to read back the actual file name resolves my issue and tidy's my scripts. This is good news.

From some of the research I have done to try and find answers to this problem there appears to be other additional features in confbridge not yet documented. It would be great if these can be captured at the same time.

Thanks for the support

By: Jonathan White (londonnet) 2013-09-12 14:49:37.465-0500

Actually, now I have tried to implement the use of the variable MIXMONITOR_FILENAME I find it is not suitable. There is never an opportunity to retrieve the file name in the dialplan as entering the conference starts recording and by the time you exit and could possibly execute a command the recording has already stopped and thus the file name lost.

Perhaps naming the files statically and using a variable to timestamp for those that need it or expose a method of extracting the file name before or after the conference has finished After is better as you may have multiple files

Is it worth renaming this log back to being a bug?

By: Matt Jordan (mjordan) 2013-10-03 20:05:08.693-0500

Nope. That would be an improvement and/or a new feature.

By: Will McCown (flynwill2) 2013-10-09 15:48:59.144-0500

I'll second Jonathan's request.

I am in the process of migrating our existing meetme() based conferencing to confbridge() and also ran into this problem.  We had built a system where a unique filename was generated (by adding a timestamp) and that filename recorded in a userfield in the cdr.  A periodic cron script then queries the cdr database and retrieves the name of the recording, converts the wave to mp3 then emails it to the owner of the conference room.  We can certainly modify the script to do a wildcard search for recordings in the spool directory instead, but that is going to take some work.


By: Jonathan White (londonnet) 2014-11-15 05:26:07.902-0600

In the end I also used a wildcard search. It's OK and just as much effort