RFC 7092

A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents, December 2013

File formats:
icon for text file icon for PDF icon for HTML
Status:
INFORMATIONAL
Authors:
H. Kaplan
V. Pascual
Stream:
IETF
Source:
straw (rai)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7092

Discuss this RFC: Send questions or comments to the mailing list straw@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7092


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search