Tools

WebRTC test

Find out whether video calls can connect in this browser, on this network, and what stands in the way when they cannot. Send this page to anyone whose calls fail.

Your browser asks our STUN server for its public address, tries our relay and opens a WebSocket to our realtime server, as a call would. We keep none of the results.

Using WordPlus Cloud? Test the connection to our servers.

Step by step: WebRTC connection failed: how to find out why a video call doesn't connect

Reading the results

What each check means

WebRTC support

Whether this browser has what a call needs, and which video and audio formats it can send. Two browsers in a call need one format in common.

Connection inside the browser

Two connections in this page talk to each other, with no network in between. When this fails, WebRTC is switched off, whatever the network allows.

UDP on ports 3478 and 443

Calls travel best over UDP. Port 3478 is the usual one for STUN and TURN, and networks that close it tend to leave 443 open. If both fail, only a relay over TCP can carry a call.

Address mapping (NAT)

Most routers keep one public port for a device, which lets another device reach it directly. A symmetric NAT gives each server a different port, so direct calls often fail and need a relay.

Relay over TLS on port 443

Our relay, on the port most firewalls leave open for web pages. It refuses the test, which has no login, and that answer shows the way to it is open.

WebSocket

Apps use a WebSocket to set up calls and to carry live updates. Some proxies and firewalls block it even where web pages load.

Camera and microphone

Whether the browser sees them at all. This test asks for no permission, so it does not use them. The webcam and microphone tests do.

WordPlus Cloud

Calls that find a way through

A call on WordPlus Cloud goes straight between two devices when it can, through the nearest relay when a firewall blocks that, and through our media servers when even the relays cannot reach, without hanging up.

Questions

Frequently asked

What does this WebRTC test check?

That this browser supports WebRTC and can start a connection, that UDP gets out of this network on ports 3478 and 443, how the network maps addresses, that a WebSocket connects, and whether a camera and a microphone are present.

Why do video calls fail when the internet works?

Browsing needs only outgoing web traffic. A call also needs a path between two devices, usually over UDP, and company networks, VPNs and some mobile carriers block or rewrite that traffic. A relay then carries the call.

What is a symmetric NAT?

A router that gives a device a different public port for each address it talks to. The port another device learns then does not work for it, so a direct connection often fails and the call then needs a relay.

What should I do when UDP is blocked?

Try another network to confirm it, such as a phone hotspot, and turn off any VPN. If the network has to stay as it is, calls need a relay over TCP on port 443, which a firewall treats as web traffic.

Is anything sent to WordPlus?

Your browser asks our STUN server for its public address, tries our relay and opens a WebSocket to our realtime server, as a call would. The results stay on this page, and we keep none of them.

Can I send this test to someone whose calls fail?

Yes. It needs no account and no install. They run it and use Copy results to send you what it found.

Do calls on WordPlus Cloud need all of these to pass?

No. A call between two people goes straight between the devices when it can, through the nearest relay when a firewall blocks that, and through our media servers when even the relays cannot reach, without hanging up.