Known Issues

These are the known issues that we are working on resolving.

Known issues/bugs

These are the known issues that we are working on resolving.

• Audible notifications for chat: When you enable audio alerts for chat, the alerts only appear if the Public Chat panel is hidden.
• Safari users not hearing audio after returning from breakout room.  The latest version of the Safari -- both Safari on the desktop and Safari Mobile on iPad and iPhone -- browser blocks access to the speaker when the returns from the main room.  Users can transmit using their microphone, but won't hear any audio.  The workaround is to quit Safari and rejoin the main session after returning from a breakout room. (2020-11-05) This issue is now fixed in iOS 14.2.
• iPad battery drains when using BigBlueButton.  When the iPad is displaying videos (webcams and screen share), it takes more CPU resources for the iPad to decode the video.  To offset this, we recommend users keep their iPad plugged in while using BigBlueButton.
• Audio is sometimes out of sync with webcam video.  In BigBlueButton, the audio and video travel through two different channels.  In some recordings, they can be about a second out of sync.  We are investigating further as to why this is happening.
• Meeting Statistics All the times in the statistics reports are currently in UTC.  We are working on automatically adjusting the times to the users local timezone. 
• Connectivity issues with Spectrum Internet.  We've seen issues with some customers of Spectrum Internet getting periodically disconnected after recent network updates.  The fix is to disable IPV6 on their router.
• iOS 14.5+ errors with webcams and screen share. On BigBlueButton 2.2 if you have upgraded you iOS device to version 14.5+ you will not be able to connect your webcam and screen share's will not load.  This is fixed in BBB 2.3 which is to be released soon.

If you encounter an issue that is not listed above, please let us know by submitting a support ticket to support@blindsidenetworks.com with the following information:

• Description of the bug or steps to take to reproduce 
• Screen shots; if able to capture
• Title, date and time of the session where issue was encountered