in this thread we’ll communicate the actions we’re taking regarding the issues some users have been experiencing when connecting to meet.coop’s service in the last few days.
To summarize, some users are unable to complete the echo test, receiving either a timeout error or a “1006” error from the BigBlueButton HTML5 client. They are then connected to the room, but can’t send audio to the other participants. This is what we have been able to find out so far:
- The issue can be reproduced on the latest versions of Chrome for Android (96.0.4664.104), Windows (96.0.4664.110) and MacOS (96.0.4664.110). It is unclear whether the issue affects other, slightly older versions of Chrome. Chrome for Linux seems not to be affected.
- Some users have reported a similar issue on Safari for iOS, but we’ve been unable to reproduce it so far.
This issue has been reported by other users both in BigBlueButton’s  and Chrome’s  issue trackers. It is apparently related to a the deprecation  of the Plan B method that Chrome was using to connect to WebRTC until recently. A similar issue has been reported by users of other videoconferencing platforms that use WebRTC, such as Jitsi . This issue does not affect the most recent BigBlueButton releases.
There are a couple of client-side workarounds for the issue described above:
- The first one is to use a different browser. Recent versions of Firefox, Edge (for Windows) and Safari (for MacOS) are unaffected as far as we can tell. Several users reported being able to connect normally to the service after switching to one of those alternative browsers.
- Another workaround is to connect using Chrome, but connect to the audio stream using the dial-in feature instead of enabling the microphone on the browser.
We understand that these workarounds won’t work for all users, for example when having a session with a larger group of new participants, which may not be able to quickly change browsers or switch to a dial-in channel.
Therefore, the tech.circle is already working on the deployment of a new server running a more recent version (2.3) of BigBlueButton. This will not be a full upgrade of meet.coop’s infrastructure, which we were planning for January, but a temporary solution to mitigate this issue. In the coming hours we’ll let you know how to access this alternative service.
Again, we want to thank you all for your patience and your feedback.
 Chrome browsers new version microphone issue · Issue #13936 · bigbluebutton/bigbluebutton · GitHub
 1280590 - chromium - An open-source project to help move the web forward. - Monorail
 [WebRTC] Deprecate and Remove Plan B - Chrome Platform Status
 Jitsi stopped working about a week ago - #8 by jbg - Install & Config - Jitsi Community Forum - developers & users