RFC 7118: The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)

In plain English — editorial summary, not part of the RFC

The WebSocket protocol enables two-way real-time communication between clients and servers in web-based applications. This document specifies a WebSocket subprotocol as a reliable transport mechanism between Session Initiation Protocol (SIP) entities to enable use of SIP in web-oriented deployments.

Document record

Document ID

RFC7118

Published

January 2014

Authors

I. Baz Castillo; J. Millan Villegas; V. Pascual

Status

PROPOSED STANDARD

Stream

IETF

Area

art

Pages

25

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7118
• Reported errata exist →

Topics

• SIP
• WebSocket

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent

  March 2014

• RFC 7092A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User AgentsCurrent

  December 2013

• RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent

  April 2014

• RFC 7163URN for Country-Specific Emergency ServicesCurrent

  March 2014

• RFC 7245An Architecture for Media Recording Using the Session Initiation ProtocolCurrent

  May 2014

• RFC 7247Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error HandlingCurrent

  May 2014

• RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted

  May 2014

• RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent

  September 2014

Also filed under

• PROPOSED STANDARD
• 2014
• IETF stream
• art area