Cisco Cisco Customer Voice Portal 8.0(1)

Page of 561
of a timing condition where one or both of the endpoints involved in the transfer (Unified CVP
or the target H.323 endpoint) may not have had a chance to register to the alternate gatekeeper.
There is a possibility that these calls may be dropped unless survivability and Unified ICME
scripting actions have been taken to compensate for the failure.
Note: See the "
" section in Chapter 9,
"Administering the Unified CVP H.323 Service," in Part 2.
Although the Unified CVP H.323 Service does not support Gatekeeper Update Protocol (GUP)
clustering, there is no reason that the gatekeepers cannot be defined as part of a GUP cluster.
In this way, other H.323 endpoints that do support clustering (such as Cisco Unified
Communications Manager and IOS gateways) can take advantage of the benefits of GUP.
Unified CVP will simply ignore GUP messages, such as when one of the gatekeepers in the
cluster becomes overloaded. Unified CVP would use one or more of the gatekeepers in the
cluster as the alternate gatekeepers in its list and detect failure according to the rules mentioned
in the bullets above. It is important to note that you must explicitly itemize all the gatekeepers
in the cluster using setGK in VBAdmin. If Unified CVP supported GUP clustering, it would
only need to register to one of the gatekeepers and the gatekeeper would send Unified CVP the
list of gatekeepers in the cluster upon registration.
How to Configure Alternate Gatekeeper Support in Unified CVP
Use the setGK command in VBAdmin to set a list of gatekeepers to which the Unified CVP
H.323 Service will register.
Step 1
From Unified CVP VBAdmin, enter 
setGK 10.86.129.33
.
This command sets up a single gatekeeper to which the H.323 Service will register.
Step 2
Enter 
setGK 10.86.129.33:zonename1
.
This command sets up a single gatekeeper to which the H.323 Service will register to the zone
in the gatekeeper named zonename1.
Step 3
Enter 
setGK 10.86.129.33, 10.86.129.34, 10.86.129.35
.
This command sets up three gatekeepers to which the H.323 Service can register. In each case,
the H.323 Service registers to the first local zone that is configured in that gatekeeper and uses
the default RAS port 1719.
Step 4
Enter 
setGK 10.86.129.33:zonename1:1718, 10.86.129.34
.
The H.323 Service first attempts to register to gatekeeper 10.86.129.33 with local zone
zonename1 on port 1718. If that gatekeeper fails, the H.323 Service attempts to register to
10.86.129.34 on port 1719 with the first local zone defined on that gatekeeper.
Unified CVP in a GK Cluster Example
GK1 assumption. 3660, running c3660-ix-mz.124-6.T, configured as follows:
Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 4.1(1)
450
Chapter 14: - Configuring the H.323 Devices and VoIP
Gatekeeper Redundancy