RFC 4244: An Extension to the Session Initiation Protocol (SIP) for Request History Information
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7044.
Current version: RFC 7044 — An Extension to the Session Initiation Protocol (SIP) for Request History Information
In plain English — editorial summary, not part of the RFC
This document defines a standard mechanism for capturing the history information associated with a Session Initiation Protocol (SIP) request. This capability enables many enhanced services by providing the information as to how and why a call arrives at a specific application or user. This document defines a new optional SIP header, History-Info, for capturing the history information in requests. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4244
- Published
- November 2005
- Authors
- M. Barnes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 44
- Also known as
- —
- Obsoleted by:
- RFC 7044
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 4239Internet Voice Messaging (IVM)Current
November 2005
- RFC 7131Session Initiation Protocol (SIP) History-Info Header Call Flow ExamplesCurrent
March 2014
- RFC 4245High-Level Requirements for Tightly Coupled SIP ConferencingCurrent
November 2005
- RFC 4247Requirements for Header Compression over MPLSCurrent
November 2005
- RFC 4235An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)Updated
November 2005
- RFC 4233Integrated Services Digital Network (ISDN) Q.921-User Adaptation LayerUpdated
January 2006
- RFC 4298RTP Payload Format for BroadVoice Speech CodecsCurrent
December 2005
- RFC 4190Framework for Supporting Emergency Telecommunications Service (ETS) in IP TelephonyCurrent
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?