Release Note

Configuration Server

8.0.x

Genesys Telecommunications Laboratories, Inc. © 2008–2011

Contents

Introduction

Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows
8.0.300.30_FRA – General X X X X X X
8.0.300.30 [10/08/10] – General X X X X X X
8.0.300.27 [09/22/10] – Hot Fix     X     X
8.0.300.14 [06/24/10] – General X X X X X X
8.0.200.10 [04/09/10] – Hot Fix     X      
8.0.200.09_FRA – General X X X X X X
8.0.200.09 [12/17/09] – General X X X X X X
8.0.100.18 [09/22/09] – General (Under Shipping Control) X X X X X X
8.0.000.09 [06/27/08] – General (Under Shipping Control) X X X X X X

Link to 7.6 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


Introduction

This release note applies to all 8.0 releases of Configuration Server for the French market.

Use of Third-Party Software

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


Release Number 8.0.300.30_FRA – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a generally available release for the French market. This localization is based on Configuration Server 8.0.300.30. Modifications to this software component in later software versions are not supported in this localized version.

Corrections and Modifications

There are no corrections or modifications in this release.

Top of Page


Release Number 8.0.300.30 [10/08/10] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

There are no restrictions for this release. This release does not contain new features or functionality.

Note: Following the initial Hot Fix release of this version of Configuration Server on the AIX, HP-UX, Solaris, and Windows platforms, Configuration Server 8.0.300.30 was tested on the Linux and Tru64 UNIX platforms. On October 25, 2010, the release type for all platforms changed from Hot Fix to General.

Corrections and Modifications

This release includes the following corrections and modifications:


Configuration Server startup performance is now improved when the history records contain large deltas. Previously, large deltas in the history records increased the time it took for Configuration Server to start. (ER# 261157107)


This release eliminates the memory leak that occurred in the following scenario:

Previously, Configuration Server experienced memory growth at a rate proportional to the rate of Person updates multiplied by the number of Configuration Server Proxies used.

(ER# 260503661)


Configuration Server Proxy in writable mode now updates its History Log correctly, thereby enabling a successful restoration of the client session if required. Previously, Configuration Server Proxy sometimes generated records with duplicate IDs that could not be written to the History Log, and therefore any restoration of a client session was incorrect.

Note: Both the master Configuration Server and Configuration Server Proxy must be updated to fix this problem.

(ER# 256659979)


A client of Configuration Server is now unable to restore a session with Configuration Server but has to reread the configuration if, while the client was not connected, one or more changes were made in the permissions of any objects to which the client was subscribed. Previously in this scenario, the client was able to restore the session to Configuration Server successfully, but did not receive all history notifications about these changes. (ER# 255472609)


After a series of switchovers, the Configuration Server that is running in Primary mode now has a complete view of the Configuration Database and recognizes incoming clients. Previously, the Configuration Server running in primary mode sometimes lost track of the Configuration Database and was unable to authenticate clients. (ER# 252107271, 234840756)


Top of Page


Release Number 8.0.300.27 [09/22/10] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a hot fix for this product. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


This release eliminates the memory leak that occurred in the following scenarios:

Previously, these memory leaks sometimes caused Configuration Server to terminate because of lack of memory.


Configuration Server Proxy now reads all configuration data correctly when it is using a schema version different than the master Configuration Server. To enable this, you must set the new configuration option fix_cs_version_7x to true in the master Configuration Server's configuration file confserv.cfg (Windows) or confserv.conf (UNIX). Previously, without this new option, Configuration Server Proxy would use an incorrect schema, and then read the data incompletely or incorrectly.

[confserv]
fix_cs_version_7x
Default Value: false
Valid Values: true, false
Changes Take Effect: After restart

Use this option when using a master Configuration Server running release 8.0.3 with a Configuration Server Proxy running a pre-8.0 version. Setting this option to true enables the master Configuration Server to treat Configuration Server Proxy as running an equivalent schema. This prevents Configuration Server Proxy from using an incorrect schema and reading configuration data incorrectly.

Note: Use this option only when migrating Configuration Server from a pre-8.0 version to the 8.0.3 version. This option does not apply to any other scenario.

(ER# 256484431)


Configuration Server now initializes correctly at restart. Previously, it initialized Virtual Agent Groups (VAGs) twice, generating the appropriate error messages, and started without being correctly initialized. (ER# 256025208)


Clients can again connect to the autodetect port of Configuration Server. Previously, after Configuration Server was upgraded to release 8.0.3, the autodetect port was unavailable. (ER# 255990856)


The backup Configuration Server now successfully switches to primary mode without rereading configuration data if it was disconnected from the primary Configuration Server at the same time as some clients were disconnecting from the primary Configuration Server. Previously in this scenario, the backup Configuration Server would delay switching to primary mode until it had reread the configuration data. (ER# 255250934)


Existing Virtual Agent Groups are now updated properly after a Skill object is deleted. (ER# 255110541)


Switchover of a backup Configuration Server Proxy to primary mode no longer occurs with incomplete data; switchover occurs only after the backup Configuration Server Proxy has completed reading all configuration data. In other words, the ports of the backup Configuration Server Proxy open only after all configuration data has been read.

Previously, even if the backup Configuration Server Proxy was in the process of reading configuration data, switchover would occur immediately. That is, Configuration Server opened its ports before all the configuration data was read. As a result, clients that subsequently reconnected to that Configuration Server Proxy had access to incomplete out-of-date data.

(ER# 254741973)


Configuration Server now loads 3-level annexes correctly, so that identical options (on the third level) in different sections (on the second level) can be read correctly. In previous releases, the data was read incorrectly, and clients using 3-level annexes sometimes received incorrect warnings when processing their data. (ER# 254381912)


Users whose passwords have been changed using the master Configuration Server after upgrading to 8.0.2 can now connect to an associated Configuration Server Proxy. This problem was specific to the HP-UX 64-bit platform. (ER# 254344366)


When using LDAP external authentication, Configuration Server no longer rejects authentication requests when an internal LDAP error occurs or if there is a communication link failure between Configuration Server and the LDAP Server. Previously in this scenario, Configuration Server would display an error message indicating that the user password was incorrect, but would not allow any user authenticated by LDAP to log in, regardless of password. The only way to fix the problem was to restart Configuration Server. (ER# 254162157)


ADDP now works properly between the master Configuration Server and Configuration Server Proxies with which it is associated. Previously, the master Configuration Server started sending ADDP polling to Configuration Server Proxy while it was initializing. This sometimes caused Configuration Server Proxy to disconnect from the master Configuration Server because of the expiration of the ADDP timeout (specified by the configuration option addp-timeout). (ER# 254155311)


If unexpected internal errors are detected, Configuration Server now generates log event 00-09999 for further diagnosis. Previously, Configuration Server did not generate the log event, and would terminate instead.

Note: 00-09999 can be used as an alarm generation event for the detection and diagnosis of internal Configuration Server errors.

(ER# 253329622, 226575276)


Configuration Server no longer terminates unexpectedly when it finishes processing a large XML update that contains multiple add and delete commands for one object, and that is received from a client using the SOAP port. (ER# 250722183)


Previously, Configuration Server Proxy sometimes terminated when its clients disconnected after it had lost its connection with the master Configuration Server. This issue has been fixed. (ER# 244020354)


The backup Configuration Server no longer terminates if, after being instructed to switch to Primary mode, it is instructed to switch to Backup mode before it has completed processing the earlier request. The proximity of the two requests may be the result of a network outage on the host where the original primary Configuration Server is running.

Previously, the backup Configuration Server terminated if it received two opposing requests (switch to primary and switch to backup) consecutively and within a short period of time.

(ER# 242922873, 223607407, 223382342, 135171302)


In a redundant configuration, the primary and backup Configuration Servers can start simultaneously. Previously, one or both of the two servers in the redundant pair sometimes stopped executing. (ER# 236730387, 232761114, 227204269, 219446302)


After losing its connection with the main Configuration Server while reading configuration data, Configuration Server Proxy now reconnects automatically to the main Configuration Server and continues executing. Previously, Configuration Server Proxy would sometimes just terminate. (ER# 236050710)


Configuration Server no longer terminates when an unexpected request is received through the SOAP port. (ER# 226894211)


Configuration Server no longer produces a core file during shut down. Previously, Configuration Server sometimes produced a core file while closing communication channels with client applications for which unprocessed data still existed in the incoming queue. (ER# 225226451)


Configuration Server now logs which ports it cannot open. (ER# 106201080)


Top of Page


Release Number 8.0.300.14 [06/24/10] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release also includes the following corrections and modifications:


Configuration Server now recalculates Virtual Agent Groups in the following scenario:

  1. Configuration Server loses its connection with DB Server and runs in Read-Only mode.
  2. Configuration Server restores the connection with DB Server, and rereads configuration data.

Previously in this scenario, Virtual Agent Groups were not initialized and remained empty.

(ER# 253091582)


Configuration Server now correctly sends to the client all Campaign Group data. Previously, the value in the Voice Transfer DN field was lost during data transfer. (ER# 252470958)


Configuration Server now correctly sends error messages to the appropriate clients. Previously, it sometimes sent error messages relating to previous requests to clients for which requests were being processed. (ER# 246969072)


The text of log events 00-04503 and 00-04504 now include the attribute [server name] as specified in Framework Combined Log Events Help. (ER# 223692755)


Top of Page


Release Number 8.0.200.10 [04/09/10] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release includes the following correction and modification:


Configuration Server now operates properly after sending a series of authentication requests to the LDAP external authentication module. Previously, Configuration Server sometimes terminated on UNIX platforms. On Windows platforms, the LDAP module sometimes terminated unexpectedly and Configuration Server continued running with no active LDAP authentication. (ER# 247452757)


Top of Page


Release Number 8.0.200.09_FRA – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This is a generally available release for the French market. This localization is based on Configuration Server 8.0.200.09. Modifications to this software component in later software versions are not supported in this localized version.

Corrections and Modifications

This release contains no corrections or modifications.

Top of Page


Release Number 8.0.200.09 [12/17/09] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

Corrections and Modifications

This release also includes the following corrections and modifications:


When the configuration option allow-empty-password is set to false, Configuration Server no longer allows you to create a Person/User with an empty (blank) password, or to change a password to such a value. Previously, a user could have an empty password, but could not log in with it. (ER# 170899385)


Configuration Server now accepts non-ASCII characters in LDAP authentication requests. (ER# 221506513)


Overriding the default LDAP search filter at the Person level (in the field External User ID) now works properly. (ER# 230620003)


Configuration Server no longer permits the deletion of an Agent Group if it is linked to a Campaign Group. (ER# 233398345)


If both LDAP and RADIUS external authentication modules are specified by the library option, and the file ldapclient.conf already exists in the installation directory, you can use both LDAP and RADIUS as configured. Previously in this case, the RADIUS module was not loaded during Configuration Server startup. (ER# 235046513)


In the following scenario, Configuration Server Proxy now uses RADIUS external authentication as configured:

  1. LDAP external authentication is configured on the master Configuration Server.
  2. RADIUS external authentication is configured on Configuration Server Proxy.
  3. Configuration Server Proxy tries to authorize a client with an empty External User ID field.

Previously, Configuration Server Proxy would perform only internal authorization.

(ER# 235405581)


Configuration Server now responds correctly to authentication requests when LDAP external authentication is used and the LDAP API functions return negative error codes. (ER# 235821515)


Configuration Server now displays the correct version of the external LDAP library in logs. (ER# 236245933)


Top of Page


Release Number 8.0.100.18 [09/22/09] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Configuration Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


Configuration Server no longer permits a user with an empty password to insert any string of characters as their old password when changing their password. Such requests are rejected, and an error message generated. (ER# 222069795)


Configuration Server now accepts and stores blank (empty) configuration option values. Previously, such values could not be stored in the Configuration Database. (ER# 216459073, 217700045)


Top of Page


Release Number 8.0.000.09 [06/27/08] – General (Under Shipping Control)

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Configuration Server.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:


In debug logs, Agents skill levels changed to 0 (zero) are displayed as level deleted. Previously, the value of the skill level before the change was displayed. (ER# 144342854)


Obsolete application type SIP Communication Server is no longer supported by Configuration Server, and does not appear as an option in any list. (ER# 150229301)


Configuration Server now uses the specified retry-attempts and retry-interval values specified for LDAP external authentication. Previously, Configuration Server ignored the specified values and used the default values instead. (ER# 150236199)


Configuration Server no longer terminates when working with external authentication. Previously, under a heavy load, Configuration Server sometimes terminated abnormally when trying to externally authenticate a user. (ER# 176892421)


Configuration Server initialization now completes successfully in those cases where Advanced Disconnect Detection Protocol (ADDP) is activated between Configuration Server and Configuration DB Server. Previously, when the ADDP timeout was short enough and the Configuration Database large enough, sometimes the ADDP timeout expired and prevented the proper initialization of Configuration Server. (ER# 182717445)


Top of Page


Known Issues and Recommendations

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


Do not configure auto-restart for both the primary and backup Configuration Servers in a redundant pair.


Existing Virtual Agent Groups are not updated if a skill object is deleted. (ER# 255110541)

Found In: 8.0.300.14 Fixed In: 8.0.300.27

Last Login information is not synchronized between the main Configuration Server and Configuration Server Proxies. For example, if a user logs in to the main Configuration Server, then logs in to a Configuration Server Proxy, the Last Login information displayed the second time does not reflect the login attempt to the main Configuration Server, but only the last login attempt to that Configuration Server Proxy.

Workaround: To avoid this, Genesys recommends that users always log in through the same Configuration Server (main or Proxy).

(ER# 241981648 )

Found In: 8.0.200.09 Fixed In: 

Consider the scenario in which LDAP external authentication is configured on the master Configuration Server and RADIUS external authentication is configured on Configuration Server Proxy. If, in this case, Configuration Server Proxy tries to authorize a client with an empty External User ID field, Configuration Server Proxy performs internal authorization. (ER# 235405581)

Found In: 8.0.100.18 Fixed In: 8.0.200.09

If both LDAP and RADIUS external authentication are configured, you cannot use the file ldapclient.conf. You can only specify one LDAP server in the Configuration Server configuration file (confserv.cfg or confserv.conf). (ER# 235046513)

Found In: 8.0.100.18 Fixed In: 8.0.200.09

Configuration Server erroneously permits the deletion of an Agent Group even if it is linked to a Campaign Group. (ER# 233398345)

Found In: 8.0.100.18 Fixed In: 8.0.200.09

Overriding the default LDAP search filter at the Person level (in the field External User ID) does not work properly. (ER# 230620003)

Found In: 8.0.100.18 Fixed In: 8.0.200.09

Tenant names must not contain one or more backslash characters (\). (ER# 229940114)

Found In: 8.0.100.18 Fixed In: 

The Framework 8.0 External Authentication Reference Manual contains incorrect descriptions of the configuration option library and the section in which it is contained, authentication. The correct descriptions are:

[authentication]
This section indicates that RADIUS external identification is to be used.

library
Specifies gauth_radius as the section that specifies the output level for debugging information produced by the Authentication Module. This option is mandatory, and its value is set automatically during installation.

Example: The following is an example of the authentication section in a Configuration Server configuration file:

   [authentication]
   library=gauth_radius

(ER# 215640647)

Found In: Document version 80fr_ref-exta_06-2008_v8.0.001.00 Fixed In: Document version 80fr_ref-exta_09-2009_v8.0.101.00


Configuration Server in Proxy mode cannot be deployed using the Web Deployment Tool in Genesys Administrator. Use the manual deployment process described in the Framework 8.0 Deployment Guide instead. (ER# 193827147)

Found In: 8.0.000.09 Fixed In: 

Configuration Server does not accept non-ASCII characters in LDAP authentication requests. (ER# 221506513)

Found In: 7.6.000.08 Fixed In: 8.0.200.09

If the backup Configuration Server has log options configured the same in both the Application object and in its local configuration file, it may not switch over to Primary mode correctly when required.

Workaround: Configure log options in the configuration file, not in the Application object.

(ER# 156491260)

Found In: 7.6.000.04 Fixed In: 

Configuration Server does not log which ports it cannot open. (ER# 106201080)

Found In: 7.5.000.11 Fixed In: 8.0.300.27

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.


HP-UX 11.00 is no longer supported.

Discontinued As Of: 8.0.100.18

Solaris 7 is no longer supported.

Discontinued As Of: 8.0.100.18

Windows 2000 is no longer supported.

Discontinued As Of: 8.0.100.18

Top of Page


Internationalization

Information in this section is included for international customers.


There are no limitations or restrictions for internationalization.


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. Please consult the Genesys Administrator Deployment Guide first.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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