When our primary server does down, logged in Finesse agents automatically redirects to secondary Finesse URL, which is good. However, once the connection to the primary server re-establishes, we are just seeing that the Finesse page refreshes but the URL is still pointing to the secondary Finesse. Should it change to primary Finesse URL?
Btw, when we checked the SystemInfo, both are "IN SERVICE".
Also, how to determine on which Cisco Finesse server is an agent currently logged in? Is there a command?
However, once the connection to the primary server re-establishes, we are just seeing that the Finesse page refreshes but the URL is still pointing to the secondary Finesse. Should it change to primary Finesse URL?
No it should not. It's totally happy where it is. Cycle that Finesse Tomcat and they will go back. It does not really matter. In an ideal world, half your agents would be on Finesse 1 and half would be on Finesse 2 so a failure only affects half the pool. A redirecting load balancer could do that for you.
there is little bit difference in Finesse architecture if we talk in terms of UCCE and UCCX. Since we are discussing here in context of UCCX, so here is description from Cisco:
Since UCCX uses the active-inactive deployment model, Finesse also mirrors this behavior in Express deployments. Finesse is active only on the node where CCX engine is Master, and follows the engine mastership. Users can log in only to the Finesse server that is currently active. If they attempt to log in to the inactive Finesse server, they will be automatically redirected back to the active Finesse server. Each Finesse server in this model connects only to its own local CTI server instance. UCCX ensures that CTI server is active and allows client connections only on the node where CCX engine is the master.
so it answer your question, that whoever has mastership of uccx engine, agent will be redirected to that UCCX.
Good information - thank you.
You are correct in assuming that my background is UCCE. I did work with IPIVR before CVP and knew that coding, but I have done very little on UCCX and nothing in the last 10 years. They certainly have a lot more similarities now that 10 years ago, but still some fundamental differences.
Actually the behaviour has changed in 11.6.
Now both Finesse Services can be in service and will be able to handle agents on both servers. if they both are in Service.
You need to configure Primary Collector and Failover Collector service parameter.
go to Unified CCX Serviceability -->Service Parameters
generally what happens, UCCX servers exchange keep alive message and if Subscriber miss five consecutive keep alive. it automatically fails over.