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.

SIP

IoT & mediaIntermediate

Set up and terminate a session with SIP dialog messages.

SIMULATION01 / 05
Loading topology…
0.0s / 5.6s
01
STEP 1 OF 5Client → Server / peer

INVITE

A caller proposes a session, commonly with an SDP body.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20INVITE
1.400198.51.100.20192.0.2.10180 Ringing
2.800198.51.100.20192.0.2.10200 OK
4.200192.0.2.10198.51.100.20ACK
5.600192.0.2.10198.51.100.20BYE

Set up and terminate a session with SIP dialog messages.

Explain INVITE and distinguish it from BYE.

Prerequisites: Ethernet

Ready to test your understanding?

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

Learn from the sourceRFC 3261Protocol guide

SIP: protocol guide / panduan protokol

Set up and terminate a session with SIP dialog messages.

Bangun dan akhiri sesi melalui pesan dialog SIP.

Communication walkthrough / Alur komunikasi

  1. INVITE

    A caller proposes a session, commonly with an SDP body.

    Pemanggil mengusulkan sesi, umumnya dengan body SDP.

  2. 180 Ringing

    A provisional response signals that the callee is being alerted.

    Respons provisional menunjukkan penerima sedang diberi notifikasi.

  3. 200 OK

    The callee accepts and returns negotiated session information.

    Penerima menerima dan mengirim informasi sesi yang dinegosiasikan.

  4. ACK

    ACK confirms the successful final INVITE response; RTP media is separate.

    ACK mengonfirmasi respons akhir INVITE yang berhasil; media RTP terpisah.

  5. BYE

    BYE terminates an established dialog; its 200 response is condensed.

    BYE mengakhiri dialog yang telah terbentuk; respons 200 diringkas.

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 3261 ↗