Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
4-18
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 4 Designing Unified CVP for High Availability
Gatekeeper
Configuration
This section covers the following topics:
•
•
HSRP Configuration
On the primary gatekeeper, enter these commands:
interface ethernet 0
ip address 10.0.1.98 255.255.255.0
! Unique IP address for this GK
standby 1 ip 10.0.1.100
! Member of standby group 1, sharing virtual address 10.0.1.100
standby 1 preempt
! Claim active role when it has higher priority.
standby 1 priority 110
! Priority is 110.
On the backup gatekeeper, enter these commands:
interface ethernet 0
ip address 10.0.1.99 255.255.255.0
standby 1 ip 10.0.1.100
standby 1 preempt
standby 1 priority 100
On both gatekeepers, enter identical gatekeeper configurations. For example:
gatekeeper
! Enter gatekeeper configuration mode.
zone local gk-sj cisco.com 10.0.1.100
! Define local zone using HSRP virtual address as gatekeeper RAS address.
For more information, refer to the latest version of the Configuration and Administration Guide for
Cisco Unified Customer Voice Portal (CVP), available at
Cisco Unified Customer Voice Portal (CVP), available at
Alternate Gatekeeper
Configure alternate gatekeepers using Unified CVP VBAdmin, as shown in the following examples:
set GK "10.0.1.100, 10.0.2.100, 10.0.3.100"
This example sets up three gatekeepers to which the H.323 Service could possible register. In
each case, the H.323 Service registers to the first local zone that is configured in that gatekeeper.
It also uses the default RAS port 1719.
each case, the H.323 Service registers to the first local zone that is configured in that gatekeeper.
It also uses the default RAS port 1719.
setGK "10.0.1.100:zone1:1718, 10.0.2.100"
This example causes the H.323 Service to attempt to register first to gatekeeper 10.0.1.100 on
port 1718 with local zone zone1. If that gatekeeper fails, the H.323 Service subsequently
attempts to register to 10.0.2.100 on port 1719, with the first local zone defined on that
gatekeeper.
port 1718 with local zone zone1. If that gatekeeper fails, the H.323 Service subsequently
attempts to register to 10.0.2.100 on port 1719, with the first local zone defined on that
gatekeeper.