Release Note

Contents

Introduction

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 Chat Server.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environments Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.

Supported Operating Systems

New in This Release

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

Corrections and Modifications

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# 230706747)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. No new features were introduced in this release of Chat Server.

Corrections and Modifications

This release includes the following corrections and modifications:

Chat Server now correctly takes timeshift information from the web client's initial request and submits this information to the UCS database when a new chat session is established. (ER# 211409427)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Chat Server.

• Support of Red Hat Enterprise Linux 4.0.
• Notification to the agent when a customer is typing during chat session.
• A new option web-max-user-messages has been introduced to specify the maximum number of messages a customer can send during a chat session. There is no limit to the number of messages an agent or supervisor can send.
• A new option web-request-max-size has been introduced to limit the maximum size of incoming packets (XML data) from web clients that can be accepted and parsed by Chat Server.

Corrections and Modifications

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

This release includes all fixes made in previous releases of this product (including hot fix releases) at the time of this initial 7.6 release.

Top of Page

Known Issues and Recommendations

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

Chat Server's status is not updated in Management Layer when running on Solaris in the following scenario:

1. Chat Server is started with no value specified in the endpoints section.
2. Local Control Agent (LCA) is started.
3. LCA receives Chat Server status as Service Unavailable.
4. A valid value is added to the endpoints section of Chat Server configuration.
5. Chat displays the message 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.

The command line options -version (-v), and -help (-h, -?) do not work on the AIX and Solaris platforms. (ER# 82376735)

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.

There are no discontinued features in this release.

Top of Page

Internationalization

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)

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 Deployment Guide first.

• Multimedia 7.6 Deployment Guide describes deployment procedures for all Multimedia components. It also contains a high-level description of the Multimedia system, its architecture, and a list of new features in the current release.

• Multimedia 7.6 User's Guide provides overall information about and recommendations on the use and operation of Genesys Multimedia.

• Multimedia 7.6 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.

• Multimedia 7.6 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple and Compound Samples, and describes procedures for customizing them.

• Multimedia 7.6 Web API Reference is a Javadoc listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component.

• Multimedia 7.6 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.

• Multimedia 7.6 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.

• Multimedia 7.6 Universal Contact Server Help is a guide to the Universal Contact Server user interface.

• Universal Routing 7.6 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for Multimedia.

• Universal Routing 7.6 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 Multimedia.

• Genesys Desktop 7.6 Help is a guide to using the Genesys Desktop.

• Genesys 7 Events and Models includes a set of basic interaction models, showing the components involved and the event messages sent among them. These models and events were formerly presented in the Open Media Interaction Models Reference Manual. The request messages that were also described in that book are now documented in the API References of the Platform SDK.

Top of Page