Cisco Cisco Unified Customer Voice Portal 10.5(1)

Page of 561
Note: The ":2" means convert the second field in the UUS parameter string to ASCII before
sending to Unified ICME.
The data that will appear in the Unified ICME UserToUserInfo will look as follows:
UUS,3,12345;;CPN,00,,u,5900;;
Note: The NSS parameters are delimited by two semicolons; fields within the NSS parameter
are delimited by a comma.
If extracting OLI from the GTD, several things need to be done:
OLI will arrive in the FDC NSS param.
You need to enter the 
isdn ie oli hex value
 indicates the IE identifier of the OLI in
the setup.
Note: This step is necessary because different switches place OLI in different ISDN IE
locations.
The service provider might need to specifically configure the switch to pass OLI to the
gateway.
Debugging Tips for VRU-Only Call Flow Model
On the gateway, enter these commands:
debug voip application script
debug gtd
In the gateway log, look for the following GTD values:
6616806: *Jan 31 17:12:41.220: cdapi_find_tsm: Found a gtd msg of length 144:
6616807: *Jan 31 17:12:41.220: gtd msg = "IAM,
PRN,isdn*,,ATT5*,
USI,rate,c,s,c,1
USI,lay1,ulaw
TMR,00
CPN,00,,u,5900
CPC,09
FCI,,,,,,,y,
UUS,3,3132333435
12345
GCI,87c0c79d91dd11daa9c4000bfda207f2"
Look for the GTD values sent to the Unified ICME using the Unified CVP Call Server:
>>> CVP bootstrap.tcl: 87C0C79D.91DD11DA.A9C4000B.FDA207F2: UUI sent to
Unified ICME is uus.dat,12345;;cpc.cpc,09;;
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
453
Chapter 14: Configuring the H.323 Devices and VoIP
Configuring Unified CVP to Propagate UUI to Unified ICME