Cisco Cisco Customer Voice Portal Downloads Guía De Instalación
Migrating Comprehensive or Call Director Deployment Models from H.323 to SIP
If your current CVP deployment model is Comprehensive or Call Director, and you wish to
migrate from H.323 to SIP, follow the instructions in this section to perform this migration. If
you have a Queue and Transfer deployment model, refer instead to the earlier section
migrate from H.323 to SIP, follow the instructions in this section to perform this migration. If
you have a Queue and Transfer deployment model, refer instead to the earlier section
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.
Managers.
•
Testing the updated configuration and removing H.323 support if testing is successful.
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.
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.
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.
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.
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.
CMs.
Installation and Upgrade Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
62
Chapter 8: - Upgrading to Unified CVP Release 4.1
Migrations for Deployment Models