RFC 7434: Interworking ISDN Call Control User Information with SIP
In plain English — editorial summary, not part of the RFC
The motivation and use cases for interworking and transporting User- to-User Information (UUI) from the ITU-T Digital Subscriber Signalling System No. 1 (DSS1) User-user information element within SIP are described in RFC 6567. As networks move to SIP, it is important that applications requiring this data can continue to function in SIP networks as well as have the ability to interwork with this ISDN service for end-to-end transparency. This document defines a usage (a new package called the ISDN UUI package) of the User-to-User header field to enable interworking with this ISDN service. This document covers interworking with both public ISDN and private ISDN capabilities, so the potential interworking with QSIG will also be addressed. The package is identified by the new value "isdn-uui" of the "purpose" header field parameter.
Document record
- Document ID
- RFC7434
- Published
- January 2015
- Authors
- K. Drage; A. Johnston
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7433A Mechanism for Transporting User-to-User Call Control Information in SIPCurrent
January 2015
- RFC 7415Session Initiation Protocol (SIP) Rate ControlCurrent
February 2015
- RFC 7459Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)Current
February 2015
- RFC 7462URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)Current
March 2015
- RFC 7463Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR)Current
March 2015
- RFC 7339Session Initiation Protocol (SIP) Overload ControlCurrent
September 2014
- RFC 7216Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNSCurrent
April 2014
- RFC 7657Differentiated Services (Diffserv) and Real-Time CommunicationCurrent
November 2015
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?