Summary:	ASTERISK-28361: app_confbridge: Missing MIXMONITOR_FILENAME in ConfBridge AMI
Reporter:	Daniel McFarlane (DanSTech)	Labels:
Date Opened:	2019-03-28 12:20:08	Date Closed:
Priority:	Minor	Regression?	Yes
Status:	Open/New	Components:	Applications/app_confbridge
Versions:	16.2.0 16.2.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOS 7.5.1804	Attachments:
Description:	In Asterisk 11 a MIXMONITOR_FILENAME would be received within an AMI VarSet Event, following a ConfbridgeStart Event. This is no longer the case in Asterisk 16.2.1 Note: While current documentation (i.e.: https://wiki.asterisk.org/wiki/display/AST/ConfBridge+AMI+Actions) says an identical MIXMONITOR_FILENAME SetVar Event should be received after a ConfbridgeStartRecord command, but this does not occur when testing. Even issuing a GetVar request, to verify the MIXMONITOR_FILENAME on receipt of a ConfbridgeRecord Event, returns MIXMONITOR_FILENAME as an empty variable. It seems that ConfBridgeRecorder Channel identifiers have been replaced by a new bridging approach within AMI commands in Asterisk 16.  If the MIXMONITOR_FILENAME was dropped in the process, with no substitute, then this may be an oversight.  Here's the problem: Without the MIXMONITOR_FILENAME (or similar) SetVar event, it’s impossible to know the exact date timestamp added to the end of the the supplied record_file name by Asterisk. This is needed to keep track of this in an external database, which can then be searched to the end of being able to select and play back a ConfBridge recording.
Comments:	By: Asterisk Team (asteriskteam) 2019-03-28 12:20:09.574-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Sean Bright (seanbright) 2020-09-23 14:45:10.526-0500 This is due to [this block of code|https://github.com/asterisk/asterisk/blob/389b2ab39bbcbfca796d90699335d6c0ddbc6a0e/main/manager_channels.c#L496-L498]: {noformat} if (snapshot->base->tech_properties & AST_CHAN_TP_INTERNAL) {        return NULL; } {noformat} Which is preventing the {{VarSet}} event from being created because the {{CBRec}} channel is "internal." By: Ian McLauchlan (ianmac28sco) 2021-02-25 04:08:40.297-0600 I have found this too. I have ported our system over to Confbridge from Meetme. The Meetme conference start event reports the recording filename. Neither ConfbridgeRecord nor ConfbridgeStart events report the filename. So if the timestamp option is enabled, the file records ok to a timestamped filename, but the application has no way of knowing what the recording filename is. A work around is to generate the filename in the dialplan: {quote}    same => n,Set(CONFBRIDGE(bridge,record_conference)=yes)    same => n,Set(RECORD_FILENAME=confbridge-rec-cv$\{CONFID\}-$\{EPOCH\})    same => n,Set(CONFBRIDGE(bridge,record_file)=$\{RECORDINGS_FOLDER\}$\{RECORD_FILENAME\}.wav)    same => n,Set(CONFBRIDGE(bridge,record_file_timestamp)=no)    same => n,UserEvent(ConfBridgeRecordFile,ConfName:cv$\{CONFID\},Filename:$\{RECORD_FILENAME\},Format:wav)    same => n,ConfBridge(cv$\{CONFID\},,user,user_menu) {quote} Use a UserEvent to fire an event to the application with the filename before the conference is started. Then pass the filename to CONFBRIDGE and start the conference. It is a bit longwinded and could be avoided if the filename was passed in one or both of the Confbridge events above.