RFC 3976: Interworking SIP and Intelligent Network (IN) Applications
In plain English — editorial summary, not part of the RFC
Public Switched Telephone Network (PSTN) services such as 800-number routing (freephone), time-and-day routing, credit-card calling, and virtual private network (mapping a private network number into a public number) are realized by the Intelligent Network (IN). This document addresses means to support existing IN services from Session Initiation Protocol (SIP) endpoints for an IP-host-to-phone call. The call request is originated on a SIP endpoint, but the services to the call are provided by the data and procedures resident in the PSTN/IN. To provide IN services in a transparent manner to SIP endpoints, this document describes the mechanism for interworking SIP and Intelligent Network Application Part (INAP). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3976
- Published
- January 2005
- Authors
- V. K. Gurbani; F. Haerens; V. Rastogi
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3910The SPIRITS (Services in PSTN requesting Internet Services) ProtocolCurrent
October 2004
- RFC 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3398Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) MappingCurrent
December 2002
- RFC 4722Media Server Control Markup Language (MSCML) and ProtocolObsoleted
November 2006
- RFC 5022Media Server Control Markup Language (MSCML) and ProtocolCurrent
September 2007
- RFC 5379Guidelines for Using the Privacy Mechanism for SIPCurrent
February 2010
- RFC 6193Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)Current
April 2011
- RFC 8433A Simpler Method for Resolving Alert-Info URNsCurrent
August 2018
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?