Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for details.

This release note applies to all 8.1 releases of Load Distribution Server (LDS).

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The operating systems available for use with each component release are listed in the table at a high level only. For more detailed information about the supported operating environments, including requirements, supported versions, and any conditions or limitations, see the Load Distribution Server page in the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality:

• LDS now uses TLS 1.3 as the default protocol to communicate securely with other Genesys components such as SIP Server, Configuration Server, Message Server, and URS (Universal Routing Server). Additionally, LDS uses TLS 1.3 for secure communication with third-party software also. (LDS-916)

Corrections and Modifications

This release includes the following corrections and modifications:

The RequestApplyTreatment timeout duration has been increased to a maximum of two hours. The treatment-expire-timeout option has been modified to support the timeout duration to two hours.

treatment-expire-timeout
Valid values: Any integer from 0-7200
Default value: 600
Change Takes Effect: Immediately
Description: Specifies the timeout in seconds during which LDS expects follow-up events to an ApplyTreatment request.

Top of Page

Supported Operating Systems

New in This Release

This is an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS is now modified to alternate between Senders in an HA pair. Previously, when the Reconnect Timeout application properties for the LDS application and LDS Sender(s) was set to the same value, LDS might not switch to another Sender in an HA pair during the reconnect procedure. (LDS-887)

enable-backup-promotion
Valid values: true, false
Default value: true
Description: When set to true, LDS, running as backup, switches to the primary role without waiting for instructions from SCS as soon as the other LDS instance in the HA pair is switched from primary to backup role. When the option is set to false, LDS waits for instructions from SCS.

Top of Page

Supported Operating Systems

New in This Release

This is an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS fixes a registration performance issue introduced in 8.1.007.01. In large environments with multiple StatServers and 1000+ DNs, the rate at which LDS in T-Proxy mode submits registration requests to T-Server is much faster, eliminating long delays for StatServers to complete registrations in such environments. (LDS-871)

Top of Page

Supported Operating Systems

New in This Release

This is an update for this product. This release contains the following new features or functionality:

• Support for the Red Hat Enterprise Linux 8 operating system. See the Supported Operating Environment: Load Distribution Server page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS no longer distributes warning messages Std 39536 and Trc 39530 when it receives a EventUserEvent containing an AttributeReferenceId from T-Server. (LDS-855)

Top of Page

Supported Operating Systems

New in This Release

This is an update for this product. This release contains the following new features or functionality:

• Support for the Windows Server 2019 operating system. See the Supported Operating Environment: Load Distribution Server page for more detailed information and a list of all supported operating systems.

• LDS now requires FlexNet Publisher License Manager version 11.13 or later. (LDS-833)

Corrections and Modifications

This release includes the following corrections and modifications:

LDS no longer becomes unstable when an LDS client requests RequestQueryCall with ThisDN that is not involved in the call. (LDS-829)

When LDS is running in T-Proxy mode with request caching enabled (enable-startup-rq-caching=true) and the LDS client disconnects from T-Proxy before finishing outstanding registrations, other T-Proxy clients now receive registrations on all DNs. (LDS-822)

Top of Page

Supported Operating Systems

New in This Release

This is an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

On startup, LDS no longer establishes a second T-Library connection to the same Hot Standby T-Server pair. This issue was introduced in version 8.1.006.03. (LDS-818)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS no longer establishes a second T-Library connection to the same Hot Standby T-Server pair when the T-Server configuration has changed. (LDS-816)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

Running in T-Proxy mode with enabled request collection (enable-startup-rq-caching=true and ha-sync-level=0), LDS no longer incorrectly reports initial DN status in EventRegistered after LDS switchover. (LDS-800)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

The backup LDS instance no longer leaks memory when sync-level is set to its highest value, 2. (LDS-786)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

In T-Proxy mode, LDS now correctly responds on RequestRegisterAddress with RegisterMode=Monitor from the LDS client when multiple clients are registered on the same DN simultaneously. Previously, an error condition could have happened in environments where multiple StatServers are connected to T-Server via LDS in T-Proxy mode and startup request caching was enabled in T-Proxy (enable-startup-rq-caching=true).

Important: To run LDS with startup request caching enabled, you must upgrade to LDS version 8.1.005.03 or later.

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• LDS now offers the sec-protocol="TLSv12" option value for secured connections. (LDS-767)

Corrections and Modifications

This release includes the following corrections and modifications:

In T-Proxy mode, LDS no longer sends incorrect DN state information to the client after receiving Events DNOutOfService or DNBackInService from T-Server. (LDS-766)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for the CentOS v7 operating system. See the Load Distribution Server page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS no longer fails for one of the clients during simultaneous registrations on the same DN from LDS clients of different kinds (such as Statserver and Workspace Desktop Edition). Previously, the issue affected LDS in T-Proxy mode when startup request caching was enabled (the enable-startup-rq-caching option was set to true). (LDS-765)

Important: To run LDS with startup request caching enabled (enable-startup-rq-caching=true), you must upgrade to LDS version 8.1.005.03 or later.

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for the Windows Server 2016 operating system. See the Supported Operating Environment: Load Distribution Server page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS running in T-Proxy mode no longer sends UnregisterAddress requests on DNs that are registered by the last T-Proxy client. T-Proxy clears DN registration information internally and resets the connection to T-Server to clear registration information in T-Server. (LDS-746)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

This release addresses two issues:

• LDS can now connect to a T-Server HA pair if network latency exceeds 1000 milliseconds when an initial connection is established to a T-Server instance running in backup mode, and 2000 milliseconds when an initial connection is established to a primary T-Server instance. Previously, the values were 250 and 500 milliseconds respectively. Note, however, that when LDS connects to T-Server on very high latency networks (>1000 milliseconds), LDS performance might be seriously degraded.
• LDS now uses both T-Servers from an HA pair alternatively to reestablish a lost connection to an HA T-Server pair. Previously, LDS might start using only one T-Server from an HA pair.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS, running in Load Distribution Mode, no longer becomes unstable when a Mute Transfer or Blind Transfer operation is completed to a routing point that LDS handles. (LDS-740)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS no longer becomes unstable after the following scenario:

1. Call1 is served by Receiver #1.
2. Call2 is served by Receiver #2 (calls 1 and 2 are unrelated).
3. Event Party Changed indicates that Connection of the Call1 is changed to Call2.
4. Call 2 is released.
5. Receiver #2 is registered on a new DN.

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• LDS now supports the MTLS (Mutual Transport Layer Security) protocol on connection to Genesys Message Server. (LDS-680)

  For details, see Introduction to Genesys Transport Layer Security.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS now includes the AttributeApplicationName in the EventPrimaryChanged event, when the T-Library generates such an event internally. Previously, a missing attribute in an EventPrimaryChanged event may have caused the client receiving such an event to become unstable. The error condition was triggered by an EventLinkConnected or EventLinkDisconnected event that did not include an AttributeApplicationName. (LDS-733)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Load Distribution Server.

• LDS now supports the Mutual TLS (MTLS) protocol on these client/server connections handled by LDS:
  • LDS to Configuration Server (Configuration Server Proxy)
  • LDS to T-Server
  • T-Lib clients to LDS
  • Primary LDS to Backup LDS
  For information about MTLS configuration, see Introduction to Genesys Transport Layer Security in the Genesys Security Deployment Guide.
• LDS now supports Linux RH 7, 64-bit.
• LDS now supports AIX v7.1, 64-bit.
• LDS uses a new request pacing mechanism on T-Server connection in T-Proxy mode. The feature is controlled by a new configuration option, max-rq-rate. The option specifies the maximum number of requests LDS in T-Proxy mode sends to T-Server in one second without considering the actual rate that responses are received from T-Server.
  When the option is set to 0, T-Proxy uses the max-outstanding configuration option to control request pacing toward T-Server.
  max-rq-rate
  Valid values: 0 - 1000
  Default value: 0
  Changes take effect: immediately
• On T-Server and client startup, LDS in T-Proxy mode handles a significant number of client requests and T-Server events. When multiple clients (such as Stat Server) are connecting at the same time there is a significant amount of traffic between T-Proxy and T-Server on behalf of each client. T-Proxy can now optimize the client registration and query process in these situations by collecting (caching) identical requests from different clients and reusing responses. This optimization reduces traffic between T-Proxy and T-Server. Note that CPU and memory use by T-Proxy will increase slightly during such events compared to previous versions. The feature is controlled by a new configuration option:
  enable-startup-rq-caching.
  Valid values : true , false
  Default value : false
  Changes take effect : immediately
  When set to true, this option enables client request collection and T-Server response caching in T-Proxy to optimize traffic between T-Proxy and T-Server when multiple clients are connecting and registering for the same set of DNs simultaneously.

  Important: To run LDS with startup request caching enabled (enable-startup-rq-caching=true), you must upgrade to LDS version 8.1.005.03 or later.

  
  
• New debug log information helps to trace communication between LDS and its clients and between LDS and T-Servers. Messages appear in the following format:
  <timestamp> To Tserver <tservername>, Message <gctimessagename>, ReferenceId <requestreferenceid>
  <timestamp> From Tserver <tservername>, Message <gctimessagename>, ReferenceId <requestreferenceid>
  <timestamp> To Client <ldsclientname>, Message <gctimessagename>, ReferenceId <requestreferenceid>
  <timestamp> From Client <ldsclientname>, Message <gctimessagename>, ReferenceId <requestreferenceid>
  
• LDS now supports ADDP on an HA Sync link connection. All configuration options for ADDP on HA Sync link should be kept in a dedicated configuration section called "backup-sync". Note: These options apply only when LDS is configured in hot standby redundancy mode.
  
  • protocol
    Default Value: addp
    Valid Values:
    
    • default - The feature is not active.
    • addp - Activates the Advanced Disconnect Detection Protocol.
    Changes Take Effect: When the next connection is established
    Specifies the name of the method used to detect connection failures. If you specify the addp value, you must also specify a value for the addp-timeout, addp-remote-timeout, and addp-trace options.
  • addp-remote-timeout
    Default Value: 0
    Valid Values: Any integer from 0 to 3600
    Changes Take Effect: Immediately
    Specifies the time interval in seconds that the redundant LDS waits for a response from this LDS after sending a polling signal. The default value of 0 (zero) disables the functionality of this option. To establish an appropriate timeout, specify a value other than the default. This option applies only if the protocol option is set to addp.
  • addp-timeout
    Default Value: 0
    Valid Values: Any integer from 0 to 3600
    Changes Take Effect: Immediately
    Specifies the time interval in seconds that this LDS waits for a response from another LDS after sending a polling signal. The default value of 0 (zero) disables the functionality of this option. To establish an appropriate timeout, specify a value other than the default. This option applies only if the protocol option is set to addp.
  • addp-trace
    Default Value: off
    Valid Values:
    
    • off, false, no - No trace (default).
    • local, on, true, yes - Trace on this LDS side only.
    • remote - Trace on the redundant LDS side only.
    • full, both - Full trace (on both sides).
    Changes Take Effect: Immediately
    Specifies whether the option is active, and to what level the trace is performed. This option applies only if the protocol option is set to addp.
  • sync-reconnect-tout
    Default Value: 20
    Valid Values: Any integer from 0 to 3600.
    Changes Take Effect: Immediately
    Specifies the time interval in seconds after which the backup T-Server attempts to reconnect to the primary server.

Corrections and Modifications

This release includes the following corrections and modifications:

LDS 8.1 fully supports transaction handling for non-equal receivers. When a transaction has been reassigned from one receiver to another, LDS generates the LMS message "39527|TRACE|GCTI_LDS_TRANS_07|Transaction (%s) receiver changed". Conditions for the LMS messages "39525|STANDARD|GCTI_LDS_TRANS_05|Client %s not registered on DN %s. Transaction %s event lost." and "39534|STANDARD|GCTI_LDS_REF_04|No clients for Transaction (%s)" are never met and such messages are never distributed by LDS 8.1. (LDS-727)

LDS no longer reports incorrect T-Server host and port parameters in the LMS message "Std 04504", when the last T-Server from a hot standby HA pair is disconnected. (LDS-678)

The LDS application template no longer enables debug log output to stdout by default. (LDS-671)

The backup LDS instance no longer grows in memory when sync-level is set to its highest value (2). (LDS-670)

LDS now recognizes and can connect to T-Server after the T-Server name has been changed in Configuration Database. (LDS-664)

The LDS executable on AIX now supports 2GB of data by default. (LDS-663)

The LDS client can now connect to a warm standby HA T-Server pair in the following scenario:

1. Backup T-Server is stopped;
2. HA T-Server relationship is removed;
3. HA T-Server relationship is restored;
4. Backup T-Server restarted;
5. Backup T-Server is promoted to the primary (switchover).

The LDS client can now connect to a hot standby HA T-Server pair after T-Server applications are disabled and enabled multiple times in Genesys Configuration Database. (LDS-654)

LDS running in Single T-Server Load Distribution Mode can now accept any type of Receiver as described in the "Load Distribution Server User's Guide". Previously, only Universal Routing Server and Call Concentrator applications were accepted. (LDS-644)

LDS no longer uses the option keep-taction-stat (beginning in release 7.x). The option is removed from the LDS configuration template. If the option is provided in the configuration, LDS will continue to ignore it. (LDS-637)

Previously, LDS in T-Proxy mode may have generated the LMS message "Std 39504 - requested Sender is not available" when only one T-Server from a T-Server HA pair was running. T-Proxy mode no longer generates this LMS message when at least one T-Server from an HA pair is running. (LDS-550)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for Windows Server 2012 in 64-bit compatibility mode.

• This version was first released as a Hot Fix on 11/07/13.

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS now correctly reconnects to the Local Control Agent (LCA). Previously, LDS might fail to reconnect to the LCA, if Configuration Server and LCA were both shutdown and restarted. (LDS-653)

LDS now prevents memory resource leaks in scenarios where LDS clients frequently reconnect and re-register on the same set of DNs. Starting from LDS version 8.1.000.17, LDS does not store multiple registration requests for the same DN. Previously, LDS might have had memory allocation issues. (LDS-649)

LDS now correctly handles unregistration requests for DNs. When establishing a connection to the backup T-Server, LDS does not send registration requests for DNs that have already been unregistered. Previously, LDS did not delete the unregistered DNs and would re-issue the registration requests. (LDS-648)

LDS now prevents memory resource leaks in scenarios where LDS clients frequently reconnect and re-register on the same set of DNs. When establishing a connection to the backup T-Server, LDS sends a significantly reduced number of registration requests. Previously, LDS might have had network traffic control issues. (LDS-564)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for Red Hat Enterprise Linux 6, 32-bit and 64-bit.

Corrections and Modifications

This release also includes the following correction and modification:

LDS now correctly distributes an event to the same Universal Routing Server (URS) after receiving an Inter Server Call Control Event Propagation (ISCC/EPP) EventPartyChanged event with a new ConnectionID attribute. Previously, LDS selected different Universal Routing Servers for distribution after receiving such an event. (ER# 318315930)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality:

• To manage network traffic control, LDS now supports the enable-backup-distribute configuration option, which controls the set of events that is distributed by the backup LDS in TProxy mode, running in a high-availability (HA) environment. This option is set in the LDS section.

  enable-backup-distribute
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  Specifies whether all or a limited set of registration and HA-related events are distributed by the backup LDS in TProxy mode, running in a high-availability (HA) environment. If this option is set to false, LDS in TProxy mode only distributes the registration and HA-related events. If this option is set to true, LDS in TProxy mode distributes all events. (ER# 307761168)

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS now correctly handles the scenario where a client unexpectedly disconnects while there are still a large number of outstanding registration requests from that client in the queue. Previously, the recursive deletion of outstanding requests could cause a stack overflow. (ER# 313021858, 308935858)

LDS now correctly handles unequal receivers (different DN sets for different clients). Previously, the handover of a transaction from one receiver to another could cause a memory corruption. (ER# 312647561)

LDS now correctly assigns the appropriate load average to a newly connected URS. Previously, LDS might have incorrectly assigned the wrong load average, which caused a temporary URS overload. (ER# 311063625, 288390451)

A backup LDS, running in a high-availability (HA) environment with a hot standby redundancy type, now correctly specifies a minimum number of events set in the TSetInputMask request, if the value of the ha-sync-level configuration option is set to 0 (zero). Previously in this scenario, the backup LDS might have unnecessarily requested full event reporting from T-Server by sending a TSetInputMask request with all of the events enabled. (ER# 310217445)

LDS now correctly reconnects to an instance of Configuration Server that is running on the same Solaris or HP-UX host. Previously, LDS could not recover if the initial connection attempt failed. (ER# 307341038)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS is now modified to add a line feed (LF) code into the T-Library debugging messages, when these messages are enabled by the tlib-verbose configuration option. Previously, the LF was missing from some of the log messages and consequently, these messages were concatenated and were hard to read. (ER# 306826481)

LDS, when running in T-Proxy mode, now correctly handles the memory allocation for the TRegisterAddress request. Previously in this scenario, a memory leak occurred when a client disconnected. (ER# 306156950, 303763056)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality.

• Load Distribution Server (LDS), when running in T-Proxy mode, now supports the Location Monitoring functionality.

  Note: Location Monitoring support is important when Universal Routing Server (URS) is configured through LDS, running in T-Proxy mode, in a multi-site environment. Location Monitoring is needed for URS to know if the destination is reachable from the present Routing Point location in order to deal with broken Inter Server Call Control (ISCC) links when the T-Servers are up and running, but the link between them is broken.

  (ER# 302943446)

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS no longer generates an EventError (Timeout error) message after receiving a TApplyTreatment request. Previously, LDS generated an EventError message after receiving a TApplyTreatment request, if the call was abandoned during the treatment. (ER# 299391926)

LDS now correctly handles all T-Server events with an attached TKVList message in excess of 64 kilobytes. Previously, LDS had a 64 kilobytes size limitation for the following T-Server events: EventRegistered, EventPartyInfo, EventAddressInfo, and EventLocationInfo. (ER# 296831680)

LDS now correctly reconnects to a pair of T-Servers running in a high-availability (HA) hot standby mode configuration. Previously, LDS did not reconnect to T-Server, when LDS and one of of the T-Servers were both running on the same Solaris (or HP-UX) host and a switchover occurred. (ER# 296159827)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

LDS no longer incorrectly sets the restrictive input mask on T-Server when, in T-Proxy mode, it changed from backup to primary mode. (ER# 295612731)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:

When a client abandons its registration leaving a big number of unprocessed requests in the queue, LDS now correctly clears the request queue of that client and processes requests coming from a new client. (ER# 293136202)

LDS no longer distributes an EventError message to the client that sent a T-Library request with an empty AttributeLocation value. LDS now handles requests with an empty AttributeLocation in the same way as requests without the AttributeLocation. (ER# 290071914)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of Load Distribution Server.

• Support for FLEXNet Publisher 11.9.
• Support for Red Hat Enterprise Linux 5, 64-bit.
• Support for HP-UX Itanium (version 11i v3).
• Support for AIX 7.1.
• Support for vSphere 4 Hypervisor.
• Support for IPv6.
• Support for Unresponsive Process Detection.
• Alarm added for expired requests in standard logging mode if those requests expired based on the rq-expire-timeout configuration option.
• Enhanced logging capabilities: the maximum number of log files to be stored using the expire configuration option is now 1000.
• Support for Bandwidth Monitoring.
• Enhanced support of T-Server HA failover.
• Support for Genesys Administrator.
• Support for bulk request pacing. The new configuration option max-outstanding supports this feature. Please refer to the Framework 8.1 Load Distribution Server User's Guide for details about this feature and option. (ER# 277765471)

Corrections and Modifications

This release includes the following corrections and modifications that were made between release 7.2 or earlier releases and the initial 8.1 release:

LDS no longer becomes unstable after Universal Routing Server or T-Server is disconnected under high request volume or significant network delay. (ER# 273477008, 275705930)

In a scenario under HP-UX and Solaris where primary and backup LDS instances are set up to run on the same host, the backup sync link is now created between the two LDS instances. Previously, this link may not have been created in this scenario. (ER# 273926613)

LDS once again distributes the LMS message "Std 04503 Connected to CfgServer..." upon startup as it did prior to the 7.2.101.00 release. (ER# 274134768)

LDS no longer remains in memory after receiving SIGABRT or SIGTERM signals if there are multiple LDS clients attempting to connect to LDS when LDS starts its shutdown procedure. (ER# 279987866)

LDS no longer terminates unexpectedly in the following scenario: (1) multiple clients request connection to an inactive, standalone T-Server, and (2) that T-Server eventually starts up. (ER# 280581235)

After changing application properties for the backup T-Server in Configuration Manager, a client is now able to connect to a High-Availability (HA) T-Server Pair behind LDS (in T-Proxy mode). (ER# 281550318)

LDS now supports the Suppress User Data feature in the same way that the feature is supported in T-Server 8.1 releases. (ER# 282586552)

LDS in T-Proxy mode now supports RequestStartCallMonitoring and RequestTransactionMonitoring. (ER# 172200898)

LDS in Load Distribution mode now supports unequal Receivers (Receivers registered on different DN sets). (ER# 191101733)

LDS now distributes a call that has not been routed to any available client(s) if the client that handled this call is disconnected. (ER# 191101735)

LDS now distributes EventPrimaryChanged from a High-Availability (HA) T-Server to the end client so that the client may perform required actions, such as querying calls or devices, and so on. (ER# 207718751)

LDS now provides to T-Server a unique client ID in AttributeExtensions for requests TReserveAgent and T ReserveAgentAndGetAccessNumber using the extension key lds-client-id. (ER# 226744879)

LDS now supports the same Client Session ID functionality as all T-Servers. (ER# 243996595)

When instructed by the Solution Control Server (SCS), LDS now correctly goes into backup mode if it delayed the previous SCS command to go to primary mode. Previously, after a switchover, both LDSs were running in primary mode. (ER# 277580784)

The LDS 32-bit executable can now be installed on all supported 64-bit UNIX operating systems. Previously, When installing LDS on a 64-bit UNIX host, the 32-bit executable could only be installed on Power PC 64-bit = AIX 5.1, 5.2, 5.3. (ER# 258977046)

There is no longer a temporary loss of connection between the Receiver and the backup LDS when the HA port in the backup LDS is a secure port. (ER# 258887071)

When installing LDS on a 32-bit UNIX host, the installation procedure now directly installs the 32-bit executable without providing the option to install the 64-bit executable. (ER# 255817061)

Top of Page

Documentation Corrections

This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.

The LDS Deployment Guide incorrectly states that changes to the configuration option ha-sync-level take effect immediately. Changes to this option take effect only on application restart.

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this prod uct.

In large environments with multiple StatServers and 1000+ DNs, the rate at which LDS in T-Proxy mode submits registration requests to T-Server can be significantly reduced. This can lead to long delays for StatServers to complete registrations in such environments.

Important: Customers who are using large environments of 1000+ DNs and currently running 8.1.007.01 or 8.1.008.00 should upgrade to version 8.1.009.00.

Antivirus software can affect system performance and call response time, but it prevents viruses from hiding in software. Genesys recommends keeping antivirus software enabled on hosts where Load Distribution Server is running. The performance of all applications on a particular host should be analyzed. Other application might be more vulnerable than Load Distribution Server. Consider moving some of those vulnerable applications to a different host. Genesys does not recommend excluding Load Distribution Server from the antivirus scanning, but in case of a significant overhead, you can consider disabling the following:

• The Load Distribution Server installation folder
• Any logs folders
• The LDServer.exe process on Windows
• The LDServer, LDServer_32 or LDServer_64 processes on Linux

The T-Server feature "logout-on-client-disconnect" does not work when the client is connected to T-Server through LDS running in T-Proxy mode. The feature works only when the client is directly connected to T-Server. (LDS-809)

To run LDS with startup request caching enabled (enable-startup-rq-caching=true), you must upgrade to LDS version 8.1.005.03 or later. (LDS-782)

LDS fully supports Location Monitoring in the "All Locations" mode. LDS implements Selective Location Monitoring ("One Location") by ensuring that all clients that have requested Selective Location Monitoring receive updates for other locations, requested through LDS by other LDS clients. (LDS-638)

The LDS deployment guide incorrectly states that configuration option ha-sync-level takes effect immediately. Changes to this option take effect only on application restart. (LDS-554)

LDS handles RequestDistributeEvent by emulating a mechanism that T-Server uses in backward-compatible mode. To ensure full transparency for clients, use the default value for the T-Server configuration option "req-distrib-event-support" = no-check. When the option is set to a non-default value, the T-Library client may experience different behavior when connected directly to T-Server and when connected to T-Server through LDS. (LDS-533)

It is recommended to keep the LDS enable-safe-handover configuration option set to the default value of false. If this option is set to true, the following issue may occur:

1. A call is delivered to a Routing Point and LDS selects a URS instance to handle this call.
2. An EventPartyChanged event with a new ConnectionId is distributed for this call.
3. The URS handling this call terminates unexpectedly.
4. Since the enable-safe-handover option is set to true, LDS now hands over this call to another URS instance by re-sending the EventRouteRequest with an incorrect ConnectionId, which subsequently cannot be routed.

Workaround: Keep the value of the enable-safe-handover configuration option set to the default value of false.

(ER# 318492553)

The strict-backup-name configuration option is incompatible with T-Proxy functionality.

Workaround: Keep the value of the strict-backup-name configuration option set to false when running Load Distribution Server (LDS) in T-Proxy mode.

(ER# 298446101)

LDS terminates unexpectedly when accepting a connection over a secure port if the Trusted Certificate file provided in the configuration does not exist. (ER# 283142181)

If an invalid port is specified for connection to the license server, LDS will force a shutdown after failing to connect. As it attempts to exit and shutdown, LDS becomes unstable and terminates unexpectedly. (ER# 272058566)

The enable-async-dns configuration option (located in the common section) does not support the value 1 (true) when both the primary and backup Load Distribution Server (LDS) are deployed on the same host in hot standby high-availability (HA) mode. (ER# 259990851)

The client-side port feature is not available while installing the LDS application, but the feature can be enabled after the application is installed. (ER# 259769251)

When installing LDS on a 64-bit UNIX host, the 32-bit executable can only be installed on the following platform:

• Power PC 64-bit = AIX 5.1, 5.2, 5.3.

(ER# 258977046)

Changes made to the Security properties on the Host tab will take effect after the application is restarted. (ER# 258887134)

LDS, running in high-availability (HA) hot standby mode, temporarily loses connection in the following scenario:

1. LDS opens the secure ports for listening.
2. The Receiver connects to LDS' secure port.
3. When the LDS switchover occurs, the Receiver loses connection with the primary LDS, and tries to connect to the backup LDS.

There is a temporary loss of connection between the Receiver and the backup LDS, because the Receiver has to exchange certificates for the secure connection to the backup LDS. This temporary loss of connection only happens when the HA port in the backup LDS is also a secure port. When this port is non-secure, there is no loss of connection.

(ER# 258887071)

A Call Concentrator (CCon) secure connection to LDS is not supported. (ER# 258831931)

When installing LDS on a 32-bit UNIX host, the installation procedure gives the option of installing a 32-bit executable or a 64-bit executable. Install the 32-bit executable on a 32-bit host. (ER# 255817061)

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

The Windows 2008 operating system is no longer supported.

The Solaris operating system is no longer supported.

The Red Hat Enterprise Linux 3.0 operating system is no longer supported.

The Tru64 UNIX operating system is no longer supported.

The AIX 5.1 and 5.2 operating systems are no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software.

• Framework 8.1 Load Distribution Server User's Guide provides instructions for installing and configuring and describes how to use Load Distribution Server.

Product documentation is provided on the Genesys Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page