RFC 8606: ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field
In plain English — editorial summary, not part of the RFC
The SIP Reason header field is defined to carry ISUP (ISDN User Part) cause values as well as SIP response codes. Some services in SIP networks may need to know the ISUP location where the call was released in the PSTN (Public Switched Telephone Network) to correctly interpret the reason of release. This document updates RFC 3326 by adding a location parameter for this purpose.
Document record
- Document ID
- RFC8606
- Published
- June 2019
- Authors
- R. Jesske
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 3326
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8787Location Source Parameter for the SIP Geolocation Header FieldCurrent
May 2020
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 8148Next-Generation Vehicle-Initiated Emergency CallsCurrent
May 2017
- RFC 8147Next-Generation Pan-European eCallCurrent
May 2017
- RFC 6739Synchronizing Service Boundaries and <mapping> Elements Based on the Location-to-Service Translation (LoST) ProtocolUpdated
October 2012
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 8917The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service TagCurrent
October 2020
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
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?