Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)

Elwell, John; Kaplan, Hadriel

doi:10.17487/rfc5947

Cited by 1 publication

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Within the problem space that has been established for this work, several constraints shape our solution. These are defined in the MARTINI requirements document [22] and are analyzed in Appendix A. In terms of impact to the solution at hand, the following two…”

Section: Constraintsmentioning

confidence: 99%

“…The document "Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)" [22] contains a list of requirements and desired properties for a mechanism to register multiple AORs with a single SIP transaction. This section evaluates those requirements against the mechanism described in this document.…”

Section: Roach Standards Track [Page 27]mentioning

confidence: 99%

See 1 more Smart Citation

Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)

Roach¹

2011

View full text Add to dashboard Cite

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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6140.

show abstract

Section: Constraintsmentioning

confidence: 99%

Section: Roach Standards Track [Page 27]mentioning

confidence: 99%