Connection test
Video call connection test
Run the test to find out whether a browser video call can connect from the network you are on. It times a small request to each Meeto media region, then opens the same three connections a call needs: signalling, the direct media path and the relay fallback. It reports what passed and what failed, with no made-up score, and needs no camera or microphone.
Test your connection
- Browser supportThe browser can make real-time calls (WebRTC) and the page is on a secure connection.
- Round trip to Meeto media regionsTime for a small request to reach each media region and come back. A new meeting from here would use the fastest one.
- Signalling connectionA secure WebSocket to the media server, which sets the call up and keeps it in sync.
- Direct media connectionAudio and video travelling straight between this browser and the media server.
- Relay connection (TURN)The fallback path: media carried through a relay server when a network blocks direct connections.
The test runs from your browser and reports to you only: no camera or microphone, no meeting, no stored report. It opens short-lived test connections to Meeto's media servers, the same ones a call uses, and they close on their own within a minute.
What does each connection check mean?
Every Meeto call runs through Meeto's media servers in the region closest to the person who started it, Europe or South-East Asia. The test opens the same connections a call opens to those servers, in the same order.
| Check | What passing means |
|---|---|
| Browser support | The browser has WebRTC, the technology behind browser calls, and the page is on a secure connection. |
| Round trip to media regions | A small request reached each region and came back; the time shown is the better of two tries. Lower is better for conversation. |
| Signalling connection | A secure WebSocket to the media server opened. It sets up the call, joins people and carries controls such as mute. |
| Direct media connection | Audio and video can flow straight between the browser and the media server, usually over UDP. This is the fastest path. |
| Relay connection (TURN) | Media can also go through a relay server. Meeto's relay also works over TLS on port 443, the port ordinary secure websites use, which is how calls get through strict firewalls. |
A call connects when signalling passes and at least one media path passes. Media is encrypted in transit on both paths (WebRTC DTLS-SRTP); read more on the security page.
How to use the results
- Run the test on the network you will call from. Open this page on the same device and network as the call, for example the office Wi-Fi with the VPN you normally use, and press Run the connection test.
- Read the four connection checks. Browser support, signalling, the direct media path and the relay each show Passed or Failed. A call needs signalling plus at least one media path.
- Compare networks if something fails. Run it again on another network, such as a phone hotspot or home Wi-Fi, or with the VPN off if your organisation allows it. A change in the result points at the network that blocks calls.
- Ask the network administrator. If a work network fails, send the administrator the failed check names. Calls need secure WebSockets and real-time media, including TURN over TLS on port 443.
The firewall troubleshooting guide explains what to ask for without weakening your organisation's security controls.
What this test does not measure
Bandwidth
It sends no large files, so it cannot tell your download or upload speed. Calls adapt to the connection: Meeto lowers video quality on a weak network and raises it again when the network recovers.
Wi-Fi stability over time
A single run takes a few seconds. Dropouts that happen every few minutes show up only during a longer call.
Your devices
The network test does not open the camera or microphone. Check them with the camera test and the microphone test.
For a fair comparison between networks, run the test a couple of times on each: the round trip varies from one moment to the next. The test can run a few times in a row from one network; after that, wait a minute between runs.
Frequently asked questions
Does this test measure my internet speed?
No. It checks whether the connections a video call needs can be made from this network and how long a small request takes to reach each media region. It does not download or upload a large file, so it does not measure bandwidth. A speed test cannot tell you whether a firewall blocks calls; this test can.
Why is there no overall score?
Because each result is a fact: a connection either opened or it did not, and a round trip took a measured number of milliseconds. Mixing them into a single number would hide which part failed, and that is what you or your administrator need to know.
Does the test use my camera or microphone, or start a meeting?
No. It sends no audio or video and does not create a meeting. The media server opens a temporary test session that closes on its own within a minute and is not kept in any meeting history. Nothing about you or your network is saved by this page.
What does it mean if only the relay passes?
Your network blocks direct real-time media but allows the relay, which carries media over the standard secure web port. Calls still connect, through the relay. This is common on company networks, hotels and VPNs.
The test passes but my calls still freeze. Why?
Passing means a call can connect. Freezes come from the quality of the connection while the call runs: weak Wi-Fi, a busy network or a far-away region. Move closer to the router, use a cable, close large downloads and check the round trip shown for the region.
Try your first browser meeting
Create a room, share the link and invite someone to join you.