Genesys T-Server and UCMA Connector for Skype for Business Release Notes
This release includes only resolved issues.
This release contains the following resolved issues:
The Connector now correctly attempts to restore services and call control when one of the Front End servers in the Microsoft Lync/Skype for Business environment is stopped and restarted. Previously in this scenario, the Connector sometimes failed if there were established calls present, and/or loose control over the existing calls.
- The Connector will work properly in scenarios involving stopping and starting one of the Front End servers only if the restart of the previously stopped Front End server is performed after synchronization of the Microsoft Lync/Skype for Business servers is completed (approximately after 5 minutes). The behavior of the Connector might be unpredictable if the Front End server restart is performed in a lesser time.
- The Connector might report the release of the calls or parties in scenarios involving starting and stopping one of the Front End servers if a User Endpoint, participating in the call, has been served by the stopped Front End server. Reporting is based on reporting from Microsoft Lync/Skype for Business.
- The Connector will reject call-related requests for the calls for which conference and serving portals are not available.
- When using Skype for Business, if the Invoke-CsComputerFailOver command is issued while the Connector is running and configured to use the conference scheduling feature, it can take 20 minutes or longer for the failover to successfully complete.
No special procedure is required to upgrade to release 8.5.001.12.
This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.90. 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.