Expand description
RTCP sender and receiver reports (RFC 3550 §6.4).
RTP carries the media; RTCP carries what happened to it. Without reports a stack cannot say why a call sounded bad, and cannot answer a peer that asks.
The field that repays attention is interarrival jitter. It is not a variance and not a standard deviation — it is the smoothed mean deviation of packet spacing, updated per packet by the RFC’s own recurrence:
J += (|D(i-1, i)| - J) / 16An implementation that computes a variance instead produces numbers that look plausible, move in the right direction, and are wrong by a factor that depends on the traffic — which is worse than reporting nothing, because someone will tune a jitter buffer with them.
Structs§
- Receiver
Report - A receiver report: what we have received, from a participant that sends nothing.
- Report
Block - One report block: what one source’s stream looked like from here.
- Sdes
- A source description packet.
- Sdes
Chunk - What one source says about itself.
- Sdes
Item - One source description item.
- Sender
Report - A sender report: what we have sent, plus what we have received from others.
- Stream
Stats - Tracks what a stream looked like from here, so a report can be produced.
Enums§
Constants§
- GOODBYE
- Goodbye.
- RECEIVER_
REPORT - A receiver report.
- SDES_
CNAME - The SDES item type of a canonical name (RFC 3550 §6.5.1).
- SENDER_
REPORT - RTCP packet types (RFC 3550 §12.1).
- SOURCE_
DESCRIPTION - A source description.