Tenfold Cloud Connect (TCC) v5.3.0 release notes
Released 20 January, 2022
Certified phone systems
This release is certified for the following phone systems and operating systems:
Avaya AES: Redhat 8
Cisco Finesse UCCX: Windows Server 2019
Cisco UCM: Windows Server 2016
Genesys PureEngage: Ubuntu 18.04
This release is not certified for the following phone systems:
Cisco Finesse UCCE
Cisco UCM with UCCE Queues
IPC Turrets
General improvements
REQ-203: Adds a warning message which displays when a user's extension is already in use and someone logs in using the same extension.
NOTE: Requires TCC 5.3.0 and App 5.3.0
TF-13506: Improves the TCC monitoring and configuration experience for users as follows:
TCC heartbeats include the hostname and IP address of the TCC server.
Restarting is not necessary when changing dialing rules or event format rules.
When new configuration properties are added, classes and fields with the old configuration also update.
NOTE: Requires CCM 5.2.0
TF-13677: Adds a default timeout of 5 seconds for sending an event.
Phone system-specific improvements
Avaya AES
REQ-194: Adds the ability to retrieve an agent's status as "busy" or "busy on call" from Avaya to Omni-channel and Tenfold.
REQ-299: Fixes an issue which required users to log out and back in again after a TCC restart in order for advanced workflows to work.
SUS-1424: Fixes an issue which caused TCC to fail to connect to Avaya AES 8.1 on port 4722.
SUS-1436: Fixes an issue which caused UUI data to fail to display in a landing page for a Lightning flow.
Cisco Finesse
SUS-1406: Fixes an issue which caused agent statuses to fail to be retrieved from Finesse for display in Tenfold.
Cisco UCM
SUS-1256: Fixes an issue so that calls for hunt groups do not cause ringing events for members who are on active calls.
SUS-1330: Fixes an issue which prevented device names configured in TCC and assigned in Tenfold Dashboard from displaying properly in the device list for use in the Tenfold UI.
TF-2691: Adds TCC failover support for Cisco UCM.
Known Issues
TF-13589: Cisco UCM and failover: After switching to standby, a call received and placed on hold before the standby became active is not on hold in the Tenfold UI (although it is on hold in the softphone).
TF-13606: Cisco UCCE: A call from another agent still displays as ringing after an agent answers it; the UI for the calling agent shows the wrong connection time.
TF-13607: Finesse UCCX/Finesse UCCE: When Agent Status is enabled, the status mapping is reset every time Finesse sets an agent to a status that has not yet been assigned in Dashboard.
TF-13611: Cisco UCCE: A user is able to log in to the Tenfold application with the wrong extension.
TF-13650: Cisco UCCE and failover: The active TCC instance does not synchronize with the secondary.
TF-13678: After TCC is restarted, agents must log out and back in for agent status to work consistently.
TF-13679: Upgrade for TCC from 3.x to 5.3.0 does not automatically create .tcc-state when TCC is stopped.