RFC 4129: Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA Protocol
In plain English — editorial summary, not part of the RFC
This document defines a mechanism for backhauling Digital Private Network Signaling System 1 (DPNSS 1) and Digital Access Signaling System 2 (DASS 2) messages over IP by extending the ISDN User Adaptation (IUA) Layer Protocol defined in RFC 3057. DPNSS 1, specified in ND1301:2001/03 (formerly BTNR 188), is used to interconnect Private Branch Exchanges (PBX) in a private network. DASS 2, specified in BTNR 190, is used to connect PBXs to the PSTN. This document aims to become an Appendix to IUA and to be the base for a DPNSS 1/DASS 2 User Adaptation (DUA) implementation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4129
- Published
- September 2005
- Authors
- R. Mukundan; K. Morneault; N. Mangalpally
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 5359Session Initiation Protocol Service ExamplesCurrent
October 2008
- RFC 5947Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)Current
September 2010
- RFC 6140Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 4119A Presence-based GEOPRIV Location Object FormatUpdated
December 2005
- RFC 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current
June 2005
- RFC 4114E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)Current
June 2005
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
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?