Release Note

Contents

Introduction

This release note applies to all 7.2 releases of Load Distribution Server.

• 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 Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• 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. Please contact your technical support representative if you have any questions.

Supported Operating Systems

New in This Release

This is a hot fix for this product. No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications:

Load Distribution Server (LDS) no longer becomes unstable after Universal Routing Server or T-Server has disconnected under high request volume or from a significant network delay. (ER# 276455727)

Load Distribution Server (LDS) now distributes the LMS message Std 04503 Connected to CfgServer '' at host '<hostname>', port <port> upon startup. Previously, while this message was provided in Load Distribution Server releases 7.2.003.09 and earlier, it was omitted in releases after 7.2.003.09. (ER# 276704489)

This release of Load Distribution Server (LDS) now supports rolling upgrades from pre-7.2.1 Load Distribution Server releases. (ER# 276648971)

Load Distribution Server (LDS) now creates the appropriate backup synchronization links when running on the same HP-UX or Solaris host. Previously, when primary and backup LDS instances were set up to be running on the same host under HP-UX and Solaris, backup synchronization links between LDS instances may have not been created. (ER# 276704482)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications:

Load Distribution Server (LDS) no longer fails when an application that is configured in the same tenant as LDS, but is unknown to LDS, is deleted. Previously, LDS only maintained configuration information for the following Configuration Manager application types: MessageServer, ConfigurationServer, TServer, Universal Routing Server, Call Concentrator and Load Distribution Server. All other application types were unknown to LDS. (ER# 270425019)

Load Distribution Server (LDS) now ignores all events received with RefID -1, other than the EventAck event, which is now correctly matched to an outstanding request from an LDS client in configurations where the following conditions occur:

• There is a large network delay between LDS and T-Server.
• There are client applications, such as URS, connected to LDS and to T-Server directly and these monitor the same DNs.
• These clients use the RequestDistributeEvent functionality of T-Server on DNs monitored by both applications.

Previously, LDS matched events received with RefID -1 as a result of a RequestDistributeEvent request from a client connected directly to T-Server with an outstanding RequestDistributeEvent event from an LDS client.

(ER# 268791780)

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:

• The following log events are new in Load Distribution Server (LDS) 7.2.101.00, but are not documented in the Log Events Help:

  83-39557
  Level:	Standard
  Text:	HA synchronization queue overflow end
  Attributes:	None
  Description:	This message is generated when the high-availability (HA) synchronization queue size in the current configuration is smaller than the number of synchronization messages received from the primary LDS on a sender-per-sender basis.
  Actions:	No actions.

  83-39514
  Level:	Trace
  Text:	Sender (%s) HA synchronization queue overflow
  Attributes:	(%s) T-Server name (per T-Server for troubleshooting)
  Actions:	No action required.

  83-39515
  Level:	Trace
  Text:	Sender (%s) HA synchronization queue overflow end
  Attributes:	(%s) T-Server name (per T-Server for troubleshooting)
  Actions:	No action required.

• The following new configuration option is introduced with this release.

  tlib-verbose
  Default Value: 0
  Valid Values: 0, 1, 2
  Changes Take Effect: Immediately

  When set to a value of 0 (zero), the T-Library debug messages are switched off. When set to a value of 1, the T-Library debug messages are set to a medium verbosity level, and if the value is set to 2, the T-Library debug messages are set to a high verbosity level.

  (ER# 265137740)

Corrections and Modifications

This release includes the following corrections and modifications:

The conditions for generating the LMS message 83-39541 Backup Link configuration failure have been changed. LDS now issues this message when a backup application is configured incorrectly (incorrect host, incorrect application, etc). (ER# 264722930)

LDS, running in Load Distribution Mode, now correctly clears all calls from its memory. Previously, this may have caused excessive memory usage. (ER# 264701218)

LDS no longer fails to reconnect with T-Servers, which are running in a primary/backup high-availability environment, when the T-Servers are restarted after their configuration parameters have been changed. (ER# 264504125)

LDS no longer fails to distribute events to URS from a remote T-Server when local a T-Server reports a call deletion before an ISCC RemoteConnectionSuccess event. (ER# 263653326)

URS uses an arbitrary value of -1 for AttributeReferenceID when submitting a RequestDistributeEvent to T-Server. A Reference ID with a value of -1 distributed in the requested event is ignored by other T-Server clients. LDS (or T-Proxy) relays the request from URS to T-Server and changes the arbitrary value of -1 for AttributeReferenceID to another value.

LDS now keeps an arbitrary value unchanged when a RequestDistributeEvent request, having an AttributeReferenceID value of -1, is submitted to T-Server. Previously, under rare circumstances, a Reference ID may have matched another request and caused an incorrect event distribution by LDS (T-Proxy).

(ER# 262912322)

LDS no longer fails to reconnect to a running Configuration Server instance in a scenario where, after successful connection to a primary Configuration Server, both Configuration Servers (primary and backup) are stopped, and only the backup Configuration Server is restarted. (ER# 263450853)

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 Microsoft Windows Server 2008 running on 32-bit and 64-bit platforms. (ER# 256312898)

• Support for HP-UX 11iv3 on 64-bit) operating system, running on PA-RISC. (ER# 256312883)

• Support for Linux 32-bit operating system running on Intel, versions 3.0, 4.0, and 5.0. (ER# 256312861)

• Support for IBM AIX 6.1 64-bit operating system. (ER# 256312856)

• Support for IBM AIX versions 5.1, 5.2, and 5.3 32 - and 64-bit operating systems. (ER# 256312851).

• Support for client-side port definition between Genesys applications.

• Support for updated operating systems and virtualization environments.

• Support for Genesys Transport Layer Security (TLS), which can be configured for secure data exchange with Senders, Receivers, and other Genesys components that support this functionality.

• The following log events are new in Load Distribution Server (LDS) 7.2.100.08, but are not documented in the Log Events Help:

  83-39525
  Level:	Trace
  Text:	Client [client-id] for transaction [transaction-id] is not registered on DN [DN]
  Attributes:	[client-id] String that indicates the client name.
  	[transaction-id] String that provides the transaction identifier (connection ID of the call).
  	[DN] String that provides a DN where the transaction took place.
  Description:	This message is generated when a transaction, assigned to a Receiver, appears on a DN that is not monitored by that Receiver.
  Actions:	Verify whether all LDS receivers are operational and have identical configuration.

  83-39526
  Level:	Standard
  Text:	Transaction [transaction-id] event lost
  Attributes:	[transaction-id] String that provides transaction identifier (connection ID of the call).
  Description:	This message is generated when a transaction has no assigned Receivers anymore (for example, due to the disconnection of a previously assigned Receiver).
  Actions:	Verify whether all LDS receivers are operational and have identical configuration.

  83-39534
  Level:	Standard
  Text:	No clients for Transaction [transaction-id]
  Attributes:	[transaction-id] String that provides transaction identifier (connection ID of the call).
  Description:	This message is generated when a new transaction has no assigned Receivers.
  Actions:	Verify whether all LDS receivers are operational.

  83-39541
  Level:	Standard
  Text:	Backup Link configuration failure
  Attributes:	None
  Description:	This message is generated when a configuration for a backup link is either incorrect or cannot be retrieved from the Configuration Layer.
  Actions:	Check primary/backup LDS configuration.

  83-39554
  Level:	Standard
  Text:	LDS role changed to [role-id]
  Attributes:	[transaction-id] String that indicates a role name (primary, backup, or unknown)
  Description:	This message is generated when the LDS role is changed.
  Actions:	No actions - Information only.

  83-39555
  Level:	Standard
  Text:	Invalid (unknown) role for LDS was requested
  Attributes:	None
  Description:	This message is generated when LDS is requested to change to an unrecognized role.
  Actions:	No actions - Information only.

  83-39556
  Level:	Standard
  Text:	HA synchronization queue overflow
  Attributes:	None
  Description:	This message is generated when the high-availability (HA) synchronization queue size in the current configuration is smaller than the number of synchronization messages received from the primary LDS.
  Actions:	No actions, but may indicate very high load or high network latency.

Corrections and Modifications

This release includes the following corrections and modifications:

Load Distribution Server (LDS) now correctly tries to reconnect to a primary Configuration Server if the primary and backup Configuration Servers are configured, but only the primary is available and restarted. Previously, LDS would try to reconnect to the Configuration Server that was configured as backup, even if it was not started. LDS did not attempt to reconnect to the Configuration Server that was configured as primary, even after that Configuration Server was restarted. There was no issue in reconnecting to Configuration Server if both the primary and backup Configuration Servers were running at the same time that the current Configuration Server was restarted. (ER# 259469366)

This release has been built with the latest libraries. (ER# 259310220, ER# 250318219, ER# 250241098, ER# 227680304)

LDS now uses the Connection tab properties — for example, Advanced Disconnect Detection Protocol (ADDP) — of the Application object that LDS connects to directly. Previously, LDS used the connection properties of the last Application in the list. (ER# 258146600)

LDS now correctly connects to Message Server, if a connection to Message Server is added to the Connections tab of the LDS Application object after LDS is started. Previously, LDS would not attempt to connect to Message Server until LDS was restarted. (ER# 255261303)

LDS now correctly handles the EventError for the TRegisterAddress on the DN specified in the configuration option query-dn of the connected T-Server. Previously, LDS might have terminated unexpectedly upon receiving such an EventError. (ER# 254109756, ER# 253768846)

LDS now correctly handles the primary and backup Configuration Server information without any errors. Previously, LDS became unresponsive when the switchover of Configuration Server occured more than once. (ER# 245396133)

LDS now properly handles the kill command in a UNIX environment. Previously, LDS could cause an exception if the kill command was used to stop LDS in a UNIX environment while LDS was still starting up. (ER# 88100201)

LDS now properly handles the active calls routed through an LDS client. Previously, a problem could occur if LDS was configured in hot standby high availability (HA) mode with URS as its client. (ER# 59185162)

LDS now properly handles the following scenario:

In tiered TProxy mode with LDS running in HA mode, the primary LDS that is connected to T-Server is disconnected from the network. The backup LDS then becomes primary. The old primary is then reconnected to the network and switchover is requested from Solution Control Interface (SCI) in order to return it to primary status.

Previously, the switchover did not occur correctly and EventPrimaryChanged was not generated. (ER# 43965891)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications:

Load Distribution Server (LDS) now reliably establishes connections to Message Server and Configuration Server when running on a 64-bit UNIX platform. Previously, LDS sometimes failed to establish these connections. (ER# 254367731)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications:

Load Distribution Server (LDS) no longer forwards EventLinkConnected and EventLinkDisconnected messages from T-Server to its clients. These messages may contain attributes that could be incorrectly interpreted by T-Server clients. (ER# 242502503, 232082023)

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.

• Load Distribution Server (LDS) now properly handles the creation and deletion of the application type T-Server and LoadDistributionServer in Configuration Manager.

  Note: This enhancement is not intended to support the moving of applications between folders with no access rights configured instead of deleting those applications in Configuration Manager.

  (ER# 235576384)

Corrections and Modifications

There are no corrections or modifications in this release.

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications since the previous release of this software:

Load Distribution Server (LDS) has been modified to ensure that, when the link is disconnected, client requests to T-Server are not blocked. As a result of this modification, configuration option validate-sender has become redundant and has been removed. (ER# 229350740)

The handing of connections between LDS in T-Proxy mode and the configured switch has been modified. Previously, LDS rejected some connection requests in chained LDS configurations because acceptance criteria were unnecessarily stringent. (ER# 230091956)

  Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications since the previous release of this software:

In complex configuration environments when a switchover occurred, Load Distribution Server (LDS) was incorrectly interpreting some connections to applications as potential proxies, and subsequently overriding accesses to T-Servers that were configured in the LDS's Connections tab, resulting in connection failures. This processing has now been modified to eliminate the possibility of such overrides. (ER# 226161565)

LDS is modified to ensure that it reconnects correctly to a T-Server running in Warm Standby mode. This scenario occurred when LDS and the primary Warm Standby T-Server were running on the same Solaris host and a switchover occurred. (ER# 227226041)

  Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release includes the following corrections and modifications since the previous release of this software:

Processing of the register-guard timer expiration has been modified to ensure even load distribution in scenarios where one of multiple Universal Routing Servers disconnects and then reconnects. (ER# 215479733)

Load Distribution Server (LDS) interaction with Management Layer has been modified to ensure that switching from primary to backup mode takes place only on receipt of the relevant Management Layer messaging. Previously, an incompatibility in this area caused the sending of incorrect EventRouteRequest messages. (ER# 211877959)

LDS is modified to ensure correct handling of reconnect requests from clients. Previously, notification about changes in T-Servers configured in a multi-site environment, but not related to LDS (T-Proxy), were being incorrectly processed as LDS / T-Proxy configuration changes. Additional verification is now applied to prevent this happening. (ER# 214436078)

Extension filtering has been removed from LDS in TProxy mode. (ER# 215505700)

TProxy mode only: The default value of configuration option ha-sync-level for LDS in TProxy mode has been changed to 1 (one). Value 0 (zero) has also been reinstated (it was previously disabled), though setting this value may cause message loss during backup/primary T-Proxy switchover or failover, because events distributed by T-Server at the time of changing the role and applying an Input Mask can be masked out. (ER# 218027143)

  Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

Configuration readings from Configuration Server to Load Distribution Server (LDS) in TProxy mode have been optimized. (ER# 160102654)

Call deletion processing has been refined to reduce network traffic. (ER# 135461019)

Load Distribution Server (LDS) is modified to enable filtering out of unnecessary ConnID-related extension keys from EventRegistered and EventAddressInfo. This prevents distribution of unnecessary extension keys to clients that would not make use of them. A new configuration option controls this functionality:

• keep-ext-key
  Default Value: No default value
  Valid Values: Comma-separated list of extensions
  Changes Take Effect: Immediately
  

  Specifies a list of extensions that will be preserved when LDS removes ConnID-related extensions from events EventRegistered and EventAddressInfo during call cleanup routines.

(ER# 159612401)

LDS has been modified to enable the safe addition or removal of a T-Server regardless of the state of its connection to LDS. Previously in some circumstances, adding or removing a T-Server connection could cause LDS to fail. (ER# 104130622)

LDS processing of client reconnections in TProxy mode has been modified. The input mask is now stored on a client-by-client basis in TProxy mode. (ER# 94019421)

A problem with large numbers of TQueryCall requests for a single call has been corrected. (ER# 125207188)

LDS has been modified to ensure correct handling of T-Server events with an attached KV list in excess of 64Kb. (ER# 181623068)

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

Load Distribution Server (LDS) has been modified to process external QueryCall requests in the same way as other client requests. Previously, LDS incorrectly processed expirations for QueryCall requests when they came from clients. This caused some live calls to be deleted and wrong information to be sent to clients, causing LDS to stop processing route requests. (ER# 134310106)

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

A memory leak during normal Load Distribution Server (LDS) operation has been corrected. Previously, LDS was failing to handle a scenario in which EventError with a deleted Conn ID arrived after EventReleased on an abstract DN. In these circumstances, the Conn ID was not deleted from memory. LDS now cleans up the call correctly. (ER# 120446585)

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

Load Distribution Server (LDS) processing of EventAddressInfo has been modified. Previously, LDS was not able to handle EventAddressInfo with no AttributeExtensions or with a KVList bigger than 64K. This was causing LDS to fail. LDS is now able to handle both these scenarios. (ER# 65707617, 82808743)

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

A problem has been fixed when Load Distribution Server (LDS) runs in Hot Standby with Universal Route Servers as clients. In previous versions of LDS, a network delay on the primary LDS could result in both the primary and backup LDSs sending a call to the client or clients. This could result in two Universal Route Servers attempting to route the same call. (ER# 55064094)

New configuration option rq-expire-timeout is introduced in this release:

• rq-expire-timeout
  Default Value: 120
  Valid Values: Any integer from 10-600
  Changes Take Effect: Immediately
  Specifies the interval (in seconds) that LDS waits before deleting pending requests from clients.

Top of Page

Supported Operating Systems

New in This Release

No new features were introduced in this release of Load Distribution Server.

Corrections and Modifications

This release contains the following corrections and modifications:

Load Distribution Server's (LDS) startup procedure has been modified to prevent a problem where LDS would repeatedly time out and then restart, and therefore never initialize correctly. This issue can occur in large multiple LDS environments or large environments with slow networks. Previously a hard-coded timer was invoked which prevented completion. Now, LDS continues the connection procedure without interruption as long as there is activity from the Configuration Server side. (ER# 40036008)

The LDS client disconnection procedure has been corrected to ensure correct updating of the DN client record. Previously, in TProxy mode, LDS was failing to delete the client list when the last DN for a client disconnected, resulting in a later LDS failure when events were received for that DN. (ER# 40030285)

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 7.2 release of Load Distribution Server.

• Support for new operating systems:
  • Red Hat Linux version 4.0 (ER# 16888271)
  • HP Compaq TRU64/Alpha version 5.1B (ER# 16888274)
  • Solaris/Sparc 10 32/64-bit version 2.10 (ER# 16888248)
  • Microsoft Windows Server version Windows 2003 32 and 64-bit. (ER# 16888245)

• Support for rolling upgrades: In release 7.2, when a backup LDS connects, the primary LDS marks all existing transactions as "not synchronized" and prevents the switchover request from Solution Control Interface. As soon as all marked transactions are removed, switchover becomes possible. This features is controlled by configuration options ha-dly-switchover and max-update-rate. (ER# 16888369)

• Enhanced extended HA client support: In release 7.2 a new attribute EventSequenceId has been implemented to improve extended HA client support. (ER# 16888277)

Corrections and Modifications

There are no corrections or modifications in this initial 7.2 release.

Top of Page

Known Issues and Recommendations

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

Support for Media Server T-Servers is not implemented. Premise and Network T-Servers are fully supported.

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)

LDS occasionally causes an exception if the kill command is used to stop LDS in a UNIX environment while LDS is still starting up. (ER# 88100201)

The following problem can occur if LDS is configured in hot standby high availability (HA) mode with Univeral Routing Servers as its clients: if there is a short network delay on the primary LDS, when a call that is active in T-Server has been routed through an LDS client, LDS continually sends RequestQueryCall. (ER# 59185162)

In the following scenario the switchover does not occur correctly and therefore no EventPrimaryChanged is generated:

In tiered TProxy mode with LDS running in HA mode, the primary LDS that is connected to T-Server is disconnected from the network. The backup then becomes primary. The old primary is then reconnected to the network and switchover is requested from SCI in order to return it to primary status. In order to overcome the problem, Genesys recommends restarting the old primary once reconnected to the network and then performing switchover. (ER# 43965891)

Synchronization of primary and backup instances of LDS at startup has not been implemented because of network/application overloading. (ER# 16888369)

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.

The Solaris 2.6 and Solaris 7 32-bit operating systems and the Solaris 7 64-bit operating system are no longer supported. (ER# 256312903)

The Microsoft Windows 2000 Server 32-bit operating system is no longer supported. (ER# 256312893)

The HP-UX 11.0 32-bit and 64-bit operating systems are no longer supported. (ER# 256312888)

The Windows NT operating system is no longer supported. (ER# 16888288)

Top of Page

Internationalization

Information in this section is included for international customers.

There are no specific issues for international customers.

Top of Page

Additional Information

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

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

Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.

Top of Page