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.genesyslab.com for more details.
This release note applies to all 7.6 releases of Configuration Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction or modification:
Configuration Server now correctly handles SOAP requests that contain XML
entities such as '
. Previously, requests containing
this and similar XML entities sometimes caused Configuration Server to
terminate unexpectedly. (ER# 313403327 [305818435])
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
In several scenarios in which Configuration Server is configured for external authentication using LDAP, memory leaks and unexpected terminations were identified and fixed. (ER# 298639921 [298532351, 296915383, 295417154, 289761437, 259528441, 254162157])
On Windows platforms, Configuration Server no longer terminates unexpectedly
with the unhandled exception STATUS_RESOURCE_NOT_OWNED (ExceptionCode:
0xc0000264
) after processing 0x7fffffff
(2147483647 in
decimal) requests. (ER# 303830469)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Configuration Server Proxy no longer produces a core file when the connection to the master Configuration Server is lost while retrieving data from the master Configuration Server. (ER# 288471547, 288453370)
Configuration Server Proxy now properly handles SOAP requests to update objects. Previously, Configuration Server Proxy would terminate unexpectedly when it received a SOAP request to update an object, resulting in a transaction rollback. (ER# 300110625, 284519253)
Case-insensitive searches in Configuration Server now function properly,
even if wildcards are used. Previously in this scenario, the search
mechanism sometimes returned a case-sensitive search result. For example,
a case-insensitive search for *BC*
now returns ABCD
and abcd
. Previously, this search returned only ABCD
.
(ER# 284247665)
Configuration Server no longer terminates when Interaction Routing Designer (IRD) tries to connect. Previously, Configuration Server would sometimes terminate unexpectedly when IRD tried to establish a connection with Configuration Server. (ER# 284114553)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release introduces the following new feature and functionality:
Advanced Disconnect Detection Protocol (ADDP) is now supported between
primary and backup Configuration Servers. Use the new configuration options
protocol
, addp-timeout
,
addp-remote-timeout
, and addp-trace
, setting
them in the configuration server section of the configuration files for
both Configuration Servers. For the primary Configuration Server, this
section is called confserv
. For the backup Configuration
Server, this section has the same name as the backup Configuration Server
Application
object.
protocol
Default Value: No default value
Valid Values: addp
Changes Take Effect: After restart
Specifies if ADDP is to be used between the primary and backup Configuration
Servers. If set to addp
, the ADDP protocol is implemented as
defined by the ADDP-related configuration options addp-timeout
,
addp-remote-timeout
, and addp-trace
in the same
configuration server section (confserv
, or its equivalent in
the backup Configuration Server) of the configuration file. If this option
is set to any other value, or if it is not specified at all, ADDP is not
used and the ADDP-related configuration options in this section are ignored.
Note: The three options below have the same names as other options that already exist in Genesys software. While all are used to implement ADDP, the placement of each option (in the configuration section and, in some cases, configuration object) is unique and determines the use thereof. The options described below do not replace these pre-existing options.
addp-timeout
Default Value: 0
Valid Values: 0–3600
Changes Take Effect: After restart
Specifies the time interval, in seconds, that Configuration Server in backup
mode waits before polling the other Configuration Server in the redundant
pair. If set to zero (0
), Configuration Server in backup mode
does not poll the other Configuration Server in the redundant pair. This
option applies only if the value of the protocol
option is
addp
.
Note: Because any Configuration Server can be in primary or backup mode, regardless of how it is configured, you must set this option to the same value in both the primary and backup Configuration Servers.
addp-remote-timeout
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: After restart
Specifies the time interval, in seconds, that Configuration Server in
backup mode instructs the other Configuration Server in the redundant pair
to use when polling to check the connection between the two servers. If
set to zero (0
), Configuration Server in backup mode does not
send any such instruction. This option applies only if the value of
the protocol
option is addp
.
Note: Because any Configuration Server can be in primary or backup mode, regardless of how it is configured, you must set this option to the same value in both the primary and backup Configuration Servers.
addp-trace
Default Value: off
Valid Values:
false , no , off |
No ADDP trace occurs | |
true , yes , on ,
local |
ADDP trace occurs on the side of the Configuration Server in backup mode. | |
remote |
ADDP trace occurs on the side of the Configuration Server in primary mode. | |
both , full |
ADDP trace occurs at both the primary and backup Configuration Servers. |
protocol
option is addp
.
Example: In the Configuration Server configuration file, the ADDP
options would appear as follows:
[confserv]
...
protocol=addp
addp-timeout=16
addp-remote-timeout=32
addp-trace=both
...
For more information about ADDP, refer to the Framework 7.6 Deployment Guide.
Note: ADDP is disabled while the backup Configuration Server is initially reading configuration data, or rereading it after reconnection, from the primary Configuration Server.
(ER# 254468865)
This release includes the following corrections and modifications:
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# 264368384, 261378006)
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 and out-of-date data.
(ER# 254741973)
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.
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)
Configuration Server no longer terminates when an unexpected request is received through the SOAP port. (ER# 226894211)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server can now accept significantly more simultaneous connection requests from clients that are using Simple Object Access Protocol (SOAP), storing them in the SOAP port backlog until each one can be processed. This means that there is much less of a chance that a SOAP connection request will be rejected because of the volume of these requests. (ER# 242558062)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
This release eliminates the memory leak that occurred if Configuration Server had to reconnect to DB Server and reload configuration data.
In addition, this release also introduces a new option, objects-cache
,
which can be used to switch off internal caching by Configuration Server.
This reduces the amount of memory used by Configuration Server.
objects-cache
Default Value: true
Valid Values: true
, false
Changes Take Effect: After restart
Specifies if Configuration Server should cache objects requested by
client applications. If set to true
, Configuration Server
behavior is unchanged from previous versions. If set to false
,
the objects are not cached. To use this option, manually add this option
to the Configuration Server configuration file in the Configuration Server
(confserv
) section.
This option can also be used for Configuration Server running in Proxy mode.
In this case, set this option on the Options
tab of the
Configuration Server Proxy Application
object, in the
csproxy
section.
Note: Disabling the cache may increase the load on Configuration Server (Proxy) during client application registration. Please use this option with care.
(ER# 250145528)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now transfers data successfully to clients that are accepting the data slower than Configuration Server can send it. Previously, Configuration Server consumed 90-100% of CPU time. In addition, the client's response timeout sometimes expired, causing the client to disconnect from Configuration Server. (ER# 245115064)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Configuration Server now properly handles SOAP requests. Previously, in some cases, Configuration Server terminated unexpectedly while processing a SOAP request. (ER# 239090877)
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. (ER# 225226451)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
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, starting in release 7.6.000.52, 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# 244224611)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Clients of Configuration Server now receive correct updates from the History Log in the following scenario:
0
).Previously, the update sent to the client did not include the change to the Skill level, so the Skill level was not changed as requested.
(ER# 239528131)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer terminates because of memory allocation problems. Previously, but in very rare cases, Configuration Server terminated unexpectedly because of memory allocation problems in internal storage. (ER# 196142276)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release introduces the following new feature and functionality:
This release includes the following correction and modification:
When using LDAP external authentication, Configuration Server now supports
the use of international (non-ASCII) characters in the search base part of
the ldap-url
LDAP server parameter, and in user names and
passwords. Previously in these scenarios, LDAP external authentication was
unsuccessful, and the error Invalid credentials
was generated.
(ER# 220967697, 221506513)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release introduces the following new feature and functionality:
This release includes the following correction and modification:
Starting in release 7.5, Configuration Server exhibited poor performance on Windows platforms when processing large SOAP requests. Now, Configuration Server processes these requests at a much higher rate, significantly improving performance. (ER# 224587780)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
When using Lightweight Directory Access Protocol (LDAP) external authentication, Configuration Server now properly handles the scenario in which:
Previously in this scenario, Configuration Server terminated.
(ER# 233728088)
Configuration Server no longer terminates when it receives a request from a client that is not a Genesys application. Previously, but very rarely, Configuration Server would terminate when it received such a request. (ER# 223336741)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now attempts to reconnect to the LDAP external
authentication server if the connection between the two servers is lost.
Previously in this scenario, Configuration Server did not try to restore
the connection. As a result, all subsequent LDAP authentication requests
were failed with the error message Password is incorrect
.
This problem occurred only in versions 7.6.000.28 to 7.6.000.43 inclusively.
Note: This is the same issue as that resolved in version 7.6.000.45, only on different platforms.
(ER# 227754374)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now attempts to reconnect to the LDAP external
authentication server if the connection between the two servers is lost.
Previously in this scenario, Configuration Server did not try to restore
the connection. As a result, all subsequent LDAP authentication requests
were failed with the error message Password is incorrect
.
This problem occurred only in versions 7.6.000.28 to 7.6.000.43 inclusively.
(ER# 227754374)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release contains the following new feature and functionality:
To manage calculation of Virtual Agent Groups by primary and backup
Configuration Servers before and after switchovers, add the new configuration
option disable-vag-calculation
to the configuration files of
the primary and backup Configuration Servers, in the sections with the same
name as the corresponding Application
objects.
disable-vag-calculation
Default Value: false
Valid Values: true
, false
Effective: After restart
If this option is set to true
, Configuration Server does not
calculate Virtual Agent Groups for existing and newly-created objects.
Note: You must set this option to the same value for both the primary and backup Configuration Servers. Set it in their corresponding configuration files. Then stop and restart both Configuration Servers. You must do this each time you change this option, to keep the contents of the Virtual Agent Group correct.
(ER# 215628689)
This release does not include any corrections and modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Configuration Server can now establish secure connections to the LDAP Server. Previously, in versions 7.6.000.28 to 7.6.000.38 only, Configuration Server was unable to verify the security certificate for an LDAP Server, and therefore could not establish the secure connection to that LDAP Server, rendering any authentication attempts unsuccessful. (ER# 223622971)
When using LDAP external authentication, Configuration Server no longer terminates when trying to externally authenticate a user when both of the following conditions exist:
ldapclient.conf
does not exist.Previously, Configuration Server would terminate after its first attempt to externally authenticate a user under these conditions.
(ER# 222402421)
If Reconnect Timeout
on the Server Info
tab of
the properties of the master Configuration Server Application
object is set to 0
(zero), Configuration Server Proxy uses the
default value of 10
instead. This ensures that Configuration
Server Proxy will respond to client requests even when the connection between
the two Configuration Servers is lost.
Previously, if the Reconnect Timeout
for the master Configuration
Server was set to the invalid value of 0
(zero), and Configuration
Server Proxy lost connection to the master Configuration Server, Configuration
Server Proxy would not respond to client requests until the connection to the
master Configuration Server was reestablished.
(ER# 221781113)
Configuration Server Proxy now retains the Advanced Disconnect Detection Protocol (ADDP) settings in the following scenario:
Previously in this scenario, Configuration Server Proxy lost the ADDP settings while connecting to the backup Configuration Server. In addition, the original ADDP settings were sometimes not restored even after Connection Server Proxy switched back over to the primary Configuration Server.
(ER# 215526151)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
When using LDAP for external authentication, Configuration Server no longer
terminates if it cannot establish a connection to the LDAP server. Previously,
if the connection could not be established because of, for example, a
non-existent or unavailable LDAP server, incorrect or invalid secure
connection parameters, or an incorrect or malformed ldap-url
,
Configuration Server terminated. (ER# 221085815)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now correctly generates OBJECT_DELETED
and
OBJECT_ADDED
notifications. Previously, when Configuration Manager
was used to change object permissions, Configuration Server sometimes generated
these notifications incorrectly. (ER# 219446838)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer utilizes 100% of the CPU while processing update requests for properties of configuration objects in a large environment. Previously in this scenario, Configuration Server sometimes utilized 100% of the CPU for an extended period of time, thereby affecting services it was supposed to provide to client applications. (ER# 215134326)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
When performing a DN search using at least a switch and folder as the search criteria, Configuration Server now includes the folder in the query. Previously, Configuration Server ignored the folder criterion and used the other criteria, including switch, to build the query. (ER# 187077090)
If the option no-default-access
is set to 1
(one),
new users created after a restart are now properly assigned default privileges.
Previously after a restart, the option was reset to its default value (zero)
and new users were not assigned any privileges. (ER# 218147547)
Configuration Server Proxy no longer terminates when a client sends an update request and then disconnects before Configuration Server Proxy receives a response from Master Configuration Server. (ER# 218590226)
Configuration Server Proxy no longer places configuration objects created by Master Configuration Server in incorrect folders, when the objects were either:
Previously, Configuration Server Proxy placed such objects in both the folder in which they had been created or to which they had been moved, and in the default folder. In addition, the new objects inherited their permissions from the default folders, not the folders in which they had been created or to which they had been moved.
(ER# 218672445)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
In the following scenario:
After the connection is re-established, Configuration Server Proxy no longer switches to sending client authentication requests to the main Configuration Server; it continues to process authentication requests itself, using the external authentication server directly.
(ER# 217647821)
When configuring RADIUS external authentication on the Master Configuration
Server and on each Configuration Server Proxy as described in
ER# 214772499 in release 7.6.000.28, you can
now specify server names in the radiusclient.conf
and
servers
files as domain names or IP addresses. Previously, these
server names had to be specified as IP addresses, not domain names.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release contains the following new features or functionality:
Section: csproxy
Option: proxy-writable
Value: true
Change Takes Effect: Immediately
RADIUS External Authentication can now be configured on the Master Configuration Server and on each Configuration Server Proxy, so authentication requests need not be passed on to the Master Configuration Server. To configure this, refer to the Deployment Procedure for this release.
Warning: For both the Master Configuration Server and Configuration Server Proxy:
radiusclient.conf
files, the RADIUS servers listed
in the parameter authserver
must be stated as IP addresses,
not domain names.servers
files must contain all of the servers listed
in the radiusclient.conf
. All server names must be stated
as IP addresses, not domain names.(ER# 214772499)
Configuration Server and Configuration Server Proxy now calculate the total number of client connections, and report this information in logs as follows:
(ER# 215012481)
To improve system performance, you can now store the History Log file in memory instead of on the hard drive. To implement this, configure the following:
confserv
section of the Configuration Server
configuration file, set the configuration option
history-log-file-name=:memory:
.csproxy
of the Options
of
the Configuration Server Proxy Application object, add the configuration
option history-log-file-name=:memory:
.
(ER# 215717741)
This release includes the following correction and modification:
Configuration Server Proxy now properly processes changes of Agents' Skill Levels to 0 (zero). Previously, when notified by the Master Configuration Server that a Skill Level had been changed to 0 (zero), Configuration Server Proxy notified its own clients, but did not itself store the change. As a result, clients that connected to Configuration Server Proxy after the change received the previous (non-zero) value of that Skill Level. (ER# 213959006)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
There are no restrictions for this release. There are no new features in this release.
This release includes the following corrections and modifications:
Configuration Server no longer sends false notifications to clients about deleted objects in the following scenario:
Previously in this scenario, Configuration Server sent false notifications to clients about having deleted child folder objects while permissions were being changed in the parent folder's ACL.
Note: This release handles the described scenario for any Folder and child objects, and is an extension of the fix for ER# 203859241 in 7.6.000.13.
(ER# 212505511)
Configuration Server no longer randomly becomes inactive in cases where external authentication is used. Previously, Configuration Server occasionally became inactive for up to several minutes, then continued its normal operations. (ER# 206791776)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release contains the following new feature or functionality:
This release includes the following corrections and modifications:
When using multiple LDAP servers for external authentication, Configuration
Server now limits its repeated reconnection attempts to the number of times
specified by its retry-attempts
parameter before trying another
LDAP server. Previously, Configuration Server ignored the value of the
parameter and continued trying to reconnect to the LDAP server using the
default value. (ER# 209389101)
Configuration Server in Proxy mode no longer has its CPU usage increase steadily while processing a very large number of update notifications (such as updating the Skills of Agents in a Virtual Agent Group) from the master Configuration Server. Previously, unnecessary validation performed on the Configuration Server Proxy side caused an increase in CPU utilization, which then decreased when the processing of the update notifications was completed. (ER# 206651031)
Configuration Server now sends the correct notification when Campaign Groups are changed in a Campaign. Previously, the notification was incorrect and sometimes led to the loss of some information, such as the Voice Transfer Destination in Outbound Contact Manager. (ER# 203666223)
Configuration Server, and Configuration Server Proxy if configured, now correctly handle Campaign Groups in a Campaign. Previously, Campaign Groups appeared sometimes to have doubled in the Campaign. (ER# 197955641)
Configuration Server now accepts a value of 0
(zero) in the
Number of CPD ports
field when you create a new Campaign
Group in Configuration Manager. Previously, Configuration Server ignored a
zero value and used the default value 10
instead.
(ER# 171782595)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer sends false notifications to clients about deleted objects in the following scenario:
Previously in this scenario, Configuration Server sent false notifications to clients about having deleted objects (the Applications folder and all Applications, in this example) while permissions were being changed in the Environment folder's ACL.
(ER# 203859241)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer terminates if, in response to receiving an incorrect client request, it rolls back the transaction, but the client disconnects before the roll back is complete and before Configuration Server can notify the client appropriately. Previously in this scenario, Configuration Server would terminate if the client disconnected before its request was processed. (ER# 200262601)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now sends complete and correct configuration information to its client applications in the following scenario:
General
tab of the Campaign Group
object, the constituent group is replaced with another group.
Previously in this scenario, Configuration Server sent incomplete configuration data to its client applications. (ER# 191771004)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer terminates when using external authentication. Previously, in rare cases when there was a high volume of authentication requests, a synchronization error occurred in the authentication module and caused Configuration Server to terminate. (ER# 178321914)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server now correctly handles the situation where it continues to send data to a client application, even though the client is not responding. Previously in this scenario, Configuration Server sometimes utilized 100% of the CPU, but without affecting other services provided by the system. (ER# 179642564)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. There are no new features in this release.
This release includes the following corrections and modifications that were made between the initial release 7.6 and this 7.6 release:
New users created in release 7.6 are no longer assigned to an Access Group
by default, but they can be assigned automatically to default Access Groups,
the same as was done in release 7.5 and earlier, by setting the following
new configuration option to 1
:
no-default-access
Default Value: 0
Valid Values:
0
No default access
privileges
1
Default access
privileges
Takes Effect: Immediately
This option is contained in the security
section, and is set
on the Options
tab of the Configuration Server Application
object.
Existing users keep their existing permissions and Access Group assignments.
(ER# 168596941)
When a user creates a new Virtual Agent Group (VAG), Configuration Server now recognizes the agent selection script entered when creating the VAG. As a result, the VAG is populated with the correct members. Previously, Configuration Server did not recognize the script, and the VAG did not have any members. (ER# 157800566)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the
Contents, above.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
Configuration Server no longer utilizes 100% of the CPU immediately after a client disconnects. Previously, CPU utilization sometimes increased temporarily after a client disconnected. (ER# 162928747)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents section, above.
There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Configuration Server.
backlog=N
option that can be
specified in the Application Parameters
field for a particular Configuration
Server port.This release includes the following corrections and modifications that were made between release 7.5 or earlier releases and the initial 7.6 release:
When operating in a high-availability environment, the backup instance of Configuration Server now correctly switches to the primary role. Previously, during the switchover, Configuration Server might remain in PRIMARY READ-ONLY mode without completing the switchover procedure. (ER#s 137154961, 109970958)
Configuration Server initialization scripts now correctly create applications
of type GVP Voice Communication Server.
Previously, the incorrect
application type in the scripts prevented Voice Communication Server from
connecting to Configuration Server. (ER# 132781512)
When operating in a high-availability environment, after a switchover, Configuration Server now correctly processes client reconnection attempts. Previously, the new primary Configuration Server might reject client reconnection requests. (ER# 153703265)
Configuration Server now correctly handles the situation in which the connection between Configuration Server and DB Server is lost while Genesys components are waiting for a response from an active transaction processed on the database side. After the disconnection, Configuration Server now clears the transaction from memory and accordingly notifies the client application that originated the transaction. Previously, when the connection with DB Server was restored, Configuration Server continued to regard this transaction as incomplete and did not initiate any new transactions. (ER# 153396143)
Configuration Server now allows using an asterisk in option names when they are configured in Annex/Options tabs of any configuration object. Previously, Configuration Server did not accept asterisks in option names. (ER# 119784423)
Configuration Server now correctly responds to a request to restore sessions from its clients when a history log file is not accessible. Previously, Configuration Server could become unstable in this situation. (ER# 143804383)
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.
Configuration Server Proxy must be configured to work with the default port only of the master Configuration Server, as follows:
Connections
tab of the Configuration Server Proxy
Application
object, the connection must be only to the
default port.The History Log on the main Configuration Server may contain records of
previous additions and deletions of agents to and from Virtual Agent Groups,
so even if the disable-vag-calculation
option is set to
true
on the master Configuration Server, clients of that
Configuration Server, such as Configuration Server Proxies, may receive
notifications about adding and deleting agents when restoring their sessions
after a switchover.
Likewise, client applications may also contain agents in a Virtual Agent Group in their own caches.
Workaround: After changing the value of this option, Genesys strongly recommends that you:
Found In: 7.6.000.43 | Fixed In: |
If your environment contains a large number of agents in Virtual Agent
Groups, and the disable-vag-calculation
option is set to
false
(in which case Virtual Agent Groups are calculated), a
Configuration Server Proxy connected to the master Configuration Server may
disconnect because the Advanced Disconnect Detection Protocol (ADDP) timeout
may be reached before the Virtual Agent Group calculations are finished.
(ER# 226553491)
Found In: 7.6.000.43 | Fixed In: |
When using LDAP external authentication, Configuration Server terminates
if the LDAP configuration file ldapclient.conf
does not exist
and if no LDAP server is defined in the Configuration Server configuration
file. (ER# 222402421)
Found In: 7.6.000.38 | Fixed In: 7.6.000.42 |
When specifying the ldap-url
element in the LDAP configuration
file ldapclient.conf
, if a blank space is left between the
equals symbol (=
) and the beginning of the URL, Configuration
Server will use the local host instead of the specified host.
Workaround: Although the blank space exists by default, remove the space when specifying the LDAP URL.
(ER# 222396721)
Found In: 7.6.000.38 | Fixed In: |
The Framework 7.6 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 76fr_ref-exta_10-2007_v7.6.001.00 | Fixed In: Document version 80fr_ref-exta_09-2009_v8.0.101.00 |
When you change an Agent's Skill Level to 0
(zero), Configuration
Server Proxy notifies its own clients but does not store the change itself.
Therefore, when new clients connect to Configuration Server Proxy, they receive
the previous (non-zero) Skill Level for that Agent.
Workaround: Use Configuration Server release 7.6.000.13 in Proxy mode.
This version correctly handles changes to Agents' Skill Levels, even those
changed to 0
(zero).
(ER# 213959006)
Found In: 7.6.000.18 | Fixed In: 7.6.000.28 |
When a user creates a new Virtual Agent Group (VAG), Configuration Server may not recognize the agent selection script entered when creating the VAG. In this case, the VAG will not have any members.
Workaround: Update the value of the Script
field of the
new VAG, and save the changes. Configuration Server will recognize the script
and this and all future updates will be honored.
(ER# 157800566)
Found In: 7.6.000.04 | Fixed In: 7.6.000.06 |
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 ignores the retry-attempts
and retry-interval
values specified for LDAP external authentication. Configuration Server uses the default
values instead. (ER# 150236199)
Found In: 7.6.000.04 | Fixed In: 7.6.000.18 |
When using redundant Configuration Servers, if the Configuration DB Server
terminates while the backup Configuration Server is terminated, and is
restarted after the backup Configuration Server is restarted, the primary
Configuration Server remains in READ-ONLY
mode. Do not attempt
to:
READ-ONLY
mode because of its lost connection
with the database.Workaround: Wait until one of the Configuration Servers is fully
initialized, or its connection with the database is restored and it is no
longer in READ-ONLY
mode.
(ER# 194138081)
Found In: 7.5.000.11 | Fixed In: |
The AIX operating system uses a default memory allocation model. If the allocated memory is not sufficient for your application, refer to the Genesys 7 Hardware Sizing Guide for information about increasing the memory allocation.
Found In: 7.5.000.11 | 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 |
In a multi-tenant environment when Configuration Import Wizard (CIW) is used to perform configuration export, some users may export entire configuration, even if they do not have permissions to certain configuration objects. (ER# 117034027)
Found In: 7.5.000.11 | Fixed In: |
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.
There are no discontinued features or functions in this release of Configuration Server 7.6.
Information in this section is included for international customers.
There are no known limitations or restrictions for internationalization.
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 Framework 7.6 Deployment Guide first.
Framework 7.6 Deployment Guide provides instructions for installing and configuring Framework 7.6 components, and for starting and stopping the Framework 7.6 components either using the Management Layer or manually.
Framework 7.6 Configuration Manager Help describes how to use Configuration Manager in either an enterprise or multi-tenant environment.
Framework 7.6 Configuration Layer Error Messages Help describes error messages that the Configuration Layer generates in either an enterprise or multi-tenant environment.
Framework 7.6 Configuration Options Reference Manual describes configuration options for Framework 7.6 components.
Framework 7.6 Combined Log Events Help describes log events that Genesys server applications generate and that Solution Control Interface displays.
Framework 7.6 External Authentication Reference Manual describes how to use RADIUS and LDAP external authentication systems with Configuration Server.
Genesys 7.6 Security Deployment Guide describes Genesys security features and detailed instructions for deploying them. These features provide secure data transfer between Genesys components, protection against unauthorized access, and protection against data loss in case of component failure.
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.