[Home]

Summary:ASTERISK-28632: ConfBridge spawns record_command before MixMonitor ends
Reporter:Bill Kervaski (bkervaski)Labels:
Date Opened:2019-11-25 11:24:13.000-0600Date Closed:2019-12-19 12:00:02.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/app_confbridge
Versions:16.6.2 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Linux (all)Attachments:
Description:Set(CONFBRIDGE(bridge,record_conference)=yes)
Set(CONFBRIDGE(bridge,record_file_timestamp)=no)
Set(CONFBRIDGE(bridge,record_file)=filename.wav)
Set(CONFBRIDGE(bridge,record_command)=mycommand)

Results in the command running before MixMonitor ends and closes the file:

== Executing [mycommand]
   -- <CBAnn/test-0000009a;1> Playing 'confbridge-leave.gsm' (language 'en')
   -- Channel CBAnn/test-0000009a;2 left 'softmix' base-bridge <6229229c-72dc-460b-9913-d7905925e988>
== End MixMonitor Recording CBRec/test-00000006
Comments:By: Asterisk Team (asteriskteam) 2019-11-25 11:24:14.133-0600

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) 2019-11-26 10:35:19.678-0600

[~bkervaski],

bq. Results in the command running before MixMonitor ends and closes the file

The code that prints these two messages:

{noformat}
== Executing [mycommand]
== End MixMonitor Recording CBRec/test-00000006
{noformat}

Is run _after_ the files have been closed. Are you having a specific problem or were you just confused by the log messages?
By: Bill Kervaski (bkervaski) 2019-11-26 11:19:49.797-0600

Yes, a specific problem.

The file seems to remain locked for some small amount of time until after the command is executed.  I've had to add a delay in the post-processing script to give it time to close or whatever is happening internally.

This doesn't happen when using MixMonitor from the dialplan, the post processing script can access the file contents immediately.  I'm assuming it's something to do with how ConfBridge is using MixMonitor, perhaps it's hanging on to the file for some reason.

I haven't tested this with any other version than 16.6.2 but happy to help if you have some things you want me to try.


By: Sean Bright (seanbright) 2019-11-26 12:04:14.273-0600

bq. The file seems to remain locked for some small amount of time until after the command is executed.

How does this manifest? How do you know it is locked?
By: Sean Bright (seanbright) 2019-12-04 16:26:44.801-0600

Hi [~bkervaski], just making sure you saw the above question. Curious what you are seeing on your end.
By: Asterisk Team (asteriskteam) 2019-12-19 12:00:01.982-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines