[asterisk-bugs] [JIRA] (ASTERISK-28361) Missing MIXMONITOR_FILENAME in ConfBridge AMI

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Mar 28 12:21:52 CDT 2019


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

Asterisk Team commented on ASTERISK-28361:
------------------------------------------

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.

> Missing MIXMONITOR_FILENAME in ConfBridge AMI
> ---------------------------------------------
>
>                 Key: ASTERISK-28361
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28361
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 16.2.0, 16.2.1
>         Environment: CentOS 7.5.1804
>            Reporter: Daniel McFarlane
>            Severity: Minor
>
> 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.



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



More information about the asterisk-bugs mailing list