Cisco Cisco Customer Voice Portal 8.0(1) Installation Guide

When converting from H.323 to SIP and using the Comprehensive or Call Director call flow
models, it is important to note that SIP does not support GKTMP and inbound dynamic routing
is done via CUSP proxy support.

To perform this migration, perform the following steps:

Install and configure the SIP Proxy Servers and/or DNS Servers.

Add SIP services to the CVP Call Control Servers capabilities, if necessary. It is not necessary
to remove H.323 services at this point. If SIP Proxy Servers are being used, configure the SIP
services to point to those devices.

Configure SIP dialed number mappings. If you are using SIP Proxy Servers, perform the
configuration in those servers. If not, perform this configuration in the SIP services configuration
screens of the CVP Operations Console. For this process, use your Gatekeeper zone prefix list
as a guide. The same dialed numbers that are configured in the gatekeeper now need to be
configured for SIP.

You must map the following three classes of dialed numbers :

•

VRU transfer labels: This includes any numbers that target VXML gateways. If correlationId
routing is used, then the dialed numbers you specify here must be suffixed with a wildcard
to allow for the variable correlationId. If TranslationRouteToVRU routing is used, then
configure all translation route DNISs here.

•

Incoming DNISs: In the gatekeeper, these are the numbers that target the CVP Call Control
Servers (or, more precisely, the CVP Voice Browsers). For SIP purposes, these should target
the CVP Call Servers.

•

ACD or agent DNISs: This includes any numbers that target egress gateways or Unified
CMs.

Perform the following steps to configure ingress gateways, VXML gateways, and Unified CMs.

a.

Configure the gateways to support SIP in general. It is not necessary at this point to disable
H.323 in general or to remove gatekeeper registration settings.

b.

Configure each ingress gateway outgoing VoIP dial-peer to use SIP rather than session
target ras. If SIP Proxy Servers are being used, configure these dial-peers to target those
servers. If not, then configure these dial-peers to target one or more CVP Call Servers.

c.

Configure each VXML gateway incoming VoIP dial-peer to be a SIP dial-peer.

d.

Configure Unified CMs such that ingress gateways and Proxy Servers are SIP Trunk
devices.

Try some test calls. If the tests are successful, perform the following steps to remove H.323
support.

a.

In the CVP Operations Console, remove H.323 services from each CVP Call Server.

Installation and Upgrade Guide for Cisco Unified Customer Voice Portal Release 8.0(1)