Why do calls fail on corporate networks?

Many networks block UDP or restrict STUN/TURN traffic. In that case, calls may connect without media or have one-way audio. Try another network or ensure TURN is available.

Do I need H.264 for video calls?

Not always—many services use VP8/VP9/AV1. Some enterprise setups require H.264, so check codec support if a service explicitly mentions it.

Why does it work in one browser but not another?

Permission state, extensions, and codec availability differ between browsers. Reset site permissions and compare results using the WebRTC and Codec tests.

Browser Diagnostics

Is My Browser Ready for Video Calls?

Quick checks for WebRTC, permissions, and media compatibility

Video Call Readiness

Checks WebRTC, storage, and notifications

What video calls need to work

Video calls typically require WebRTC APIs, camera/microphone permissions, and supported audio/video codecs. Network firewalls can also block real-time media even when the APIs exist. This readiness check summarizes the common failure points and links to deeper diagnostics.

Run the detailed tests

WebRTC Test Codec Test Notifications Test

Fix common issues

Fix WebRTC Camera not working Microphone not working

FAQ

Why do calls fail on corporate networks?: Many networks block UDP or restrict STUN/TURN traffic. In that case, calls may connect without media or have one-way audio. Try another network or ensure TURN is available.
Do I need H.264 for video calls?: Not always—many services use VP8/VP9/AV1. Some enterprise setups require H.264, so check codec support if a service explicitly mentions it.
Why does it work in one browser but not another?: Permission state, extensions, and codec availability differ between browsers. Reset site permissions and compare results using the WebRTC and Codec tests.