SIPsip:aliceEFsip:bob
Envelope: a SIP request (REGISTER, INVITE, ACK, BYE)Card: a SIP reply (100, 180, 200 OK)Small blue block: one RTP packet, 20 ms of voiceOrange block: a big download waiting at the routerOne call from alice@example.com to bob@example.com. SIP (RFC 3261) sets it up through sip.example.com: Bob's phone registers, Alice's phone sends INVITE with an SDP offer (RFC 8866, RFC 3264), the server forwards it, 180 Ringing and 200 OK with the SDP answer come back, and ACK goes straight to Bob. The voice then travels phone to phone as RTP over UDP (RFC 3550): G.711 µ-law, one 200-byte packet every 20 ms, marked DSCP EF (46, RFC 3246). A 40 ms jitter buffer evens out arrival; the one-way delay stays under 150 ms (ITU-T G.114). BYE ends the call. The phones have public addresses here. Behind home NAT a phone's private address in SDP is unreachable, so real phones use STUN and ICE (RFC 8445) or a media relay. A real REGISTER is usually challenged first (401 Unauthorized) and repeated with a password digest; SIP over TLS uses port 5061 and SRTP (RFC 3711) encrypts the voice. Names are RFC 2606 examples; 192.0.2.10, 198.51.100.20, 203.0.113.5 and 192.0.2.1 are RFC 5737 documentation addresses. Tags, Call-ID, SSRC, RTP start values, arrival times, the network delay and the buffer size are illustrative.

Setting up the call

  1. Bob's phone sends a SIP REGISTER to the SIP server: "bob@example.com is now at 198.51.100.20." SIP, the Session Initiation Protocol (RFC 3261), sets calls up; it carries no sound.

Carrying the voice

Limits and hanging up

The messages, step by step

;; step 1/11 · register
;; bob → sip
UDP 198.51.100.20:5060 → 203.0.113.5:5060
REGISTER sip:example.com SIP/2.0
From: <sip:bob@example.com>;tag=a73kszlfl
To: <sip:bob@example.com>
Contact: <sip:bob@198.51.100.20>
Expires: 3600
← SIP/2.0 200 OK   (binding saved for one hour)

Responses retrace the Via headers through the proxy. ACK and BYE go straight to the other phone because this proxy did not add Record-Route; many do, and then stay in the signalling path. DSCP marks are kept only inside networks that agree to honour them; across the public internet they are often ignored or reset.