3CX GUIDE - web-meeting best practice
From the 3CX Admin Portal:
Like any internet-based solution, the quality of experience relies on sufficient bandwidth (specifically download bandwidth).
Web-meeting works on WebRTC (Web Real-Time Communications), requiring one stream (in both directions) for each connection. Bandwidth usage for participants within the same network will increase exponentially. See schematic below:
Web-meeting works on WebRTC (Web Real-Time Communications), requiring one stream (in both directions) for each connection. Bandwidth usage for participants within the same network will increase exponentially. See schematic below:
|
In this example, there are 5 people on a web-meeting at Location 1 using the same connection (e.g. in the same building) meeting with 4 other people.
Location 1 will require 40MB bandwidth. Bear in mind that there are likely to be many other activities (maybe even simultaneous web-meetings) using the bandwidth at the same time, so bandwidth can very quickly become saturated. |
To get the most out of web-meeting, we recommend the following:
1. Check / optimise your bandwidth
Limit the users of individual connections from one location – if several participants are joining the same call, try to convene in one meeting room to use just one channel (in the above example this will reduce the bandwidth requirement at Location 1 to 8MB).
2. Check your browser
WebRTC is currently supported by Google Chrome, Mozilla Firefox, and Opera, in both their desktop and Android versions. Microsoft’s Internet Explorer and Apple’s Safari have yet to add support for WebRTC. Currently support for these browsers comes in the form of 3rd party plugins.
3. Optimise your web-meeting server selection
Check the nearest MCU (web-meeting server); the system selects the closest by default (based on the IP address of the PBX). So if your PBX has a UK IP address, the web-meeting will automatically choose one of the London servers. However, if the participants are geographically nearer to, say, India, then the meeting organiser can select an MCU closer to the majority of participants – see below:
|
The MCU server can be set to a specific location or use the Automatic option from the Admin portal under Settings>>conferencing
This can be completed when scheduling a Video Conference/web-meeting. You can check the status of the web-meeting servers (MCUs) here: www.status.3cx.net |
4. Reduce the bitrate
Users can reduce/lower the bitrate. The bitrate is the number of bits (data) processed in a unit of time. When it comes to video conferencing, generally the higher the bitrate the better the video quality – but it does require more processing power. Dialling down the bitrate can improve the overall experience for participants. Bitrate is set by default to 1024Kbps – try reducing it.
5. Review your web-meeting settings
Once you’re in a web-meeting you can optimise your meeting settings – see below:
|
Video quality – is set by default to HD Mid (Mbps).
Try reducing this – NB: ALL participants will need to do this. |
|
Users can also check their up-link and down-link capacity from the active web-meeting window from the Settings (Cog icon in upper right hand corner).
This is useful to check what your upload / download capacity is. This is not an issue with web-meeting, but with the available bandwidth. Getting at this data is also useful when troubleshooting issues. Remember there might be multiple simultaneous web-meetings (as well as other activities) taking place, all using up bandwidth. |
|
If one or more participants has a degraded connection, network warnings will appear which can be very distracting, therefore turn this option off.
Click Ignore Network Warnings so this isn’t displayed during the meeting (most especially if you are screen-sharing).
|
Top Tips Summary
• Encourage participants in the same location to use one channel to minimise bandwidth drain (see section 1)
• Reduce bitrate when setting up the web-meeting (see section 4)
• Check you’re using your most local web server (MCU) when setting up the web-meeting (see section 3)
• Review your settings when joining (or during) the web-meeting (see section 5)
• Ensure your device is compatible with supported browsers (see section 2)
• Consider increasing your bandwidth availability in line with your requirements if you intend to use regular web-meetings
• Use a good quality compatible and supported headset when participating in web-meetings for a quality audio experience. Where you can’t use a headset, place your speakers away from your microphone to reduce feedback / echo.
• Reduce bitrate when setting up the web-meeting (see section 4)
• Check you’re using your most local web server (MCU) when setting up the web-meeting (see section 3)
• Review your settings when joining (or during) the web-meeting (see section 5)
• Ensure your device is compatible with supported browsers (see section 2)
• Consider increasing your bandwidth availability in line with your requirements if you intend to use regular web-meetings
• Use a good quality compatible and supported headset when participating in web-meetings for a quality audio experience. Where you can’t use a headset, place your speakers away from your microphone to reduce feedback / echo.
