[asterisk-bugs] [JIRA] (ASTERISK-20987) non-admin users, who join muted conference are not being muted

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-20987:
-----------------------------------------

Looks like some good ideas. 

I can't imagine a use case where you would only want to mute the current participants, and not any joining participants. However having the option seems like a good thing as long as it doesn't make things overly complex.

I'm not a developer either. You probably want to grab the interest of a developer to work on this. I recommend you share those ideas on the dev list, or in #asterisk-dev.
                
> non-admin users, who join muted conference are not being muted
> --------------------------------------------------------------
>
>                 Key: ASTERISK-20987
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20987
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 11.2.0
>         Environment: debian squeeze 64-bit
>            Reporter: hristo
>            Severity: Minor
>
> If an admin user sets global conference mute via 'admin_toggle_mute_participants' it only affects users, who are currently in the conference. Any new (or reconnecting) non-admin users, who join the conference after that are not being muted.
> I would certainly expect that once a conference is muted for all non-admin users, then it must remain muted, even when for example a user drops out of the conference and reconnects or new (late) users connect after it has started.
> This would have been trivial to resolve in the dialplan if the conference muted/unmuted state was somehow exposed via a variable or function (like CONFERENCE_INFO or similar), but without this I would consider it a bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira