You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
There is one use case: use webrtc in receive only mode/non-sender(such as online gaming), in this case, client will not send SR, there is no way to calculate round-trip time by default, webrtc support rfc3611(RTCP xr) which allow non-senders to calculate round-trip time, but not active by default, the remote-outbound-rtp stats of webrtc-stats spec also describe roundTripTime stats need DLRR , calculate rtt is necessary for non-senders use case, nack module use rtt for nack interval check.
Suggestion
as #143 described, we need a control API for active rtcp xr feedback.
The text was updated successfully, but these errors were encountered:
Background
There is one use case: use webrtc in receive only mode/non-sender(such as online gaming), in this case, client will not send SR, there is no way to calculate round-trip time by default, webrtc support rfc3611(RTCP xr) which allow non-senders to calculate round-trip time, but not active by default, the remote-outbound-rtp stats of webrtc-stats spec also describe
roundTripTimestats need DLRR , calculate rtt is necessary for non-senders use case, nack module use rtt for nack interval check.Suggestion
as #143 described, we need a control API for active rtcp xr feedback.
The text was updated successfully, but these errors were encountered: