WebRTC Metrics
A comprehensive overview of WebRTC statistics, derived calculations, extracted features, and observable signals, to better understand call quality, connectivity, and user experience in rtcStats
On this page4 sections
No remote candidate applied
Last updated Applies tortcstats-enrichmentrtcstats.com
No remote ICE candidate was ever applied to this connection.
Description
After both descriptions are set and local ICE gathering starts, the ICE agent needs at least one remote candidate to form a candidate pair and start checking. Candidates arrive either inline in the remote SDP or trickled afterward through the signaling channel.
Is it a problem?
Yes, though the evidence available cannot tell which side is at fault. It can mean the remote peer never gathered or sent a candidate at all (its own network or TURN reachability), or that the signaling channel dropped or never relayed a candidate that was sent.
What do we do here?
We look at peer connections that never reached the connected state. If both descriptions were set and local ICE gathering started, but the connection never reached the checking state, we mark an observation.
