Monitoring for network events during a call can help troubleshoot connection issues.
There are (currently) three possible network connection types:
Call setup and call management information flow through the
signaling network connection.
Audio and video flow through the
sfu network connections.
Generally, if a participant's
signaling connection is interrupted, the participant is temporarily offline. If we aren't able to reconnect within approximately 20 seconds, the participant will be ejected from the call.
sfu network connections are interrupted, remote audio and video tracks stop, for the participant. We will attempt to reconnect
sfu connections (and restore audio and video) as long as there is a live
The most common cause of
sfu connection interruptions is high packet loss on the participant's local wifi network.
Dive into network connection types
To those building audio-only apps:
As it stands today, this event only applies to video-related data.
Fires when the
quality of the network has changed.
threshold is an assessment of the current network quality, and can have the value
'very-low'. The threshold value is calculated from network stats averaged over an approximately 30-second rolling window. By default, we lower the bandwidth used for the call, when the network quality drops to low.
quality is a subjective calculation of the current network quality on a scale of 1-100, suitable for display in a user interface.
The event object holds the stats for both.
A network connection
'connected' or is
The event object specifies which type of connection was affected (
'sfu'), the kind of connection event (
'interrupted'), and any other available information, like a participant's
session_id or the
The most common cause of peer-to-peer and sfu connection interruptions is high packet loss on the participant's local wifi network.