When creating rooms, we recommend creating rooms that use our selective forwarding unit (SFU) mesh for data transfer instead of peer-to-peer rooms. This is done by setting "roomMode": "group"
instead of "normal"
on room creation.
- Our SFU rooms are generally less intensive on network usage, especially when there are more than 2 people in a call or when cloud recording/streaming are being used.
- The mesh can make changes on the fly to participants' calls in order to manage the bandwidth usage of different resources and prioritize audio transmission. For example, if a participant decreases the size of their browser window during a call, the SFU will adjust the resolution of the videos they are receiving in order to optimize the quality of the call.
- Your calls will benefit from the continuous improvements we make to our SFU mesh.
Turning on the pre-call ceremony will conduct a live device and network connectivity test for the participant before they join the call.
Read more about this feature in our release notes.
Turning on low data mode will set the participant's video resolution lower by default. This means there is less data to send and receive, which is helpful with poor network conditions.
With pre-call ceremony enabled, we surface an option for the participant to toggle this mode on themselves before they join the call.
- Disable any ad-blockers, VPN, or privacy extensions. Occasionally browser extensions can interfere with how video calls load, which can manifest as video, audio, or room joining issues.
- Close any unnecessary applications when on the video call. This will free up resources on the computer and improve the quality of the video call.
- Ensure the browser is up to date. Outdated software may have bugs that can cause packet loss and other problems.
- Move closer to the Wifi router or use a wired connection if one is available, as it is less prone to interference than wireless networks.
- Try joining the call with video turned off.
Our support team has also provided some additional suggestions in our Troubleshooting guide.