Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
8.1.001.41 [04/04/14] – Hot Fix | X | X | X | X | ||
8.1.001.40 [08/15/13] – General | X | X | X | X | ||
8.1.000.26 [03/07/12] – General | X | X | X | X | ||
8.1.000.20 [10/27/11] – 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.genesys.com for more details.
This release note applies to all 8.1 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 third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
If Chat Server receives the basic chat protocol request Release Party
from a connection
that did not register (by sending the request Register
),
it replies with the error message User was logged out.
Previously, Chat Server exited in this situation.
(ESR-7956)
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.
server-reply-timeout
option now works for Interaction Server as well as Universal Contact Server.
Specifies how long, in seconds, Chat Server waits for a reply from Interaction Server. If no reply is received within the specified timeout, Chat Server considers the corresponding request to have failed.
This option is identical with server-reply-timeout.
If server-reply-timeout-ixn
is present, server-reply-timeout
does not apply to Interaction Server.
stop-abandoned-interaction
option specifies the action Chat Server is to perform with the interaction after the session has closed. It has the following new possible values:
never
The interaction is not stopped.
noanswer
(default)The interaction is stopped if no agent ever joined the session
(that is, if the chat session was never answered).
noagents
The interaction is stopped if there is currently no agent or supervisor
in the session (the chat session may have been answered but the agent then left the session).
always
The interaction always stops when the chat session closes.
The previous possible values are still supported, and are interpreted as follows:
true
is interpreted as noanswer.
false
is interpreted as never.
If the interaction is not stopped, the interaction property IsOnline
is set to false.
Edit.
Connection Protocol
dropdown:
chat-basic
Only basic protocol requests are accepted on connections opened to this port.
chat-flex
Only flex protocol requests are accepted on connections opened to this port.
chat-all
Both basic and flex protocol requests are accepted on connections opened to this port.
esp
Only ESP protocol requests are accepted on connections opened to this port.
chat-all
unless it is one of the legacy fixed IDs.
default:
webapi
port specified,
either in Port Info or using the webapi-port
option,
set to chat-basic
protocol type.
chat-all.
ESP
Set to esp
protocol type.
webapi
Set to chat-flex
protocol type.
Notes:
ESP
protocol port, it checks the esp-server-port
option
in the settings
section.
default
ID (the protocol type of which could be interpreted as chat-all or chat-basic according to above rule),
it is used in ChatServerPort
in userdata. Otherwise the first detected port
of type chat-all
or chat-basic
is used.
There are no corrections or modifications for this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. No new features were introduced in this release of Chat Server.
This release includes the following corrections and modifications:
In High Availability mode, the current time no longer shifts one hour ahead after session restoration. Previously, it sometimes shifted. (ER# 286255593)
After an agent leaves a chat session that a supervisor barged into after monitoring, the session continues. Previously, in this scenario the session was closed. (ER# 288339245)
An agent can now remove from a chat session a second agent who was participating in coaching (INT) mode.
Previously, in this scenario the first agent received a message No privileges to perform this operation.
(ER# 28693055)
Chat Server now correctly converts attached data to UTF-8 (available only on UNIX) for all locales. Previously, for some Asian languages, converted attached data sometimes included nonsense characters at the end of the converted string. (ER# 276350235)
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.1 release of Chat Server.
There are no corrections or modifications for this release.
This section provides the latest information on known issues and recommendations associated with this product.
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: |
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.
Support is discontinued for all 32-bit Unix platforms.
Discontinued As Of: 8.1.001.40 |
Solaris x32 is no longer supported.
Discontinued As Of: 8.1.000.20 |
AIX 5.1, AIX 5.2, and Solaris 8 are no longer supported.
Discontinued As Of: 8.1.000.20 |
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 Customer Care website. The following documentation also contains information about this software. Please consult the eServices 8.1 Deployment Guide first.
eServices 8.1 Deployment Guide describes deployment procedures for all eServices components. It also contains a high-level description of the eServices system, its architecture, and a list of new features in the current release.
eServices 8.1 User's Guide provides overall information about and recommendations on the use and operation of Genesys eServices.
eServices 8.1 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
eServices 8.1 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.1 Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product.
eServices (Multimedia) 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
8.1 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
eServices 8.1 Knowledge Manager Help is a guide to the Knowledge Manager user interface.
Universal Routing 8.1 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.
Universal Routing 8.1 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.
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.
Genesys 8.0 Security Deployment Guide describes the deployment and configuration of some of the security features provided in Genesys software.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.