-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users who dial in by phone are not automatically muted when entering the conference via a waiting room #18916
Comments
Hi @KjellWolf, Good catch -- and thanks for the detailed report. I was able to reproduce the issue on one of our test servers. |
Hi @ffdixon, |
Users would expect dial-in users to be muted by default, but we don't have a timeline yet for implementing it. |
In this case, our users expect to be muted when they dial in. Thats why we asking. |
Just as a side note (and sorry for the hijacking, this should probably be a separate issue), I think there is a bit of a problem with muting dial-in users in general:
I think 1) could maybe be solved by playing something like "Press 0 to mute or unmute yourself." after successful pin-entry (but before joining the audio). I can't think of a good solution for 2. I guess dial-in users just need to ask the other participants whether they can be heard or not. |
so, a custom dialplan can answer, mute line, and play message to unmute hit * button. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the bug
Users who dial in by phone are not automatically muted when entering the conference via a waiting room. This happens with all our BBB instances, regardless of the configuration.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The phone user is automatically muted when he enters the conference
Actual behavior
The phone user is not muted when he enters the conference via waiting room
Screenshots
Not applicable
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: