Contents

Introduction

Prerequisites

Requirements

Components Used

Configuration

Introduction

This document describes the steps to pass the UUI data on CVP.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

- CVP

- Intelligent Contact Management (ICM) scripting

- Session Initiation Protocol (SIP)

Components Used

This document is not restricted to specific software and hardware versions.

Configuration

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:

INVITE sip:7274884100@65.59.218.99:5060 SIP/2.0

Via: SIP/2.0/UDP 10.200.2.20:5060;branch=z9hG4bK17DDEF

From: <sip:$9159999999@65.59.218.99>;tag=14072DC-18F7

...

--uniqueBoundary

Content-Type: application/sdp

Content-Disposition: session;handling=required

v=0

o=CiscoSystemsSIP-GW-UserAgent 1570 7514 IN IP4 10.200.2.20

s=SIP Call

c=IN IP4 10.200.2.20

t=0 0

m=audio 19240 RTP/AVP 0 18 101 19

c=IN IP4 10.200.2.20

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=rtpmap:19 CN/8000

--uniqueBoundary

Content-Type: application/gtd

Content-Disposition: signal;handling=optional

IAM,

PRN,isdn*,,NI***,

USI,rate,c,s,c,1

USI,lay1,ulaw

TMR,00

CPN,04,,1,7274884100

CPC,09

FCI,,,,,,,y,

GCI,011db91a2c0f11d6802f000c8638cdeb

--uniqueBoundary-

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.