PDF(6.2 KB) View with Adobe Reader on a variety of devices
ePub(75.0 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(69.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:August 28, 2016
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.
This document describes the steps to pass the UUI data on CVP.
Cisco recommends that you have knowledge of these topics:
Intelligent Contact Management (ICM) scripting
Session Initiation Protocol (SIP)
This document is not restricted to specific software and hardware versions.
You can pass generic data to and from Unified ICM through Unified CVP using User-to-UserInformation (UUI).
This is accomplished by populating the UUS parameter (often known as the UUI) in the InitialAddress Message (IAM) of the Generic Transparency Descriptor (GTD) data that is sent to the gateway from the network in the Q.931 setup message.
The gateway sends this data to Unified CVP through SIP messages. Unified CVP can then send the data to Unified ICM on a new call.
UUI processing scenarios:
When GTD data is present in the inbound call leg of the SIP INVITE message, Unified CVP saves the GTD data as inbound GTD and the UUI portion (if present) is passed to UnifiedICM If Unified ICM modifies the data, it sends the modified UUI back to Unified CVP. Unified CVP converts the UUI data it receives from Unified ICM into Hex and modifies the UUS(if it is present) and overwrites the inbound GTD value. Only the UUS portion will bemodified, using the format: UUS,3,<converted Hex value of data from ICM>
When GTD is not present in the inbound call leg, Unified CVP prints an informational message on the trace stating No GTD Body present in Caller Body and the call continues as a regular call.
Here is an example how this information must be received:
CVP expects it to be in GTD data and not in the header. This is the reason why the user-to-user data in your header field is not processed as UUI from the CVP.
Now regarding to Passing information with SIP Headers. Once configured correctly, these SIP headers are passed to Unified ICM in the SIPHeaderInfo field of New Call and Request Instruction messages. To access the SIP Header variable in the ICM script, read the Call.SIPHeader call variable. So if you want to have this information with UUI data in the CVP logs, then GTD data needs to be present in the inbound call leg of the SIP INVITE message.