How do I debug dropped video calls on mobile

To debug dropped video calls on mobile, work from the basics outward: device, network, app, then backend.

1) Reproduce and capture the failure

• Note exact device model, OS version, app version
• Record when it drops:
  • immediately after joining
  • after 1–2 minutes
  • only when switching apps / screen locks
  • only on Wi‑Fi or only on cellular
• Capture the call state and any error shown:
  • disconnect code / reason
  • “network unstable,” “media failed,” etc.
• If possible, get a timestamp for the drop and the preceding 30–60 seconds

2) Check the user/device side

• Test on:
  • another phone
  • another account
  • another headset / no headset
  • front vs rear camera
• Make sure:
  • app has camera, microphone, network, and local network permissions
  • battery saver / low power mode is off
  • VPN / firewall / ad blocker is disabled
  • background restrictions are not killing the app
  • the app is updated
• Try:
  • Wi‑Fi off / cellular on
  • cellular off / Wi‑Fi on
  • different Wi‑Fi network

3) Inspect network quality

Dropped calls are often caused by:

• packet loss
• high jitter
• high RTT/latency
• NAT changes / roaming
• Wi‑Fi sleep or handoff
• sudden bandwidth drops

Check:

• signal strength
• whether the device is moving between APs or towers
• whether the call drops when the screen turns off
• whether other devices on the same network are fine

Useful tests:

• ping / traceroute to your signaling and media infrastructure
• run a network quality test from the same network
• compare good vs bad call logs by network type and carrier

4) Collect app and system logs

For mobile video calls, logs should include:

• call/session ID
• signaling events:
  • invite / join / answer / reconnect / disconnect
• WebRTC/media stats if applicable:
  • RTT
  • jitter
  • packet loss
  • bitrate
  • frame rate
  • encode/decode time
  • available bandwidth
  • ICE candidate type
  • selected transport/protocol
• app lifecycle:
  • foreground/background
  • screen lock/unlock
  • permission changes
  • network changes

On Android, look at:

• adb logcat
• dumpsys connectivity
• dumpsys wifi
• battery optimization state

On iOS, check:

• device console logs
• network changes
• app lifecycle callbacks
• whether iOS is suspending the app

5) If you use WebRTC

Check:

• iceConnectionState
• connectionState
• signalingState
• ontrack / track ended
• getStats() around the drop

Important stats:

• packetsLost
• jitter
• roundTripTime
• availableIncomingBitrate
• framesDropped
• framesDecoded
• audioLevel
• ICE candidate pair changes
• TURN fallback usage

Common WebRTC causes:

• ICE fails due to NAT/firewall
• TURN server unreachable
• network handoff triggers ICE restart issues
• video encoder overload on low-end devices
• app doesn’t handle backgrounding/resume correctly

6) Check server side

Look for:

• signaling disconnects
• auth/session expiration
• TURN allocation expiry
• media relay overload
• SFU/MCU participant disconnects
• rate limits
• server region mismatch
• abrupt BYE / teardown events

Correlate by:

• call ID
• user ID
• device type
• network type
• region
• timestamp

7) Compare good vs bad calls

The fastest way to find the issue is to compare:

• successful vs failed calls
• Wi‑Fi vs cellular
• Android vs iOS
• low-end vs high-end devices
• foreground vs background
• same user on different networks

Look for patterns like:

• only on one carrier
• only after 30 seconds
• only when the app is backgrounded
• only on IPv6
• only behind certain routers

8) Add diagnostics to future calls

If you’re building the app, add:

• call event timeline logging
• periodic network stats sampling
• automatic log upload on disconnect
• user-visible “Report problem” flow
• crash/ANR reporting

9) Quick isolation checklist

If you need a fast triage:

1. Does it happen on another phone?
2. Does it happen on another network?
3. Does it happen only in background?
4. Do logs show packet loss/jitter or ICE failures?
5. Does TURN work?
6. Does it correlate with one OS/device version?

If you want, I can also give you:

• a mobile video call debugging checklist
• a WebRTC-specific troubleshooting guide
• or a sample log schema for diagnosing dropped calls