RFC 4497: Interworking between the Session Initiation Protocol (SIP) and QSIG
In plain English — editorial summary, not part of the RFC
This document specifies interworking between the Session Initiation Protocol (SIP) and QSIG within corporate telecommunication networks (also known as enterprise networks). SIP is an Internet application-layer control (signalling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include, in particular, telephone calls. QSIG is a signalling protocol for creating, modifying, and terminating circuit-switched calls (in particular, telephone calls) within Private Integrated Services Networks (PISNs). QSIG is specified in a number of Ecma Standards and published also as ISO/IEC standards. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4497
- Published
- May 2006
- Authors
- J. Elwell; F. Derks; P. Mourot; O. Rousseau
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 65
- Also known as
- BCP117
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2824Call Processing Language Framework and RequirementsCurrent
May 2000
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 2331ATM Signalling Support for IP over ATM - UNI Signalling 4.0 UpdateCurrent
April 1998
- RFC 4488Suppression of Session Initiation Protocol (SIP) REFER Method Implicit SubscriptionCurrent
May 2006
- RFC 4508Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER MethodUpdated
May 2006
- RFC 4485Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)Current
May 2006
- RFC 4484Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)Current
August 2006
- RFC 4483A Mechanism for Content Indirection in Session Initiation Protocol (SIP) MessagesCurrent
May 2006
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?