Cisco Unified Contact Center Enterprise Solution Reference ...

Chapter 3 Design Considerations for High Availability
OL-8669-05
Peripheral Gateway Design Considerations
Figure 3-19 Scenario 3 – Only the Primary Cisco Unified CallManager Subscriber Fails
CallManager C
CallManager A
Fails
Agent PG A Agent PG B
M M
M M
Scenario 4: Only the Cisco Unified CallManager CTI Manager Service Fails
IP
CallManager D
CallManager B
ICM synchronzation messages
CallManager intra-cluster messages
JTAPI messages
H323 or MGCP messages
SCCP messages
Figure 3-20 shows a CTI Manager service failure on Cisco Unified CallManager subscriber C. The CTI
Manager services are running on Cisco Unified CallManager subscribers C and D, and Cisco Unified
CallManager subscriber C is the active CTI Manager connected to the Unified CCE Peripheral Gateway
side A. However, all phones and gateways are registered with Cisco Unified CallManager subscriber A.
During this failure, both the CTI Manager and the PG fail-over to their secondary sides. Because the
JTAPI service on PG side B is already logged into the secondary (now primary) CTI Manager, the device
registration and initialization time is significantly shorter than if the JTAPI service on PG side B had to
log into the CTI Manager.
The following conditions apply to this scenario:
All phones and gateways are registered with Cisco Unified CallManager subscriber A.
All phones and gateways are configured to re-home to Cisco Unified CallManager subscriber B (that
is, B is the backup server).
Cisco Unified CallManager subscribers C and D are each running a local instance of CTI Manager.
If the Cisco Unified CallManager CTI Manager service on subscriber C fails, the PG side A detects
a failure of the CTI Manager service and induces a failover to PG side B.
PG side B registers all dialed numbers and phones with the Cisco Unified CallManager CTI
Manager service on subscriber D, and call processing continues.
143947
Cisco Unified Contact Center Enterprise 7.x SRND
3-29