[asterisk-bugs] [JIRA] (ASTERISK-24264) ARI: Adding a channel to a holding bridge automatically starts MOH

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24264:
----------------------------------------

There's actually a few problems here:

# A channel that doesn't specify a participant role when joining a bridge is automatically assigned MoH. That's not terrible, but it is probably unexpected. We should probably create a role of "holding_participant" with no sound/options unless the user specifies it.
# Starting MoH on a holding bridge has several problems:
## MoH channels are not currently recognized as being allowed in Stasis and get bounced out
## When they aren't bounced out (which was an easy fix), they also get added as a participant in a holding bridge, and they have MoH started on them. Whoops.
## Looking more carefully, playback channels in a holding bridge also aren't announcers

Generally, if a channel gets put into a Stasis bridge, and that bridge happens to be a holding bridge, we should handle it correctly based on its intended purpose.

> ARI: Adding a channel to a holding bridge automatically starts MOH
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-24264
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24264
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari, Resources/res_ari_bridges
>    Affects Versions: 12.5.0, 13.0.0-beta1
>         Environment: Ubuntu 12.04
>            Reporter: Samuel Galarneau
>
> With Asterisk installed from svn trunk, when adding a channel to a holding bridge using ARI, the MOH starts automatically. A Call to stop MOH returns with an error that the bridge is currently not playing MOH. Removing the channel from the bridge then stops MOH.
> MOH should not start until startMoh has been called manually.



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