RFC 7131: Session Initiation Protocol (SIP) History-Info Header Call Flow Examples

In plain English — editorial summary, not part of the RFC

This document describes use cases and documents call flows that require the History-Info header field to capture the Request-URIs as a Session Initiation Protocol (SIP) Request is retargeted. The use cases are described along with the corresponding call flow diagrams and messaging details.

Document record

Document ID

RFC7131

Published

March 2014

Authors

M. Barnes; F. Audet; S. Schubert; H. van Elburg; C. Holmberg

Status

INFORMATIONAL

Stream

IETF

Area

art

Pages

52

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7131

Topics

• SIP
• History-Info
• RFC4244bis
• Example
• Call Flow

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current

  January 2014

• RFC 7163URN for Country-Specific Emergency ServicesCurrent

  March 2014

• RFC 7092A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User AgentsCurrent

  December 2013

• RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent

  April 2014

• RFC 7044An Extension to the Session Initiation Protocol (SIP) for Request History InformationCurrent

  February 2014

• RFC 7245An Architecture for Media Recording Using the Session Initiation ProtocolCurrent

  May 2014

• RFC 7247Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error HandlingCurrent

  May 2014

• RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted

  May 2014

Also filed under

• INFORMATIONAL
• 2014
• IETF stream
• art area