Jump to: navigation, search

8.5.001.50

Genesys T-Server and UCMA Connector for Skype for Business Release Notes


Genesys T-Server and UCMA Connector for Skype for Business is part of 9.x starting in 8.5.001.44.
Release Date Release Type Restrictions AIX Linux Solaris Windows
10/12/17 Hot Fix X

What's New

This release contains the following new features and enhancements:

  • T-Server now generates new alarms for connection or disconnection to configured connectors. These alarms can be configured for interception and an action can be applied in Solution Control Interface. The following alarms are now available:
    • GCTI_MSLYNC_CONN_DISCONNECTED
      ID: 35198
      Level: STANDARD
      Text: Link %d to [%s]:%d is disconnected; %d connectors remain connected
      Description: This alarm is generated by T-Server when connection to a connector is lost.

      T-Server generates a message with ID=35198 and context "Link {linkId} to [{hostname}]:{port} is disconnected; {number_of_connected_links}] connectors remain connected".

    • GCTI_MSLYNC_CONN_CONNECTED
      ID: 35199 <br Level: STANDARD<br Text: Link %d to [%s]:%d is opened; %d connectors are now connected<br Description: This alarm is generated by TServer when connection to connector is opened.

      T-Server generates a message with ID=35199 and context "Link {linkId} to [{hostname}]:{port} is opened; {number_of_connected_links}] connectors are now connected".

    (LYNC-3300)

  • Connector is now able to print the version of the loaded Microsoft Collaboration DLL in its log file. In addition, Connector is able to provide information regarding the Microsoft DLL that will be loaded when the mslync_connector -V command is issued. (LYNC-3269)



Resolved Issues

This release contains the following resolved issues:


Previously, using a ringtone sound file or a music-on-hold sound file caused a memory leak in UCMA. Now this UCMA memory leak is fixed and using a ringtone file or a music-on-hold file no longer causes memory leaks. (LYNC-3299)


T-Server now has a mechanism to clear any stuck calls or sessions on a DN.

A new DN level option force-call-cleanup is available and can be configured in the T-Server section of the Annex tab of a DN. The valid values are true and false. The default value is false.

If this option is set to true and the DN is disabled in the Configuration Database, T-Server will clean up any calls on the DN, and all of the calls on the DN will be dropped.

After the cleanup process has been completed and all calls on the DN are dropped, Genesys recommends that you remove the option from the DN Annex tab or set it to false. (LYNC-3289)


Now T-Server no longer applies ACW for IM calls and does not take active IM calls into account in determining when ACW starts; if an AV call is released during active IM calls, ACW will be applied (LYNC-3277)


Previously, if a participant asked to join a call, for example, using RequestRouteCall, RequestMakeCall, or a similar request, but was not connected for some reason, the call became stuck waiting for the new participant. Now, the im-joining-timeout and av-joining-timeout options are used for this case, as follows:

  • For IM calls—If the destination of the request is answered but not joined during the time interval specified by im-joining-timeout, the request will be failed.
  • For AV calls—If the destination of the request is answered but not joined during the time interval specified by av-joining-timeout, the request will be failed.

In both of these cases, the call is established, but is disconnected when the timer expires.

(LYNC-3265)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.001.50.

Dependencies

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.

This page was last edited on April 5, 2018, at 21:54.
Comments or questions about this documentation? Contact us for support!