RFC 3824

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

Canonical URL:
https://www.rfc-editor.org/rfc/rfc3824.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Authors:
J. Peterson
H. Liu
J. Yu
B. Campbell
Stream:
IETF
Source:
sipping (rai)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC3824

Discuss this RFC: Send questions or comments to sipping@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×