SIP History INFO Header Support

Available Languages

Download Options

  • PDF     (58.3 KB)
    View with Adobe Reader on a variety of devices
Updated:February 7, 2011

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

SIP History INFO Header Support

Table Of Contents

SIP History INFO Header Support

Prerequisites

Configuring SIP History INFO


SIP History INFO Header Support

The SIP History-info Header Support feature provides support for the history-info header in SIP INVITE messages only. The SIP gateway generates history information in the INVITE message for all forwarded and transferred calls. The history-info header records the call or dialog history. The receiving application uses the history-info header information to determine how and why the call has reached it.

Additional information on the SIP History INFO feature is available in the SIP: History-info Header Support section of the "Cisco IOS SIP Configuration Guide, Release 15.1"

Prerequisites

Cisco Unified Border Element

•Cisco IOS Release 12.4(22)T or a later release must be installed and running on your Cisco Unified Border Element.

Cisco Unified Border Element (Enterprise)

•Cisco IOS XE Release 3.1or a later release must be installed and running on your Cisco ASR 1000 Series Router.

Configuring SIP History INFO

To configure the SIP History INFO feature, see the Configuring SIP History-info Header Support section of the "Cisco IOS SIP Configuration Guide, Release 15.1"

Was this Document Helpful?

FeedbackFeedback

Contact Cisco