Cisco Cisco Unified Customer Voice Portal 10.0(1) Installation Guide

Migrating from Queue and Transfer to Comprehensive with SIP

Migration from the Queue and Transfer deployment model to the Comprehensive deployment
model with SIP involves the following tasks:

•

Making configuration changes in ICM, in the CVP Call Server, and in the ingress gateways.

•

Optionally, deploying new SIP Proxy Servers and/or DNS Servers.

•

In most cases, deploying and configuring additional gateways.

•

Adding Cisco CSS switches if the number of servers and the desired failover and redundancy
model for your deployment necessitates it.

• If you are converting to SIP from the Unified CVP 3.1 SR2 Queue and Transfer model, you

need to follow the instructions below. In addition, you will need to adjust the VXML gateway
dial-peer configurations to SIP dial-peers, and specify some global SIP parameters. You will
also need to decide whether to use the CUPS Proxy server or a non-proxy deployment (local
static route configuration on the CVP Call Server). If you intend to use redundant Proxy
servers (primary and secondary or load balancing), then you must use DNS server lookups
for SRV records or non-DNS based local SRV record configuration. The SRV records will
need to be configured on DNS server or locally with an xml file (local xml configuration
avoids the overhead of DNS lookups with each call). If a single CUPS server will be used,
then SRV record usage is not required. The Configuration and Administration Guide for
Cisco Unified Customer Voice Portal explains how to perform these steps. So besides OAMP
for the Call Server, SIP configuration may also be required on CUPS, Gateways, CUCM and
DNS Server and in order for the solution to be operational with routing calls.

• Note: Local SRV configuration with xml file on the CVP Call Server is available in 7.0 release

only. The ability to configure the XML data from the Operations Console SIP Service
subsection is not yet available.

To perform this migration, perform the following steps:

Modify the ICM configuration as follows. Refer to the ICM Configuration Guide for Cisco ICM
Enterprise Edition for instructions.

a.

Change the current Type 5 NetworkVRU to Type 10. Assign a VRU Transfer Label to
this VRU, which will cause the call to be transferred to a VoiceXML Gateway. Duplicate
this label for each CVP peripheral routing client.

b.

Associate each CVP peripheral with this new Type 10 NetworkVRU.

Modify the CVP Call Server configuration using the Operations Console, to ensure that the
VRU Transfer Label length is properly set in the ICM tab for each CVP Call Server.

Installation and Upgrade Guide for Cisco Unified Customer Voice Portal Release 7.0(2)