Jump to: navigation, search


Section: settings
Default Value: 2000
Valid Values: Any integer from 0-1000000
Changes Take Effect: Immediately

Specifies the maximum possible delay, in milliseconds, required for Chat Server to process an incoming request. The delay is calculated as an average value over an interval defined by the option "limit-average-interval".

Chat Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
07/29/16 General X X X X

Helpful Links

Releases Info

Product Documentation


Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • Documentation regarding data retention (TTL) and sample initialization scripts for automating cleanup procedures in case of failure.
  • Ability for agent to alter participant nicknames while a chat session is in progress.
  • Improvement to Chat Server load control management (configuration option limit-for-reply-delay). This improvement is essential for deployments running several Chat Server instances.
  • New key-value pairs attached at the end of a session describing the reason that the session ended:
    • csg_SessionEndedBy indicates the type of user that initiated the end of the session: CLIENT (i.e. end customer), AGENT, SUPERVISOR, SYSTEM.
    • csg_SessionEndedReason describes how the session was closed: DISCONNECT, QUIT (participant logged out), FORCE (participant requested that the session be closed), INACTIVE, DB_ERROR
  • Support of read receipt notifications. Notification can be used by widgets and desktops to display read receipts to agents and customers.*
  • Ability to send notifications to participants when an agent or supervisor joins a chat session for coaching or silent monitoring, based on configuration. The notification message can then be used by Chat Widget or Desktop to notify the respective attendees.*

*Note: Check the appropriate Genesys Workspace and Widget/GMS releases for compatibility. Custom agent desktops can utilize these features via the corresponding PSDK version.

Resolved Issues

This release contains no resolved issues.

Upgrade Notes

No special procedure is required to upgrade to release

This page was last modified on September 1, 2016, at 14:55.


Comment on this article:

blog comments powered by Disqus