Cisco Cisco Customer Voice Portal 8.0(1) 安装指南

下载
页码 96
This migration involves the following tasks:
Optionally, deploying new SIP Proxy Servers and/or DNS Servers.
Adding SIP service capabilities to Unified CVP Call Servers.
Configuring SIP dialed number mappings.
Configuring ingress gateways, VXML gateways, and Cisco Unified Communications
Managers.
Testing the updated configuration and removing H.323 support if testing is successful.
When converting from H.323 to SIP and using the Comprehensive or Call Director call flow
models, it is important to note that SIP is not equivalent to H.323 as it does not support hookflash,
post-call survey, GKTMP, bandwidth management, RAI, or inbound and outbound dynamic
routing.
When using Unified CVP Release 3.1 SR2 Advanced Speech or Standalone call flow models,
there is no need to perform this conversion since there is no call control involved. Any call
control is performed using a Unified ICME NIC or through some third-party device, which is
not affected by this conversion.
Warning: When converting to SIP from the Unified CVP Release 3.1 SR2 Queue and
Transfer call flow model, you must first convert to the Comprehensive call flow model.
Refer to 
 for
complete instructions.
To perform this migration, perform the following steps:
Step 1
Install and configure the SIP Proxy Servers and/or DNS Servers.
Step 2
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.
Step 3
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 VoiceXML 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.
Installation and Upgrade Guide for Cisco Unified Customer Voice Portal Release 7.0(2)
81
Chapter 11: Performing CVP Solution Migration
Migrations for CVP Deployment Models