Help for owners
Video calls in my app will not connect or sound bad
Short answer
Video calls between two phones often cannot connect directly, so they need a relay server. WebRTC's own guide says a direct socket between clients is often not possible, and the common fix is a TURN relay. If calls fail only for some people or networks, a missing or misconfigured relay is a leading suspect.
Does this sound like your situation?
- Calls connect for some people but not others.
- I can see them but they cannot hear me, or the other way round.
- Video freezes or the picture breaks up.
- Calls work on the same Wi-Fi and fail across networks.
- The call works on my phone and fails for customers.
Why does this happen?
A direct connection is often impossible
The WebRTC guide says a direct socket between clients is often not possible unless they sit on the same local network. That is why an app that works in the office can fail outside it.
Confirmed by webrtc.org
No relay server, or a misconfigured one
TURN, short for Traversal Using Relays around NAT, is a protocol for relaying network traffic and is described as the common way to solve this. If the relay is missing, down or has wrong credentials, some calls will not connect.
Confirmed by webrtc.org
Network quality on either side
A weak signal or crowded network lowers quality for every call app. This is not a defect in your app, but it shapes what is realistic.
Phone permissions for camera and microphone
One-way audio can also come from a microphone permission being refused on one phone. It is a quick check.
What can I do about it today?
- Test across networksCall from one phone on Wi-Fi to another on mobile data. If that is the case that fails, a relay is likely missing.
- Check the microphone and camera permissionsOn the phone with one-way audio, open the app's settings and confirm both are allowed.
- Note the patternWhich phones, which networks, which time of day. This is more useful than the words 'bad quality'.
- Do not switch to another call provider yetA new provider costs time and may repeat the problem. Find the cause first.
- Ask who runs the relayYour developer or a call service? Make sure you know who holds the account.
When should I bring someone in?
- Calls are the core of your service, for example consultations or lessons.
- Customers on certain networks cannot connect at all.
- You do not know if a relay server exists.
How do I handle it?
- Reproduce across networksI test calls between different networks and devices to see where connection fails.
- Check the connection setupI check for a relay, its credentials and how the app uses it.
- Separate connection from qualityA call that cannot start and a call that looks poor are different problems and get different fixes.
- Retest on real phonesI confirm calls work between real phones on mixed networks, then hand you a short test checklist.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why do calls work on the same Wi-Fi?
The WebRTC guide says clients can usually connect directly only when they are on the same local network.
Is a relay server expensive to run?
That depends on usage and who hosts it. A developer can estimate it once call volume is known.
Will every call always look perfect?
No. Quality depends on each person's network, so a good app handles weak connections gracefully.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.