RFC 7544: Mapping and Interworking of Diversion Information between Diversion and History-Info Header Fields in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
Although the SIP History-Info header field described in RFC 7044 is the solution adopted in IETF, the non-standard Diversion header field described, as Historic, in RFC 5806 is nevertheless already implemented and used for conveying call-diversion-related information in Session Initiation Protocol (SIP) signaling. RFC 7044 obsoletes the original RFC 4244 and redefines the History-Info header field for capturing the history information in requests. Since the Diversion header field is used in existing network implementations for the transport of call diversion information, its interworking with the SIP History-Info standardized solution is needed. This document describes a recommended interworking guideline between the Diversion header field and the History-Info header field to handle call diversion information. This work is intended to enable the migration from non-standard implementations toward IETF specification-based implementations. This document obsoletes RFC 6044, which describes the interworking between the Diversion header field defined in RFC 5806 and the obsoleted History-Info header field defined on RFC 4244.
Document record
- Document ID
- RFC7544
- Published
- August 2015
- Authors
- M. Mohali
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 30
- Also known as
- —
- Obsoletes:
- RFC 6044
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent
March 2014
- RFC 7044An Extension to the Session Initiation Protocol (SIP) for Request History InformationCurrent
February 2014
- RFC 4244An Extension to the Session Initiation Protocol (SIP) for Request History InformationObsoleted
November 2005
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?