RFC 6140: Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a mechanism by which a Session Initiation Protocol (SIP) server acting as a traditional Private Branch Exchange (PBX) can register with a SIP Service Provider (SSP) to receive phone calls for SIP User Agents (UAs). In order to function properly, this mechanism requires that each of the Addresses of Record (AORs) registered in bulk map to a unique set of contacts. This requirement is satisfied by AORs representing phone numbers regardless of the domain, since phone numbers are fully qualified and globally unique. This document therefore focuses on this use case. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6140
- Published
- March 2011
- Authors
- A.B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 35
- Also known as
- —
- Updates:
- RFC 3680
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5947Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)Current
September 2010
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent
September 2005
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
- RFC 4686Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)Current
September 2006
- RFC 6135An Alternative Connection Model for the Message Session Relay Protocol (MSRP)Current
February 2011
- RFC 6128RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) SessionsCurrent
February 2011
- RFC 6155Use of Device Identity in HTTP-Enabled Location Delivery (HELD)Updated
March 2011
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?