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

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28361:
--------------------------------------

    Summary: app_confbridge: Missing MIXMONITOR_FILENAME in ConfBridge AMI  (was: Missing MIXMONITOR_FILENAME in ConfBridge AMI)

> app_confbridge: 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)