The History of SIP
From a research paper at Columbia University to the protocol powering billions of calls worldwide — the story of how the Session Initiation Protocol became the backbone of modern telecommunications.
The Creators of SIP
SIP was co-created by two researchers who believed the telecom world needed a simpler, internet-native signaling protocol.
Henning Schulzrinne
Professor of Computer Science at Columbia University and one of the most influential figures in internet telephony. Co-created SIP, RTP (Real-time Transport Protocol), RTSP (Real-Time Streaming Protocol), and contributed to numerous IETF standards. Served as CTO of the FCC (2012–2014).
Mark Handley
Professor of Networked Systems at UCL and co-architect of SIP. Also co-created SDP (Session Description Protocol) and contributed to multicast and internet conferencing protocols. A key figure in the IETF MMUSIC working group that developed SIP.
Why SIP Was Created
H.323 Was Too Complex
The ITU's H.323 protocol used binary encoding (ASN.1), required multiple sub-protocols, and was difficult to implement and debug.
HTTP as Inspiration
SIP was intentionally designed to resemble HTTP — text-based, human-readable, and using a familiar request/response model that web developers already understood.
Tightly Coupled Systems
Existing protocols tied signaling to media transport. SIP decoupled them, letting signaling and media flow independently for greater flexibility.
Not Internet-Friendly
Legacy telecom signaling (SS7, H.323) wasn't designed for the internet. SIP was built from the ground up as an internet protocol, using URIs, DNS, and existing web infrastructure.
SIP Timeline — 30 Years of Evolution
From a university research paper to the protocol powering virtually all modern voice communication.
SIP is Born
Henning Schulzrinne and Mark Handley present the first SIP draft at the IETF (Internet Engineering Task Force). The protocol is designed as a simple, HTTP-like mechanism for initiating, modifying, and terminating multimedia sessions over IP. The initial draft introduces the core concept: use text-based messages with URIs to locate and invite users to sessions. It's a radical departure from the complex binary protocols of the telecom world.
RFC 2543 — First Official Standard RFC 2543
The first SIP standard is published as RFC 2543 (Proposed Standard). It defines the six core SIP methods that still form the foundation of the protocol today:
- INVITE — Initiate a session (call setup)
- ACK — Confirm session establishment
- BYE — Terminate a session
- CANCEL — Cancel a pending request
- REGISTER — Register a user's location with a server
- OPTIONS — Query server capabilities
SIP vs H.323 — The Protocol War
The telecom industry debates which protocol will dominate VoIP: the ITU's H.323 (complex, binary, telecom-centric) or the IETF's SIP (simple, text-based, internet-native). SIP gains momentum due to its simplicity, extensibility, and alignment with web architecture. H.323 advocates argue it is more mature and feature-complete, but SIP's developer-friendly design wins over the growing internet community. This is the turning point that shapes modern telecommunications.
3GPP Adopts SIP for IMS
The 3rd Generation Partnership Project (3GPP) selects SIP as the core signaling protocol for the IP Multimedia Subsystem (IMS) — the framework for delivering IP multimedia services over 3G, 4G, and future mobile networks. This is a landmark decision that guarantees SIP's place at the heart of mobile telecommunications for decades to come. Every VoLTE and VoNR call today traces back to this decision.
RFC 3261 — The Definitive SIP Standard RFC 3261
RFC 3261 is published, completely replacing RFC 2543. This is the document that defines SIP as we know it today and remains the core SIP specification in 2026. Key improvements over RFC 2543 include:
- Stronger security model with TLS and S/MIME support
- Improved transaction handling and reliability
- Better NAT traversal guidance
- Clearer state machine definitions for UAC and UAS
- Stricter message parsing rules
- Companion RFCs published simultaneously: RFC 3262–3265
Key SIP Extensions Published
A wave of important SIP extension RFCs are published, expanding the protocol's capabilities far beyond basic call setup:
- RFC 3262 (PRACK) — Reliable provisional responses, ensuring 180 Ringing and other provisional messages are acknowledged
- RFC 3265 (SIP Events) — SUBSCRIBE/NOTIFY framework enabling presence, message waiting, and event-driven features
- RFC 3311 (UPDATE) — Modify session parameters before the call is established
- RFC 3428 (MESSAGE) — SIP-based instant messaging, extending SIP beyond voice
- RFC 3515 (REFER) — Enables call transfer and third-party call control
The VoIP Explosion
Consumer and enterprise VoIP adoption accelerates dramatically. Vonage launches aggressive consumer marketing campaigns. SIP-based softphones and IP phones proliferate. Asterisk (open-source PBX) gains massive traction, putting SIP-based telephony within reach of any business. The VoIP revolution begins eating into traditional telco revenue.
The SIP Trunking Era Begins
Businesses begin replacing traditional PRI (Primary Rate Interface) and ISDN lines with SIP trunks. The cost savings are dramatic — 50–70% reduction in telecom bills by routing calls over IP instead of dedicated circuits. SIP trunking providers emerge, and enterprises realize they can consolidate voice and data over a single internet connection. This marks the beginning of the end for TDM-based enterprise telephony.
RFC 4474 — SIP Identity RFC 4474
RFC 4474 introduces SIP Identity — a framework for authenticating the source of SIP requests to prevent caller ID spoofing. This early work on SIP identity lays the groundwork for the STIR/SHAKEN framework that would become mandatory in the United States over a decade later. The RFC defines how digital signatures can be attached to SIP messages to verify the caller's identity.
WebRTC Development Begins
Google begins developing browser-based real-time communication technology (later named WebRTC). While WebRTC uses its own signaling approach, SIP's concepts of session negotiation and SDP (Session Description Protocol) heavily influence WebRTC's design. SIP and WebRTC would eventually become complementary technologies, with SIP gateways bridging WebRTC clients to the traditional telephony network.
SIP over WebSocket
Work begins on enabling SIP over WebSocket connections, eventually published as RFC 7118 in 2014. This allows SIP to run natively in web browsers, enabling browser-based VoIP applications without plugins. The JsSIP and SIP.js JavaScript libraries emerge, making it possible to build full SIP clients entirely in a web browser.
4G/LTE and the Birth of VoLTE
As 4G/LTE networks roll out globally, they are all-IP networks with no native circuit-switched voice support. VoLTE (Voice over LTE) is defined using SIP/IMS as the signaling framework. This means every single 4G voice call in the world uses SIP. Suddenly, billions of mobile devices become SIP endpoints — even though most users have no idea they're using SIP every time they make a phone call.
RFC 6665 — Updated SIP Events RFC 6665
RFC 6665 updates the SIP-Specific Event Notification framework, replacing parts of RFC 3265. The updated spec improves the SUBSCRIBE/NOTIFY mechanism used for presence, message-waiting indicators, and dialog state monitoring. This framework underpins features like BLF (Busy Lamp Field) on IP phones and presence indicators in unified communications platforms.
WebRTC + SIP Gateway Era
With WebRTC maturing in browsers, SIP becomes the essential bridge between web-based communication and the traditional telephone network. SIP-to-WebRTC gateways enable click-to-call from websites, browser-based contact center agents, and seamless connectivity between modern web apps and legacy telephony infrastructure. Overbott, Otherrequired, FreeSWITCH, and Asterisk all add WebRTC gateway capabilities.
SIP Platforms at Scale
SIP-based communication platforms reach massive scale. Asterisk, FreeSWITCH, and Otherrequired power millions of business phone systems globally. CPaaS (Communications Platform as a Service) providers like Twilio and Nexmo build their APIs on top of SIP infrastructure. The SIP trunking market exceeds $7 billion annually. SIP is no longer just a protocol — it's the foundation of an entire industry.
STIR/SHAKEN — Fighting Robocalls RFC 8224/8225/8226
The STIR/SHAKEN framework is published as RFCs 8224, 8225, and 8226. Built on SIP identity mechanisms, it uses digital certificates to verify that the caller ID presented in a SIP INVITE is legitimate. The FCC would later mandate STIR/SHAKEN implementation for all US carriers, making it one of the most significant SIP-related regulatory actions ever taken. It represents SIP's evolution from a simple call setup protocol to a trust framework.
5G and SIP Continues
As 5G networks begin deployment worldwide, the IMS architecture — with SIP at its core — remains the signaling framework for voice services (VoNR, Voice over New Radio). Despite 5G introducing new service-based architecture for data services, SIP's role in voice signaling is reaffirmed. The protocol has proven so effective that no replacement has been deemed necessary even in the 5G era.
Pandemic-Driven Boom
The COVID-19 pandemic triggers an unprecedented surge in remote communication. SIP trunk usage grows over 30% as businesses shift to remote work. Video conferencing platforms (Zoom, Microsoft Teams, Google Meet) rely on SIP-derived signaling for PSTN connectivity. Enterprise SIP trunking demand spikes as office phone systems are redirected to home workers. SIP proves its resilience and scalability under extreme global demand.
Security and Performance Updates
Various SIP-related RFCs are published addressing modern security challenges and performance optimizations. Updates to STIR/SHAKEN address new robocall techniques. SIP over QUIC is explored for reduced connection latency. The IETF continues refining SIP for cloud-native deployments with improvements to load balancing, containerized SIP proxies, and enhanced TLS 1.3 support.
AI + SIP Integration
Artificial intelligence is integrated into SIP-based communication systems at an unprecedented scale. AI-powered applications running on SIP infrastructure include intelligent call routing based on caller intent, real-time speech transcription and translation during SIP calls, AI-driven fraud detection analyzing SIP traffic patterns, automated quality monitoring of SIP call metrics, and conversational AI agents handling customer service calls over SIP trunks.
SIP Powers Global Communication
Thirty years after its creation, SIP is more critical than ever. It powers:
- 80%+ of all VoIP calls worldwide
- All VoLTE and VoNR calls on 4G/5G networks
- Enterprise unified communications for millions of businesses
- Cloud contact centers handling billions of customer interactions
- SIP trunking — a multi-billion dollar global market
- WebRTC gateways connecting browsers to the phone network
- IoT communication for machine-to-machine signaling
- Emergency services (NG911/NG112) transitioning to SIP
SIP Version History & Key RFCs
The complete RFC lineage from the initial SIP standard to the extensions that define modern SIP.
Where SIP is Used Today (2026)
SIP has become the universal signaling protocol for real-time communication across every sector of telecommunications.
VoLTE / VoNR
Every 4G and 5G voice call uses SIP signaling via the IMS framework. Billions of mobile users are SIP users without knowing it. VoLTE is deployed in 200+ networks across 100+ countries.
Enterprise PBX
Asterisk, FreeSWITCH, 3CX, Cisco CUCM, and other IP-PBX systems use SIP as their primary signaling protocol. Millions of businesses run SIP-based phone systems.
SIP Trunking
Replacing ISDN and PRI lines globally. SIP trunks connect business phone systems to the PSTN over IP. The global SIP trunking market exceeds $15 billion and continues growing.
Contact Centers
Cloud-based contact centers (Amazon Connect, Genesys, Five9, NICE) use SIP for call routing, queuing, and agent connectivity. SIP enables skills-based routing and real-time call control.
UCaaS Platforms
Microsoft Teams, Zoom Phone, RingCentral, and other UCaaS providers use SIP on their backend for PSTN connectivity, inter-system routing, and carrier interconnection.
CPaaS / APIs
Twilio, Vonage, Bandwidth, and Sinch expose SIP-based communication through APIs. Developers use SIP trunks and SIP interfaces to build custom voice applications.
WebRTC Gateway
SIP gateways bridge WebRTC browser clients to the traditional phone network. Click-to-call, in-browser softphones, and web-based contact centers all rely on SIP-WebRTC interworking.
IoT Communication
Machine-to-machine communication, industrial IoT, and smart building systems use lightweight SIP for device signaling. SIP's text-based simplicity makes it suitable for embedded devices.
Emergency Services
NG911 (Next Generation 911) in the US and NG112 in Europe are transitioning emergency call systems to SIP-based infrastructure, enabling multimedia emergency communication.
SIP vs Other Signaling Protocols
How SIP compares to H.323, MGCP, and other signaling protocols that competed for dominance in VoIP.
Fun Facts About SIP
Interesting tidbits from three decades of SIP history that make for great conversation starters.
Designed to Look Like HTTP
SIP was intentionally modeled after HTTP so that web developers could quickly understand and implement it. The request/response model, text-based headers, and status codes all mirror HTTP conventions. This design choice was crucial to SIP's rapid adoption.
Born in a University Lab
The first SIP call was made in an academic research lab, not at a telecom company. SIP was born from the internet research community, not the traditional telecommunications industry — which partly explains its internet-first design philosophy.
Human-Readable Packets
Unlike most telecom protocols, SIP messages are plain text. You can literally open a packet capture in a text editor and read a SIP message. This makes debugging SIP significantly easier than working with binary protocols like H.323.
100+ Related RFCs
There are over 100 RFCs related to SIP and its extensions. The SIP ecosystem encompasses everything from basic call setup to instant messaging, presence, event notification, security, and emergency services.
Almost Called "SCIP"
During early development, one proposed name was "SCIP" (Session Control Initiation Protocol). The simpler "SIP" name won out — fitting for a protocol whose core design philosophy was simplicity over complexity.
You Use SIP Every Day
If you make a phone call on a 4G or 5G network, you are using SIP. Every VoLTE and VoNR call is a SIP call. Most people use SIP dozens of times per week without ever knowing the protocol exists.