Genesys T-Server and UCMA Connector for Skype for Business Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
|07/25/16||General||Under Shipping Control||X|
This release includes only resolved issues.
This release contains the following resolved issues:
When the connector is running where the option caching-enabled option is set to true and the conference cache is not empty, the connector now fully recovers from a FrontEnd Pool restart. After a restart, new calls created in the connector no longer fail. (LYNC-2131)
T-Server now correctly releases the supervisor in the following scenario:
- A supervisor starts agent monitoring with the following configuration: scope = 'agent', type = 'one call', mode = 'mute', and the T-Server option monitor-consult-calls = 'all'.
- The supervisor joins the conference with a caller and Agent1.
- Agent1 performs a two-step transfer to Agent2 that is not monitored by the supervisor.
- The supervisor no longer remains in the conference after Agent1 completes the transfer and leaves the conference.
If two people are connected in an IM interaction and then the originator escalates it to voice, the originator is no longer immediately displayed as connected when the second party has not yet accepted the voice call and can decline it. (LYNC-1739)
When the primary and backup T-Servers unexpectedly exit at the same time, a call that was in a treatment at the time of the exit now continues correctly after the servers restart. (LYNC-1405)
When a supervisor is engaged in an IM conversation with the agent, whose voice calls he monitors, IM-to-voice escalation no longer reports incorrect call flows. (LYNC-1403)
When a supervisor is busy, a monitoring session no longer starts. Previously, if a monitored agent received a call while the supervisor was busy, T-Server tried to start a monitoring session, which failed with an error, made the monitoring session inactive, and prevented the supervisor from monitoring the agent or initiating new monitoring sessions. (LYNC-1388)
If the backup T-Server starts when the primary T-Server is already running, agent states are now synchronized between the T-Servers. (LYNC-1202)
T-Server does not support DND state synchronization between primary and backup T-Server. Previously, after T-Server switchover or failover, the DND state could become desynchronized from the Skype for Business presence state. The DND state now synchronizes when the newly appointed primary T-Server receives the first presence update from Skype for Business. (LYNC-1108)
T-Server now correctly handles subscription information when multiple switchovers and failovers occur. (LYNC-1013)
During a reconnect procedure between T-Server and the Connector, T-Server no longer loses control of some route points if the subscription fails once. (LYNC-588)
No special procedure is required to upgrade to release 8.5.000.94.
This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.68. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.