Welcome to the new Daily Docs. Please let us know what you think.

Network events

Monitoring for network events during a call can help troubleshoot connection issues.

There are (currently) three possible network connection types: signaling, peer-to-peer, and sfu.

Call setup and call management information flow through the signaling network connection.

Audio and video flow through the peer-to-peer and 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.

When peer-to-peer and sfu network connections are interrupted, remote audio and video tracks stop, for the participant. We will attempt to reconnect peer-to-peer and sfu connections (and restore audio and video) as long as there is a live signaling connection.

The most common cause of peer-to-peer and sfu connection interruptions is high packet loss on the participant's local wifi network.

network-quality-change

Compatibility:
Prebuilt
Custom

Fires when the threshold or quality of the network has changed.

threshold is an assessment of the current network quality, and can have the value 'good', 'low', or '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, and we turn off the local camera when the network quality drops to very-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.

network-connection

Compatibility:
Prebuilt
Custom

A network connection 'connected' or is 'interrupted'.

The event object specifies which type of connection was affected ('signaling', 'peer-to-peer', or 'sfu'), the kind of connection event ('connected' or 'interrupted'), and any other available information, like a participant's session_id or the sfu_id.

The most common cause of peer-to-peer and sfu connection interruptions is high packet loss on the participant's local wifi network.