RFC 7092: A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents
In plain English — editorial summary, not part of the RFC
In many SIP deployments, SIP entities exist in the SIP signaling path between the originating and final terminating endpoints, which go beyond the definition of a SIP proxy, performing functions not defined in Standards Track RFCs. The only term for such devices provided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), which is defined as the logical concatenation of a SIP User Agent Server (UAS) and User Agent Client (UAC). There are numerous types of SIP B2BUAs performing different roles in different ways; for example, IP Private Branch Exchanges (IPBXs), Session Border Controllers (SBCs), and Application Servers (ASs). This document identifies several common B2BUA roles in order to provide taxonomy other documents can use and reference.
Document record
- Document ID
- RFC7092
- Published
- December 2013
- Authors
- H. Kaplan; V. Pascual
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current
January 2014
- RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent
March 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 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?