Migrate Comprehensive or Call Director Deployment Models From H.323 to SIP
Starting with Unified CVP 9.0(1), only SIP based implementations are supported. Before migrating from the previous release of Unified CVP 8.0(1) or Unified CVP 8.5(1) to Unified CVP 9.0(1) you must migrate
H.323 to SIP. If your
current CVP deployment model is Comprehensive or Call Director, and to
migrate from H.323 to SIP, follow the instructions in this section to perform
This migration involves the following
Optionally, deploying new SIP Proxy Servers
and/or DNS Servers.
Adding SIP service capabilities to
Unified CVP Call Servers.
Configuring SIP dialed number
Configuring ingress gateways, VXML gateways,
and Cisco Unified Communications Managers.
updated configuration and removing H.323 support if testing is
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
To perform this migration, perform the following
Install and configure
the SIP Proxy Servers and/or DNS Servers.
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
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.
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.
: 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.
gateways to support SIP in general. It is not necessary at this point to
disable H.323 in general or to remove gatekeeper registration
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
Configure each VXML gateway
incoming VoIP dial-peer to be a SIP dial-peer.
Configure Unified CMs such that ingress gateways and Proxy Servers are
SIP Trunk devices.
test calls. If the tests are successful, perform the following steps to remove
In the CVP Operations
Console, remove H.323 services from each CVP Call Server.
In the ingress gateways, remove H.323 support as well as any
settings that cause the gateway to register with the
Standalone VXML Server Components
Server deployments prior to Unified CVP 4.0 did not include Unified ICME
components. In these deployments, applications are invoked as a direct result
of calls arriving in the VXML Gateway, and a single post-application transfer
In Unified CVP versions 4.0(x) and later, you can
select the VXML Server during installation to add reporting or ICM lookup
capability. Unified ICME integration with VXML Server is nominal. Refer to
Operations Console Online Help for Cisco Unified Customer Voice
User Guide for Cisco Unified CVP VXML
Server and Cisco Unified Call Studio
for more information about
CVP VXML Server.
Migrate to 9.0(1)
With the additions and changes in functionality in Unified CVP
Release 9.0(1), there are a number of possible CVP environment migrations you
may need to perform:
During the Unified CVP 9.0(1) installation the Call Server, VXML Server, and Media Server are installed together by selecting the installation option named CVP Server.
This section provides the steps that you must follow to migrate
your CVP environment from version 8.0(1) or 8.5(1) to 9.0(1). It indicates all
of the tasks needed to redeploy your servers during migration.
To redeploy your
CVP Server from CVP Release version 8.0(1) or 8.5(1) to 9.0(1), perform the
Back up your
Back up custom media files
and Java code.
Reinstall the CVP Server
Deploy Call Server device in
Deploy VXML Server device in Ops Console.
Relicense Call Server and VXML
Restart CVP Server.
Redeploy Dialed Number Pattern system-level configuration if
Redeploy SIP Server Groups
system-level configuration if applicable.
Location system-level configuration if applicable.
Redeploy Courtesy Callback system-level configuration if
Redeploy SNMP configuration if
Retransfer or deploy VXML
Copy custom media files and Java
code to CVP Server.
Redeploy CVP Reporting Server
redeploy your CVP Reporting Server from CVP Release version 8.0(1) or 8.5(1) to
9.0(1), perform the following steps:
Reinstall the Reporting Server machine.
Save and deploy Reporting Server device in OAMP.
Relicense Reporting Server.
Redeploy Courtesy Callback
system-level configuration if applicable.
SNMP configuration if applicable.
Redeploy CVP VXML Server
To redeploy your CVP VXML Server (Standalone) from CVP Release version
8.0(1) or 8.5(1) to 9.0(1), perform the following steps:
there is no option to install only a VXML Server, you can install CVP and
configure and run the VXML Server. In essence, you can create a VXML-only
server by installing Call Server and modifying it by configuring only the VXML
components and not the Call Server component.
Reinstall the VXML Server (Standalone) machine.
Save and deploy VXML Server (Standalone) device in
Relicense VXML Server
Restart the VXML Server
Back up your VXML applications so
that they can be redeployed.
For more information, see Step 1 in
the procedure to upgrade the Cisco Unified CVP VXML Server.