Cisco Unified Contact Center Enterprise Solution Reference ...
Cisco Unified Contact Center Enterprise Solution Reference ...
Cisco Unified Contact Center Enterprise Solution Reference ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Chapter 3 Design Considerations for High Availability<br />
OL-8669-05<br />
<strong>Cisco</strong> <strong>Unified</strong> <strong>Contact</strong> <strong>Center</strong> <strong>Enterprise</strong> 7.x SRND<br />
CTI OS Considerations<br />
Scenario 3: CTI OS Server A Fails<br />
In this scenario, CTI OS Server side A processes are co-located on PG/CTI Server side A. The following<br />
events occur:<br />
CTI OS Client 1 detects the loss of network connection and automatically connects to CTI OS<br />
server B. During this transition, the buttons of the CTI Toolkit Agent Desktop will be disabled and<br />
will return to operational state as soon as it is connected to CTI OS server B.<br />
CTI OS Client 2 stays connected to CTI OS Server B.<br />
NodeManager restarts CTI OS Server A.<br />
Scenario 4: CTI OS Server B Fails<br />
In this scenario, CTI OS Server side A processes are co-located on PG/CTI Server side B. The following<br />
events occur:<br />
CTI OS Client 2 detects the loss of network connection and automatically connects to CTI OS<br />
server A. During this transition, the buttons of the CTI Toolkit Agent Desktop will be disabled and<br />
will return to operational state as soon as it is connected to CTI OS server A.<br />
CTI OS Client 1 stays connected to CTI OS Server A.<br />
NodeManager restarts CTI OS Server B.<br />
Scenario 5: CTI OS Client 1 Fails<br />
In this scenario, the following events occur:<br />
The agent manually restarts CTI OS Client 1 application.<br />
CTI OS Client 1 randomly selects one CTI OS Server to connect to. (CTI OS Client 1 can be<br />
connected to either CTI OS Server A or B.)<br />
Once connected, the agent logs in, and CTI OS Client 1 recovers its state by getting agent and call<br />
states through the CTI OS Server to which it is connected.<br />
Scenario 6: CTI OS Client 2 Fails<br />
In this scenario, the following events occur:<br />
The agent manually restarts CTI OS Client 2 application.<br />
CTI OS Client 2 randomly selects one CTI OS Server to connect to. (CTI OS Client 2 can be<br />
connected to either CTI OS Server A or B.)<br />
Once connected, the agent logs in, and CTI OS Client 2 recovers its state by getting agent and call<br />
states through the CTI OS Server to which it is connected.<br />
Scenario 7 - Network Failure Between CTI OS Client 1 and CTI OS Server A<br />
In this scenario, the following events occur:<br />
CTI OS Server A drops the connection of CTI OS Client 1<br />
CTI OS Client 1 detects the loss of network connection and automatically connects to CTI OS<br />
server B. During this transition, the buttons of the CTI Toolkit Agent Desktop will be disabled and<br />
will return to operational state as soon as it is connected to CTI OS server B.<br />
Scenario 8: Network Failure Between CTI OS Client 1 and CTI OS Server B<br />
CTI OS Client 1 is not affected by this failure because it is connected to CTI OS Server A.<br />
3-43
Change language