[asterisk-bugs] [JIRA] (ASTERISK-22006) bridges/ast_bridge_playfile: Use a bridge technology callback to resume entertainment sounds.

[Digium Subversion (JIRA)]

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

Digium Subversion closed ASTERISK-22006.
----------------------------------------

    Resolution: Fixed
    
> bridges/ast_bridge_playfile: Use a bridge technology callback to resume entertainment sounds.
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22006
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22006
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_bridgewait, Core/Bridging, Resources/res_parking
>    Affects Versions: SVN, 12
>            Reporter: Jonathan Rose
>            Assignee: Jonathan Rose
>              Labels: Asterisk12
>      Target Release: 12
>
>
> Currently if a channel is listening to music on hold or ringing in a holding bridge and playfile is invoked on that channel, the behavior is a bit wonky. After the announcement is finished, if music on hold should be playing on the channel, it will start music on hold back up without reverence to what music on hold class option was applied in the channel's participant role. For ringing it's a bit worse. Ringing isn't resumed at all and the user will hear silence when the announcement is finished.
> I discussed a potential fix with Richard. The bridge technologies can specify a callback to execute after ast_bridge_channel_playfile is finished which can then evaluate what music on hold settings or indications need to be applied while having access to relevant information such as bridge role options. The core variant of this fix would probably be more or less the same as the current MOH flag check to restart music on hold while the holding bridge in particular would check roles as needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira