| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 8.0.210.07 [04/01/11] – General | X | X | X | X | ||
| 8.0.200.03 [12/17/10] – General | X | X | X | X | ||
| 8.0.100.11 [10/27/10] – Hot Fix | X | |||||
| 8.0.100.08 [05/07/10] – General | X | X | X | X | ||
| 8.0.100.08 [04/26/10] – Hot Fix | X | |||||
| 8.0.100.07 [04/01/10] – General | X | X | X | X | ||
| 8.0.000.07 [08/13/09] – Hot Fix | X | |||||
| 8.0.000.06 [07/27/09] – General | X | X | X | X |
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 8.0 releases of Chat Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about any 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
There are no restrictions for this release. This section describes new features that were introduced in this release of Chat Server.
This release includes no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Chat Server.
This release includes no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release. This section describes new features that were introduced in this release of Chat Server.
If Chat Server receives incoming data that consists of an XML-based chat-basic or chat-flex protocol packet, and if that data is unparseable because of invalid structure or incorrect characters, Chat Server now outputs the content of the packet to its log in hexadecimal format. It does this for connections to both the default and the Web API port. (ER# 262374297)
This release includes no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Chat Server.
This release includes the following corrections and modifications.
This release corrects an issue that prevented Chat Server from sending EventPartyLeft
to chat participants about a customer (flex chat participant) who was removed from the chat session
due to an inactivity timeout (specified in the flex-disconnect-timeout option).
(ER# 250713713 )
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Chat Server.
This release includes the following corrections and modifications.
This release corrects an issue that prevented Chat Server from sending EventPartyLeft
to chat participants about a customer (flex chat participant) who was removed from the chat session
due to an inactivity timeout (specified in the flex-disconnect-timeout option).
(ER# 250713713 )
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Chat Server.
userdata of a chat interaction.smssession media type for the SMS Server
session mode.This release includes the following corrections and modifications.
Chat Server no longer truncates any strings of the startAt attribute on the chat transcript. Previously, on the Linux operating system,
Chat Server truncated some of the strings in this scenario. (ER# 232612203)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Chat Server.
This release includes the following corrections and modifications:
Chat Server now
correctly sends the full value of the startAt attribute in chat transcripts
to Universal Contact Server (UCS) when Chat Server is running on the Linux
platform. Previously, on Linux only, the startAt attribute could be
truncated to one character in chat close/update requests sent to UCS from Chat Server.
(ER# 233773171)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of Chat Server.
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
Chat Server now correctly processes wrong packets of data that are delivered to the ESP (External Service Protocol) port. Previously, Chat Server exited under such conditions. (ER# 218695684)
Chat Server now correctly processes invalid content of ESP requests and sends error notification to its clients for all failed requests. Previously, Chat Server mistakenly sent successful replies to Interaction Server for failed ESP requests. (ER# 220548497)
This section provides the latest information on known issues and recommendations associated with this product.
Configuring Chat Server's ESP port is changed in the 8.0.1 release.
Instead of using the esp-server-port option (which is retired in the 8.0.1 release),
you must go to the Chat Server Application object's Server Info tab and
create a port with ID = ESP, manually typing the exact string ESP.
There is a corresponding change in the way that Interaction Server connects to Chat Server:
On the Interaction Server application object's Connections tab, create a connection to Chat Server and select ESP in the Port ID drop-down list.
You must observe both of these changes in order to establish a properly working chat channel. See also the Interaction Server Release Note and the eServices Wizard Advisory.
Chat Server mistakenly listens on its ESP and Web-API ports when the ports were previously opened and are actively being used by other applications. (ER# 218946381)
| Found In: 7.6.100.02 | Fixed In: |
Chat Server's status is not updated in Management Layer when running on Solaris in the following scenario:
endpoints section.Service Unavailable.endpoints section of Chat Server configuration.LCA status was changed: server is enabled to process new chat requests. LCA does not receive a status update. Chat Server's status does not change to Started in Solution Control Interface. Status remains as Service Unavailable.If Chat Server's current status is not operable, chat requests from Web API Server could be rejected. This problem only occurs if LCA is started after Chat Server. (ER# 163081274)
Workaround: Restart Chat Server.
| Found In: 7.6.000.06 | Fixed In: |
The command-line options -version (-v) and -help
(-h, -?) do not work on AIX and Solaris platforms. (ER# 82376735)
| Found In: 7.5.000.09 | Fixed In: |
During startup, Chat Server logs no information about the primary (or backup) Configuration Server to which Chat Server is connected. In addition, no messages are logged, during runtime, about dynamic changes to Configuration Server configuration. (ER# 36753655)
| Found In: 7.2.000.05 | 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.
Windows 2000 is no longer supported.
| Discontinued As Of: 8.0.000.06 |
Information in this section is included for international customers.
The EUC Korean code page does not work correctly on the Solaris platform. This is a known issue of International Components for Unicode (ICU) library versions prior to 3.4. The suggested workaround is to set ko_KR.EUC-KR instead of ko_KR.EUC.
To set ko_KR.EUC-KR for Chat Server, issue the command: export LC_ALL=ko_KR.EUC-KR (This command is inserted in the run.sh file in the Chat Server installation folder).
Note: These are not valid local IDs or valid language codes, but the ICU library (which is a part of Chat Server distribution) will still be initialized correctly.
(ER# 86832931)
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 Deployment Guide first.
eServices 8.0 Deployment Guide describes deployment procedures for all eServices/Multimedia components. It also contains a high-level description of the eServices/Multimedia system, its architecture, and a list of new features in the current release.
eServices 8.0 Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product. It is available on the Genesys Documentation Wiki at http://developerzone.genesyslab.com/wiki/index.php?title=Category:EServices_Social_Media_Solution_Guide
eServices 8.0 User's Guide provides overall information about and recommendations on the use and operation of Genesys eServices/Multimedia.
eServices 8.0 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
eServices 8.0 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple Samples, and describes procedures for customizing them.
For a listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component, see:
eServices 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
eServices 8.0 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
eServices 8.0 Knowledge Manager Help is a guide to the Knowledge Manager user interface.
Universal Routing 8.0 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for eServices/Multimedia.
Universal Routing 8.0 Business Process User's Guide contains step-by-step instructions for using Interaction Routing Designer to design interaction workflows. It also describes the sample business processes supplied with eServices/Multimedia.
Genesys Desktop 7.6 Help is a guide to using the Genesys Desktop.
Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. For authoritative description of the event messages, see the next item.
The API References of the Platform SDK, which provide the authoritative
information on methods and functions for each SDK, including requests
and events. The class Message includes all event and request messages.
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.