RFC 4715: The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI

In plain English — editorial summary, not part of the RFC

Without a tel URI parameter to carry an encoding type of Integrated Services Digital Network (ISDN) subaddress, interworking between ISDN User Part (ISUP) network and a Session Initiation Protocol (SIP) network is impossible in some cases. To solve this problem, this document specifies a new optional tel URI parameter to carry the encoding type of ISDN subaddress. This memo provides information for the Internet community.

Document record

Document ID

RFC4715

Published

November 2006

Authors

M. Munakata; S. Schubert; T. Ohba

Status

INFORMATIONAL

Stream

IETF

Area

—

Pages

14

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4715

Topics

• uniform resource identifier
• isup
• isdn user part

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4694Number Portability Parameters for the "tel" URICurrent

  October 2006

• RFC 4666Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)Current

  September 2006

• RFC 4622Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Obsoleted

  August 2006

• RFC 4575A Session Initiation Protocol (SIP) Event Package for Conference StateCurrent

  August 2006

• RFC 4452The "info" URI Scheme for Information Assets with Identifiers in Public NamespacesCurrent

  April 2006

• RFC 4415IANA Registration for Enumservice VoiceUpdated

  February 2006

• RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated

  October 2007

• RFC 4395Guidelines and Registration Procedures for New URI SchemesObsoleted

  February 2006

Also filed under

• INFORMATIONAL
• 2006
• IETF stream