Find out More About the Network Environment Needed for eyeson
What to do if the connection is poor?
Video conferencing on the Internet can sometimes be unstable, depending on the nature of the network or how busy it is. eyeson automatically adapts the bandwidth for a connection and, if necessary, reduces the quality of the video. If that is not enough, here are some more tips:
- Browser refresh? Open the link again
- Network: possibly deactivate VPN in order to communicate via the private network instead of the company network
- We recommend Google Chrome on the PC and also on the MAC - with the exception of iPhone / iPad, please use Safari there (iOS).
- Make sure that the camera, microphone, speaker, etc. are not blocked by parallel opened Skype, Zoom, MS Teams or other browser tabs.
- With Bluetooth devices: Make sure that they are connected to the PC used for the eyeson meeting and not to the phone next to it
- Video “freezes” and audio disturbed? Try turning off the camera
- Network: If the connection is bad, possibly "refresh" the browser and reconnect with Audio Only
- No Audio? Please check if there is an on/off switch for your microphone built in in the cable of your headset
The Detailed Explanation
eyeson is a WebRTC / WebSocket based system and the eyeson communication clients – web browsers and mobile apps – connect to the eyeson server and cloud infrastructure and establish different connections on different ports and protocols for registration, call signaling and real time audio / video streaming.
The eyeson core video technology provides a Single Stream transcoding multi speaker video streaming unit (eyeson cloud MCU) which is a virtual meeting room instance started in the cloud on demand when a meeting is started.
For a quick try you can simply use free independent test tools for realtime communication to verify your network if it is good to use with eyeson.
Use our NEW eyeson test tool
The following eyeson test tool checks your complete client setup and gives a detailed report. Find out in some seconds how your setup is prepared for the use of eyeson.
Also with this test you can generate detailed logs in case of any faiure to get better support from our support team when you reach out.
Environment Requirements for the Use of eyeson
For each communication client, a minimum bandwidth of 1.5 Mbit/s for upload and 1.5 Mbit/s for download is required. The bandwidth required needs to be multiplied by the number of simultaneously active clients within the same network.
Please note: If 2 clients are connected to the same network at the same time, the needed minimum bandwidth is 3 Mbit/s upload and 3 Mbit/s download. It is recommended to allow preferred traffic for real-time communication connections.
Packet loss in the network connection during active communication between the communication clients has to be less than 2%.
Please note: Higher packet loss than 2% can cause pixel errors, frozen video images and in the worst case connection loss. Video connection algorithms additionally use packet loss information to downsize video quality in order to keep the video connection active with lower bitrates and resolutions running with lower quality.
Jitter in the network connection during active communication shall be less than 400ms.
The CPU usage of the used hardware platform shall be less than 80% (maximum) during an active connection. Make sure that you close other applications for the case that your hardware does not provide sufficient processing power.
Please note: Higher CPU usage than 80% can cause pixel errors, frozen video images and in worst case connection loss. Video connection algorithms use CPU usage values also to downsize video quality in order to reduce CPU usage with lower rates and resolutions running with lower quality.
The Internet connection shall allow direct UDP communication between all real-time streaming system components.
The network environment shall be configured in a way that a TCP proxy connection is NOT needed. The eyeson communication software additionally supports TCP and UDP TURN relay streaming connections, but this causes a deviation from ideal real-time communication conditions. For this reason, the requirement is that TCP and UDP TURN RELAY connections shall be avoided by network and firewall configuration as far as possible.
(TCP option*) Is not recommended, but possible for networks that do not allow UDP communication in general.
Minimum Required Streaming Setup
For best streaming performance (in terms of bandwidth and latency) UDP traffic should be allowed to any destination. If that is not possible due to e.g. company network policies, it is highly recommended to whitelist outbound traffic on port UDP/3478, TCP/3478 and TLS/443 to our relay/TURN servers.
Our relay/TURN-servers are:
Optional Setup Extension for Optimum Streaming Conditions
In this case all connections go directly between eyeson clients and cloud conference servers, STUN/TURN Media Proxy not used in active stream.
How Much Bandwidth Do I Need?
One of the advantages of the single stream technology in terms of bandwidth usage is that each client only sends and only receives one stream – independent of the number of participants in a conference.
So the conference connection is reduced to a P2P call from the clients point of view. Each client has only one upstream and one downstream.
The connection for up- and downstream of each client automatically adjusts with the real time streaming capabilities of the network the client is located in. Possible adjustments:
- 960p @ 20fps --> approx. 1.5 Mbit/s
- VGA @ 20fps --> approx. 0.8 Mbit/s
- QVGA @ 20fps --> approx. 0.4 Mbit/s
- QQVGA @20fps --> approx. 0.1 Mbit/s
So the bandwidth usage range for an eyeson connection is between 0.1 - 1.5 Mbit/s per client.
Please note that the quality of the video will be reduced by automatically adjusting to networks not fulfilling the network requirements described in this article.
Screensharing is transmitted with up to Full-HD (1920x1080) / 30 fps. Bandwidth is limited to max. 1.5 MBit/s average.
Should you have any comments, suggestions or questions, please do not hesitate to contact firstname.lastname@example.org!