Skip to main content

Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3398.
Authors Jon Peterson , Gonzalo Camarillo , Adam Roach , Lyndon Ong
Last updated 2015-10-14 (Latest revision 2002-08-26)
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state RFC 3398 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to <>, <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3398
        Title:      Integrated Services Digital Network (ISDN) User
                    Part (ISUP) to Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, A. B. Roach, J. Peterson, L. Ong
        Status:     Standards Track
        Date:       December 2002
        Pages:      68
        Characters: 166197
        Updates/Obsoletes/SeeAlso:   None
        I-D Tag:    draft-ietf-sipping-isup-06.txt


This document describes a way to perform the mapping between two
signaling protocols: the Session Initiation Protocol (SIP) and the
Integrated Services Digital Network (ISDN) User Part (ISUP) of
Signaling System No. 7 (SS7).  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).

This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.