Search RFCs
RFC 7092
A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents,December 2013
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7092
Discuss this RFC: Send questions or comments to the mailing liststraw@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 pathbetween the originating and final terminating endpoints, which gobeyond the definition of a SIP proxy, performing functions notdefined in Standards Track RFCs. The only term for such devicesprovided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), whichis 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 indifferent 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 toprovide taxonomy other documents can use and reference.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.