Using E.164 numbers with the Session Initiation Protocol (SIP)

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 16
Abstract: There are a number of contexts in which telephone numbers are employed by Session Initiation Protocol (SIP) applications, many of which can be addressed by ENUM. Although SIP was one of the primary applications for which ENUM was created, there is nevertheless a need to define procedures for integrating ENUM with SIP implementations. This document illustrates how the two protocols might work in concert, and clarifies the authoring and processing of ENUM records for SIP applications. It also provides guidelines for instances in which ENUM, for whatever reason, cannot be used to resolve a telephone number. This memo provides information for the Internet community.
Publication Date: 2004-06-01
Status Note: Informational
DOI: 10.17487/RFC3824
Link: https://doi.org/10.17487/RFC3824
Author(s): Jon Peterson
Hong Liu
James Yu
Ben Campbell
Keyword(s): Telephone Records, Application

Latest version of IETF RFC 3824

Document Versions — IETF RFC 3824

▶ IETF RFC 3824 (2004-06-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 1034 [Active*]
IETF RFC 2119 [Active*]
IETF RFC 2396 [Superseded*]
IETF RFC 2806 [Superseded*]
IETF RFC 3261 [Active*]
IETF RFC 3401 [Active*]
IETF RFC 3403 [Active*]
IETF RFC 3761 [Superseded*]
IETF RFC 3764 [Active*]

Bibliographic Reference(s)

Peterson, J., "Enumservice Registration for Presence Services" , Work in Progress, February 2003. EXTERNAL
Rosenberg, J., Schulzrinne, H. and P. Kyzviat, "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)", Work in Progress, June 2003. EXTERNAL
Arends, R., et al., "Protocol Modifications for the DNS Security Extensions", Work in Progress, May 2004. EXTERNAL
IETF RFC 2327 [Superseded*]
IETF RFC 2915 [Superseded*]
IETF RFC 2916 [Superseded*]
IETF RFC 3219 [Active*]
IETF RFC 3263 [Active*]
T-REC-E.164.1997 — E.164 EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3824.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 3824, Using E.164 numbers with the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3824

Snippet:

IETF RFC 3824, Using E.164 numbers with the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3824

HTML (ISO 690 compliant)

Preview:

IETF RFC 3824, Using E.164 numbers with the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3824

Snippet:

<span class="citation"><cite>IETF RFC 3824</cite>, Using E.164 numbers with the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC3824" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3824</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 3824, Using E.164 numbers with the Session Initiation Protocol (SIP)
doi: 10.17487/RFC3824
url: https://doi.org/10.17487/RFC3824

Snippet:

<li>
<cite id="bib-rfc3824">IETF RFC 3824</cite>, Using E.164 numbers with the Session Initiation Protocol (SIP)
<span class="doi">10.17487/RFC3824</span>
</li>

Referenced By

IETF RFC 5278 [Active*]
IETF RFC 5483 [Active*]
IETF RFC 6116 [Active*]
IETF RFC 6189 [Active*]