Firefox Tomorrow

web api interface

RTCRemoteOutboundRtpStreamStats

View on MDN ↗

The RTCRemoteOutboundRtpStreamStats dictionary of the WebRTC API is used to report statistics from a remote endpoint about its outbound RTP stream. This will correspond to an inbound stream that is currently being received by the local RTCPeerConnection object.

The statistics can be obtained by iterating the RTCStatsReport returned by getStats() until you find a report with the type of remote-outbound-rtp.

Instance properties

Remote outbound specific statistics

Sent RTP stream statistics

  • bytesSent Optional
    • : A positive integer indicating the total number of bytes sent for this SSRC, including retransmissions.
  • packetsSent Optional
    • : A positive integer indicating the total number of RTP packets sent for this SSRC, including retransmissions.

Common RTP stream statistics

  • codecId Optional
    • : A string that uniquely identifies the object that was inspected to produce the RTCCodecStats report associated with this RTP stream.
  • kind
    • : A string indicating whether the MediaStreamTrack associated with the stream is an audio or a video track.
  • ssrc
    • : A positive integer that identifies the synchronization source (SSRC) of the RTP packets in this stream.
  • transportId Optional
    • : A string that uniquely identifies the object that was inspected to produce the RTCTransportStats report associated with this RTP stream.

Common instance properties

The following properties are common to all WebRTC statistics objects.

  • id
    • : A string that uniquely identifies the object that is being monitored to produce this set of statistics.
  • timestamp
    • : A DOMHighResTimeStamp object indicating the time at which the sample was taken for this statistics object.
  • type
    • : A string with the value "remote-outbound-rtp", indicating the type of statistics that the object contains.

Usage notes

The RTCRemoteOutboundRtpStreamStats object’s remoteTimestamp property provides statistics based on the received data’s NTP timestamp taken from an RTCP Sender Report (SR) block. Be aware that the remote clock may not be synchronized with the local clock (either in current time or speed at which time elapses).

Specifications

SpecificationsStandards references are available on the canonical MDN page.

Browser compatibility

Browser compatibilityCompatibility data is available on the canonical MDN page.