Default Value: 0
Valid Values: Any integer from 0-1728000
Changes Take Effect: Immediately
Specifies timeout (in seconds) after which Chat Server disconnects a web (flex) chat participant if there are no agents in the chat session. After timeout expires, the timer fires (in other words, activates) only upon a subsequent request from a chat participant. Setting this option to "0" disables this functionality.
Chat Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- For a deployment with multiple GMS clusters, which is needed for multi-data center operations, Chat Server now selects a GMS node from another cluster if the cluster that was registered initially, is empty (in other words, all GMS nodes in this cluster are down). (CHAT-3684)
- New health metrics for Chat Server, including the application name and the identifier (DBID), have been introduced. These metrics, together with an existing process identifier value, can be used in monitoring for capturing Chat Server application restart occurrences. (CHAT-3683)
- New health metrics mem_sessions_launched and mem_sessions_disposed have been introduced. These metrics are intended to report how many chat sessions Chat Server keeps in its memory. (CHAT-3673)
- Chat Server now correctly sets idle alert timeout after a session restoration, taking in account the idle waiting time before the restoration. Previously, Chat Server was resetting idle alert timeout completely after a session restoration. (CHAT-3597)
This release contains the following resolved issues:
Chat Server now sends a different Party Left reason code when a customer is removed from the chat session by the flex-no-agents-timeout configuration option. Bot Gateway Server uses it to correctly stop a bot session when StopBotOnCustomerLeft is set to true during the bot startup. (CHAT-3694)
Chat Server now correctly applies Personally Identifiable Information (PII) configuration from UCS after a session is restored. Previously, for restored sessions, only the default hardcoded PII configuration was applied. (CHAT-3679)
No special procedure is required to upgrade to release 8.5.311.06.