RFC 3372: Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
In plain English — editorial summary, not part of the RFC
The popularity of gateways that interwork between the PSTN (Public Switched Telephone Network) and SIP networks has motivated the publication of a set ofcommon practices that can assure consistent behavior across implementations. This document taxonomizes the uses of PSTN-SIP gateways, provides uses cases, and identifies mechanisms necessary for interworking. The mechanisms detail how SIP provides for both 'encapsulation' (carriage of PSTN signaling across a SIP network) and 'translation' (protocol mapping).
Document record
- Document ID
- RFC3372
- Published
- September 2002
- Authors
- A. Vemuri; J. Peterson
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- BCP63
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 3578Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)Current
August 2003
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 4904Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs)Current
June 2007
- RFC 3573Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)Current
July 2003
- RFC 3136The SPIRITS ArchitectureCurrent
June 2001
- RFC 3910The SPIRITS (Services in PSTN requesting Internet Services) ProtocolCurrent
October 2004
- RFC 5009Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early MediaCurrent
September 2007
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?