-
Notifications
You must be signed in to change notification settings - Fork 323
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
Video and Audio Call Limit #1094
Comments
I too am interested in increasing the participant limit for on-prem installations. |
Currently, for N participants, there are connections established between participants. So for 10 participants, there are 45 connections established, which require individual encryption/decryption and enough upstream/downstream bandwidth (every participant needs to encrypt/decrypt individually for every other participant and upload/download 9 streams). In case one of those 45 connections breaks, some person will no longer hear/see one other person, while other people are unaware of the problem. So unless all participants have really good hardware and really good internet connections, there will be problems. That being said, feel free to tweak https://github.com/wireapp/wire-web-config-default/blob/master/wire-webapp/.env.defaults#L84 (add something to We're aware of this problem, and a solution to allow more participants (keeping end-to-end-encryption) without laptops melting is being worked on. |
Thank you very much of the great answer. What is the approach currently being worked? Some kind of MCU or SFU? |
SFU, as MCUs don't work well with end-to-end encryption. We're hoping to make this work using WebRTC Insertable Streams once they stabilize. |
My question:
The documentation and website claims that Video Calls are restricted to 4 participants, and Audio Calls to 10. I'd like to ask what causes this limitation and if it is feasible to have a Video Call with up to 10-12 people. Is this something that can be configured or is it a deeper rooted, technical limitation?
The text was updated successfully, but these errors were encountered: