Unified Contact Center Express 12.5(1) SU01 ES01.The fix for Unified CCX deployments is included in these releases: It will also be included in the upcoming Finesse Release 12.0.1 ES08 and Finesse Release 11.6.1 ES11. The Finesse standalone agent moves to Not Ready.įor a Unified Contact Center Enterprise (UCCE) Finesse standalone deployment, customers should upgrade to Finesse Release 12.6.1 or later and Finesse Release 12.5(1)ES7 or later.The Finesse for Unified Contact Center Express (Unified CCX) agent moves to Not Ready-Agent Logon while in the Talking state and Not Ready.There will be a connection failure for these cases: Backgroundįor more information, see Heavy throttling of chained JS timers beginning in Chrome 88. Due to browser throttling of these JavaScript timers, the http-bind request is delayed and the server proceeds to disconnect the client. This is also done via recursive JavaScript timers that run on the Finesse client. In Finesse desktops which use Bidirectional-streams Over Synchronous HTTP (BOSH) for notifications, the http-bind request with long polling is used by the client to maintain presence on the server. This delay will cause the Finesse client to lose the connection with the server. Now, with Chrome 88, this JavaScript timer will be throttled and ping will be rescheduled to every 60 seconds when the Finesse client tab is in the background or minimized.
This ping mechanism is facilitated by the JavaScript timers on the Finesse client. The Finesse client sends a ping to the server at fixed intervals so that the presence is maintained on the server and the server knows that the client is alive. This change in Chrome breaks the ping mechanism between the Finesse client and the server.
Google Chrome 88+ will heavily throttle chained JavaScript timers for minimized/background tabs in particular conditions. UCCE Finesse Agents getting disconnected in Chrome 88+ Agents getting disconnected in Chrome 88+
0 kommentar(er)
