FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

RTP

IoT & mediaIntermediate

Track media sequence numbers, timestamps and receiver feedback.

SIMULATION01 / 03
Loading topology…
0.0s / 2.8s
01
STEP 1 OF 3Client → Server / peer

Audio packet 100

Sequence numbers detect loss; the timestamp identifies the media sampling instant.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Audio packet 100
1.400192.0.2.10198.51.100.20Audio packet 101
2.800198.51.100.20192.0.2.10RTCP Receiver Report

Track media sequence numbers, timestamps and receiver feedback.

Explain Audio packet 100 and distinguish it from RTCP Receiver Report.

Prerequisites: UDP

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 3550Protocol guide

RTP: protocol guide / panduan protokol

Track media sequence numbers, timestamps and receiver feedback.

Lacak sequence media, timestamp, dan umpan balik penerima.

Communication walkthrough / Alur komunikasi

  1. Audio packet 100

    Sequence numbers detect loss; the timestamp identifies the media sampling instant.

    Sequence mendeteksi kehilangan; timestamp menandai waktu sampling media.

  2. Audio packet 101

    For a 160-sample frame the timestamp advances by 160, not by wall-clock milliseconds.

    Untuk frame 160 sampel, timestamp bertambah 160, bukan milidetik waktu nyata.

  3. RTCP Receiver Report

    RTCP reports reception quality; it is not an RTP retransmission acknowledgement.

    RTCP melaporkan kualitas penerimaan; bukan acknowledgement retransmisi RTP.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 3550 ↗