[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=202323#comment-202323 ] 

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

I agree that most would expect this feature to behave in the way you describe. It's also my experience that a "mute everyone but the admin" feature behaves that way on other non-Asterisk conference systems. However, I do not know the author's original intent.

I've linked issue ASTERISK-18204 where the original author submitted the feature for inclusion.

I'll ping Kevin Reeves to see if he would like to modify the feature with the improvement you request.  Also, you might ping dev list to see who has interest in taking this on. 
                
> 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