ProtoStackv0.1

Interactive Protocol Visualizer

Back to all protocols
RTPNFS
Application LayerProfessional trackAdvancedOSI: Application LayerDefault Port: 5060 / 5061Standard: RFC 3261

SIP

— Session Initiation Protocol

SIP borrows the request-response style of HTTP and the address style of email to establish multimedia sessions. INVITE, ACK, and BYE manage call state while SDP in the message body negotiates codecs and media addresses, and proxies route requests between user agents.

Read first: UDP, TCP, RTPContent reviewed 2026-11-18

Interactive Session: How SIP Works

Step through the packet exchange sequence between nodes.

Interactive Execution Sandbox

Interact with a live or clearly-labelled simulated instance of SIP.

Threat Model & Attack Simulation

How this protocol is attacked in practice, what defenders can see, and which control stops it.

Threat model & attack simulation

Simulated

Defensive education. Every step runs in this page; no traffic is generated or sent.

Attack library

SIP registration hijack

Spoofing

Weak digest credentials allow an attacker to register as a user and route calls through the attacker.

Attackersimulated
SIPtarget
Attack step 1 of 3
Guess credentials

The attacker brute-forces or reuses SIP digest passwords.

What a defender can see

Many 401/407 challenges for one account.

Impact if unmitigated

Call interception and toll fraud.

Defences that matter
  • TLS for SIP signalling
  • Strong digest or certificate auth
  • Fraud detection and registration monitoring

This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.

Protocol Specification & Architecture

Key characteristics, real-world deployment patterns, and trade-offs.

Core Technical Features

  • Text request methods: INVITE, ACK, BYE, CANCEL, REGISTER, OPTIONS
  • SDP body negotiates codecs, RTP ports, and media direction
  • Proxy, registrar, and redirect servers route requests by address of record
  • Runs over UDP or TCP on 5060, with TLS on 5061

Real-World Use Cases

  • VoIP desk phones and softphone calls
  • WebRTC gateways bridging browsers to the PSTN
  • Unified communications platforms with presence and video

Advantages & Strengths

  • Human-readable text messages simplify troubleshooting
  • Extensible design supports new methods and body types

Limitations & Vulnerabilities

  • NAT traversal usually requires STUN, TURN, or a session border controller
  • Signalling alone does not guarantee media quality