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
Signaling incomplete
Last updated Applies tortcstats-enrichmentrtcstats.com
Only one of the local or remote description was ever set on this peer connection, so negotiation never completed.
Description
Establishing a peer connection requires both sides of the offer/answer exchange: a local description (setLocalDescription()) and a remote description (setRemoteDescription()). Only once both are set can ICE start checking candidate pairs.
Is it a problem?
Yes. When exactly one of the two descriptions was ever applied, negotiation stopped partway through. The signaling channel may have dropped a message, the remote peer may have rejected or ignored the offer or answer, or the application aborted the call before finishing the exchange.
What do we do here?
We look at peer connections that never reached the connected state. If exactly one of setLocalDescription() or setRemoteDescription() was ever called, we mark an observation.
