Once the active finesse is down, the connector tries 3 times to connect to the same server, after that, it will show the disconnection error. Once the connection is disconnected, it then checks for an available server and connects with it. The whole process takes roughly 3 - 4 minutes.
UCCE 12. 6 Issues/Limitations:
- There is no limitation related to UCCE 12.6
- Call Type internal for conference case as not able to track the origin of the call.
- If the Agent state is Ready before failover, the Agent state becomes Not Ready - Agent Logon after failover then the state changed to Ready.
- If failover happens during the active consult call, the consult div starts showing the conference and transfer button instead of the original consult div, after some time it starts showing the original consult div.
- Agent State changed to Not ready (Agent Logon) after the call ended / during the call.
- The supervisor is unable to silent monitor/barge in after the connection is restored.
- The brage in button gets disappears on Finesse after the connection is restored (when failover during silent monitoring).
- Call Variables become Null.
- If we log in the agent on the slave node and then failover happens, it doesn’t switch to another node.
All issues are related to Call Data not being available after failover.
Cisco Documentation Link: Cisco Unified Contact Center Express Administration and Operations Guide, Release 11.6(1) - Unified CCX Introduction [Cisco Unified Contact Center Express] - Cisco
"If the active server fails, the Unified CCX provides automatic failover to the standby server. If the active server fails (for example, in the event a hardware failure occurs or the Unified CCX Engine process terminates), some calls being handled by the server are lost. The lost calls are restricted to those being handled by the system (those in the IVR stage or in the queue). Calls answered by agents continue to remain live even though related data on the agent desktop is lost. "
The above issues/limitations are only for the current ongoing call on which failover occurs. For the next call, all the operations should be performed smoothly.