Cisco Cisco Customer Voice Portal 8.0(1)

 zone cluster local B_Cluster zoneB

  element zoneB_GK1 10.86.129.36 1719

 zone cluster local A_Cluster zoneA_GK2

  element zoneA 10.86.129.36 1719

 zone prefix zoneA_GK2 111111* gw-priority 10 gw1-zoneA

 zone prefix zoneB 112233* gw-priority 10 gw2-zoneB

 zone prefix zoneA_GK2 2222* gw-priority 10 ccm1-zoneA_1

 zone prefix zoneB 3333* gw-priority 10 ccm2-zoneB_1

 zone prefix zoneA_GK2 5900* gw-priority 10 cvp1-zoneA

 zone prefix zoneB 6900* gw-priority 10 cvp2-zoneB

 gw-type-prefix 1#* default-technology

 lrq forward-queries

 no shutdown

How It Works

The Unified CVP H.323 Service can be configured with a list of up to five gatekeepers. When
the H.323 Service starts, it attempts to register to the first gatekeeper in the list. If the registration
is not successful, it proceeds to sequentially try the remainder of the gatekeepers in the list until
a successful registration occurs.

The H.323 Service stays registered to that gatekeeper until either:

•

That gatekeeper experiences a failure.

The Voice Browser recognizes a gatekeeper failure in the following ways:

–

The periodic RAS RRQ (registration request) to the gatekeeper times out or is rejected.

–

An ARQ (admission request) on a transfer times out.

•

The gatekeeper proactively tells the H.323 Service to unregister, such as when the
administrator does a shutdown on the gatekeeper configuration.

•

The user executes another setGK from VBAdmin. This will cause the H.323 Service to
register with the first gatekeeper in the list, if that gatekeeper is available; otherwise, it will
once again do a sequential attempt.

The Unified CVP H.323 Service goes out of service when it detects a gatekeeper failure and
stays out of service until it can successfully register to another gatekeeper. During the period
that it is out of service, new calls will be rejected by the Unified CVP H.323 Service. The ingress
gateway will need to take an alternate routing action for those incoming calls (for example,
invoke Unified CVP survivability, or reject the call back to the PSTN network to take alternate
call routing action). Calls that are in service will generally be unaffected. This is because either
the call has already been transferred or by the time the call needs to be transferred (the only
time that the gatekeeper is needed by the Unified CVP H.323 Service). The Unified CVP H.323
Service has most likely already registered to an alternate gatekeeper. However, there is a risk
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.

Configuration and Administration Guide for Cisco Unified Customer Voice Portal Release 8.0(1)