We have two video bridges, using web sockets and splitting participants between bridges in the same meeting and we seem to have a recurring issue.
Examples:
User 1 and 2 has full functionality and can hear and see User 3.
User 3 can see video of all participants but cant hear User 1 and 2. They can however hear User 4.
This seems to happen even if they are on the same videobridge coincidentally.
We also tried two new sessions today with two users.
First meeting User 1 is first to join and it works flawlessly. User 2 can’t hear user 1 however.
Next meeting User 2 is first to join and everything works this time for some reason.
I doubt it is due to who joins first, but still. Seems to be inconsistent.
Any ideas?
Thank you
Can you provide more information about the user’s apps? Are they joining using Safari? Chrome? Edge? Electron? Joining from a mobile browser or mobile Jitsi app?
Also can you provide what version of Jitsi you are running on your servers?
With these details, the community can better help you.
Also getting the ids of the participants that are not heard and the js console logs of the participant that is not hearing them will also help. Thanks.
Thank you
They are all using chrome browser. It doesn’t matter if it’s a PC, chromebook or the smartphone app or mobile browser it seems. The participants affected keep changing in different meetings. A friend of mine might post additional details soon since we’re working together on this but he has access to more stats.
During tests it has been 100% chrome browser (Windows and Chromebooks).
JMS
ii jitsi-meet 2.0.5765-1
ii jitsi-meet-prosody 1.0.4900-1
ii jitsi-meet-turnserver 1.0.4900-1
ii jitsi-meet-web 1.0.4900-1
ii jitsi-meet-web-config 1.0.4900-1
JVB1
ii jitsi-videobridge2 2.1-492-g5edaf7dd-1
JVB2
ii jitsi-videobridge2 2.1-492-g5edaf7dd-1
After setting “startWithVideoMuted: false” and "startWithAudioMuted: false,
" I’ve yet to experience this issue. We ran a non-test meeting with around 55 participants (various browsers, no apps though) earlier this week and everything went smooth - well except for the fact that people forget to turn off their mics.
I have identified one user we can reproduce this issue with every time (when cam/mic defaults to off), otherwise it seems random at best, affecting different users every time. This user is on a Chromebook, stable release channel. I suspect there might be something about the network since this person works from home.
We have seen a similar issue (looking at the logs you provided), and we have added a workaround for it in the latest versions. You can update the latest from unstable today and try it out (we will push it to stable probably next week). If you still reproduce the issue, please send the logs and the info as you did in the previous post. Thank you.