Cisco Cisco Customer Voice Portal 8.0(1) デザインガイド
5-18
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 5 Interactions with Cisco Unified ICM
Enhanced User-to-User Information
Whereas RTP media port and codec information is defined as a SDP body type, ISDN data is
encapsulated in a Generic Type Descriptor body type by the IOS gateways. When both RTP and ISDN
data are sent to Unified CVP via the TDM gateway, both body types are sent in a multipart/mixed mime
type, that includes both SDP and GTD parts.
encapsulated in a Generic Type Descriptor body type by the IOS gateways. When both RTP and ISDN
data are sent to Unified CVP via the TDM gateway, both body types are sent in a multipart/mixed mime
type, that includes both SDP and GTD parts.
The following configuration in the gateway is required to turn on the Enhanced UUI feature:
voice service voip
signaling forward unconditional
Manipulating the UUS Field
UUI can be set by ICM scripts and extracted by Unified CVP to be resent in SIP messages.
UUI processing scenarios:
•
When GTD (generic type descriptor) data is present in the inbound call leg of the SIP INVITE
message in the mime body format for GTD, Unified CVP saves the GTD data as inbound GTD and
the UUI portion (if present) is passed to Unified ICM.
message in the mime body format for GTD, Unified CVP saves the GTD data as inbound GTD and
the UUI portion (if present) is passed to Unified ICM.
This GTD format is supported by the IOS gateways on outbound voip dial peers with SIP transport.
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 be modified, using the format:
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 be modified, using the format:
UUS,3,<converted Hex value of data from ICM>
The rest of the GTD parameter values are preserved, keeping the values as they arrived from the
caller GTD.
caller GTD.
•
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.
the trace stating No GTD Body present in Caller Body and the call continues as a regular call.
Note
The modified UUI from Unified ICM is passed using the user.microapp.uui ECC variable, or the
Call.UsertoUserInfo variable.
Call.UsertoUserInfo variable.
If both variables are used, Call.UsertoUserInfo takes precedence.
Modified GTD is set in the outbound INVITE mime body from CVP SIP B2BUA, which includes IP
originated callers as well as TDM callers. If a DTMF label for outpulse transfer is received on a
connected call, then the BYE will be sent with the GTD only if UUI is passed by Unified ICM. The BYE
is sent immediately after the SIP INFO with DTMF.
originated callers as well as TDM callers. If a DTMF label for outpulse transfer is received on a
connected call, then the BYE will be sent with the GTD only if UUI is passed by Unified ICM. The BYE
is sent immediately after the SIP INFO with DTMF.
Using UUI
Extract the UUI in your Unified ICM Script by looking at the Call ECC variable user.microapp.uui and
the Call.UserToUserInfo variable, such as in the IF node. By using the SET node on either one of these
variables, the variable can be set on the outbound direction of the call.
the Call.UserToUserInfo variable, such as in the IF node. By using the SET node on either one of these
variables, the variable can be set on the outbound direction of the call.
Setting Call.UserToUserInfo takes precedence over using the ECC variable.
Note
Unified CVP will not send a BYE message on the DTMF label if UUI is not received from Unified ICM.
If a BYE message is received, then the GTD from the received BYE is used to send it on the other leg.