RFC 3578: Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document describes a way to map Integrated Services Digital Network User Part (ISUP) overlap signalling to Session Initiation Protocol (SIP). This mechanism might be implemented when using SIP in an environment where part of the call involves interworking with the Public Switched Telephone Network (PSTN). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3578
- Published
- August 2003
- Authors
- G. Camarillo; A. B. Roach; J. Peterson; L. Ong
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 3910The SPIRITS (Services in PSTN requesting Internet Services) ProtocolCurrent
October 2004
- RFC 3581An Extension to the Session Initiation Protocol (SIP) for Symmetric Response RoutingCurrent
August 2003
- RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated
October 2003
- RFC 3515The Session Initiation Protocol (SIP) Refer MethodUpdated
April 2003
- RFC 3486Compressing the Session Initiation Protocol (SIP)Updated
February 2003
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
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?