Home / RTP, codecs, and DTMF / RTCP sender and receiver reports
RTCP sender and receiver reports
RTCP sender reports and receiver reports describe the RTP flow. A SIP 200 OK does not report loss.
Learn in 5 minutes
- Distinguish sender reports from receiver reports
- Look in RTCP for loss and jitter
- Pair RTCP with the RTP port using the RFC 3550 default
Visual
RFC 3550 pairs RTCP with RTP. SIP status codes are not a substitute.
Worked example
Name the RTCP port The answer says m=audio 40030. Apply the RFC 3550 default and name the RTCP port.
- Dissect the 200 OK.
- Read the m= port.
- Add one for the default RTCP port.
Fault
SIP shows 200 OK and the caller says words are missing. Nobody opened RTCP.
Receiver reports carry fraction lost and jitter. Sender reports show who is actually sending.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Analytics Amazon Connect can attach conversational analytics to an external voice system with a SIPREC connector. The analytics plane is not a second SIP proxy for the customer call.
Sources and go deeper
- RFC 3550 — last checked 2026-10
- Wireshark RTP display filter reference — last checked 2026-10