Honeit's network test can help you identify and troubleshoot network-related concerns and issues.

To diagnose issues, we provide an automated test you can run that will check your browser and network environment and report the results. This article will help explain the results you may receive.

For instructions on testing your network connection, see our Testing your Network Connection article.

Understanding Your Test Results

Once you click on the "Test your network connection" link from within the Honeit Call Dashboard connection menu or from the footer of your home page, the network test will launch in a new browser tab (as seen below) and will start to show network diagnostics.

You can run this by clicking here... (The test will take about a minute)

The following table provides details on the most important tests:

Network Quality Parameter	Description	Steps to resolve
TURN UDP Connectivity	Verifies UDP connectivity from your browser to Network's TURN servers	If the UDP connectivity fails, it indicates that your WebRTC session did not establish a connection over UDP. Check the log output for more details. Ensure that you whitelist all the IP addresses and open the ports. Check the Network requirements to see the list of ports and IP addresses that should be whitelisted.
TURN TCP Connectivity	Verifies TCP connectivity from your browser to Network's TURN servers	If the TCP connectivity fails, it indicates that your WebRTC session did not establish a connection over TCP. Check the log output for more details. Ensure that you whitelist all the IP addresses and open the ports. Check the Network requirements to see the list of ports and IP addresses that should be whitelisted.
Bandwidth	Checks the number of simultaneous clients your network can support	Check the log output for the highest, lowest, and average bandwidth. This gives you the number of simultaneous connections can be supported within your network. For example, if your team of 15 interviewers uses Honeit at the same time on the same network and the result shows that only 10 simultaneous calls, there could be call lags, call quality issues, one-way audio issues and high possibility of call drops. Having an increased bandwidth can resolve these issues.
Test call using PCMU	Tests the browser's ability to make calls. This test requires permission to access your microphone, hence, make sure that your microphone access is not blocked.	This test may fail if you have an older version of the browser or OS. So always, use an updated OS version and the latest version of Chrome or Firefox. If using a Bluetooth headset, make sure the correct device is enabled in your browser or OS settings.
Test call using Opus	Test the browser's ability to make calls. This test requires permission to access your microphone, hence, make sure that your microphone access is not blocked.	This test may fail if you have an older version of the browser or OS. So always, use an updated OS version and the latest version of Chrome or Firefox. If using a Bluetooth headset, make sure the correct device is enabled in your browser or OS settings.

Tips to achieve a good network connection

For general best practices and troubleshooting, check out the Network requirements.

Run the network test on each interviewer's local machine, and specifically make it mandatory for ones who report call quality issues.
Make sure that you clear the major network tests specified above under each section.
If any test fails, it indicates firewall restrictions. Here, TCP, UDP, or both could have failed. Ensure that you whitelist all the IP addresses and open the ports mentioned. Check the Network requirements to see the list of ports and IP addresses that should be whitelisted.
If you encounter an ICE error, your call will be disconnected within 10 secs. The possible solution for this is to Whitelist the IPs and to open up the respective ports.
Increase the network bandwidth if needed. This is a crucial step that can solve most call quality issues.
Check if other applications (for example, Youtube, Chrome, etc.) are consuming the available bandwidth. If yes, ask your network/IT team to deprioritize the other applications and give maximum priority to call and call-related activities to have a smooth call experience.
Check for possible Jitter and Packet loss issues (there should be zero packet loss and jitter should be less than 3s).

Last but not least....

Make sure that your browser is not blocking your microphone. You can check this in Chrome here.