connection-down-report-scs
Section: settings
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
With a value of 'false', Chat Server does not send a 'SERVICE
UNAVAILABLE' notification to Solution Control Server when Chat
Server detects disconnection from Interaction Server and/or UCS.
This can prevent Chat Server from switching over when configured as
primary/backup.
user-register-timeout
Section: settings
Default Value: 25
Valid Values: Any integer from 1-86400
Changes Take Effect: Immediately
Specifies the timeout, in seconds, during which the chat client
must send a registration/login request before it is
disconnected. This option is intended for debugging Web
Applications. It has almost no practical use in a regular
environment.
stop-abandoned-interaction
Section: settings
Default Value: never
Valid Values: always, never, noagents, noanswer
Changes Take Effect: Immediately
Modified: 8.5.301.06
Specifies how Chat Server handles chat interactions (in Interaction Server) when the chat session is finished. Possible values:
- always: interactions are always stopped when the chat session is finished (not recommended value).
- never: interactions are never stopped by Chat Server (recommended value).
- noagents: interactions are stopped only if there are currently no agents or supervisors in the session (use value wisely).
- noanswer: interactions are stopped only if no agents ever joined the session - in other words, the session was never answered (use value wisely).
Note: When the chat session is closing, it ignores the presence of bot participants when evaluating this option (in other words, bot participants are not considered "agents"). The legacy "true" and "false" values are also supported and converted to new values as following:
- "false" is interpreted as "never"
- "true" is interpreted as "noanswer"
By default, Chat Server does not stop any interaction after the chat session is finished. Instead, Chat Server updates the IsOnline interaction property to false and attaches reporting statistics. If your deployment includes Genesys Info Mart reporting, Genesys recommends that you set the value of this option to "noanswer", to enable accurate reporting of abandoned chats. In all other deployments, Genesys recommends that you set the value of this option to "never", and have the agent desktop and/or a workflow stop the interaction. Values other than "never" must be used cautiously, as stopping the interaction from Chat Server may lead to conflicts with updates from the agent desktop.
message-log-print-size
Section: settings
Default Value: 0
Valid Values: Any integer from 0-7000
Changes Take Effect: Immediately
Specifies the number of characters from the whole client message that the log prints, starting from the beginning of the message.
max-waiting-requests
Section: settings
Default Value: 500
Valid Values: Any integer from 0-1000000
Changes Take Effect: Immediately
Specifies the maximum number of sessions which reside in a waiting state after being created.
A waiting state is defined as waiting for an agent to join the chat session.
A value of 0 means that Chat Server will not create any new sessions.
flex-disconnect-timeout
Section: settings
Default Value: 45
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Modified: 8.5.301.06
Specifies timeout (in seconds) after which Chat Server disconnects an inactive web (flex) chat client. Inactivity is defined as the absence of protocol requests, not the absence of messages.
MessageText
Section: log-filter-data
Default Value: hide
Valid Values: copy, skip, hide
Changes Take Effect: Immediately
Specifies log filtering type for attribute MessageText.
verbose
Section: log
Default Value: all
Valid Values:
- all: All log events (that is, log events of the Standard, Trace, Interaction, and Debug levels) are generated.
- debug: The same as all.
- trace: Log events of the Trace level and higher (that is, log events of the Standard, Interaction, and Trace levels) are generated, but log events of the Debug level are not generated.
- interaction: Log events of the Interaction level and higher (that is, log events of the Standard and Interaction levels) are generated, but log events of the Trace and Debug levels are not generated.
- standard: Log events of the Standard level are generated, but log events of the Interaction, Trace, and Debug levels are not generated.
- none: No output is produced.
Changes Take Effect: Immediately
Determines whether a log output is created. If it is, specifies the minimum
level of log events generated. The log events levels, starting with the highest
priority level, are Standard, Interaction, Trace, and Debug.
8.5.000.30
Chat Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 04/17/15 | General | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- The default values of the following options have changed:
- In the [log] section: verbose
- In the [log-filter-data] section: MessageText
- In the [settings] section: flex-disconnect-timeout, max-waiting-requests, message-log-print-size, stop-abandoned-interaction, user-register-timeout.
- You can enhance performance by limiting the maximum number of chat sessions that each Chat Server can accept and/or restore.
- You can enable and configure masking of sensitive data (such as credit card numbers, Social Security numbers, and other patterns) in logs and transcripts.
- Support for UTF-8.
- Support for the following operating systems. See the Supported Operating Environment: eServices page for more detailed information and a list of all supported operating systems.
- Windows Server 2012
- Red Hat Enterprise Linux 6
Resolved Issues
This release contains the following resolved issues:
This release introduces the connection-down-report-scs configuration option. If Chat Server is configured in primary/backup mode, you may want to stop it from reporting service unavailable to SCS when it detects disconnection from Interaction Server and/or UCS; you can do so by setting connection-down-report-scs to false. Blocking these notifications avoids a scenario in which Chat Server in primary/backup mode closes a chat session because (1) Chat Server detects disconnection from Interaction Server and/or UCS, (2) it sends a service unavailable notification to Solution Control Server, (3) SCS switches Chat Server to backup, which closes the chat session. (This scenario does not apply if Chat Server is in N+1 mode: multiple Chat Servers with no backup configured). (ESR-7623)
Chat Server now properly reads the command-line argument -transport-ip-version 6,4 while connecting to Configuration Server. Previously, Chat Server's failure to read this argument prevented it from connecting to Configuration Server using IPv6. (ESR-7234)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.000.30.