Jump to: navigation, search

flex-push-timeout

Section: settings
Default Value: 300
Valid Values: Any integer from 1-1728000
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09

Specifies timeout (in seconds) after which Chat Server sends ping notification for push-flex connected client. If no request from the client is submitted within the next "flex-push-timeout", Chat Server activates flex-disconnect-timeout. Inactivity is defined as the absence of protocol requests, not the absence of messages

identifyCreateContact

Section: chat
Default Value: 3
Valid Values: 1, 2, or 3
Changes Take Effect: Immediately


Specifies how a contact should be processed in the Contact Server.
Note: This option is applicable for proactive chat sessions only. For reactive chat sessions, you can specify the related parameter in the chat widget. See the createContact API docs for details.

8.5.309.17

Chat Server Release Notes


Chat Server is part of 9.x starting in 8.5.201.05.
Release Date Release Type Restrictions AIX Linux Solaris Windows
12/19/19 Update X X


Helpful Links

Releases Info


Product Documentation

eServices

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:



Resolved Issues

This release contains the following resolved issues:


Chat Server no longer leaks memory upon a session closure when the chat session is moved to another instance of Chat Server in High Availability mode. (CHAT-3611)


If the ContactId is provided in the userdata, this information is now used for contact identification if it is enabled by the identifyCreateContact option. (CHAT-3608)


When running in cluster mode (in other words when a web application is subscribed to either mobile or custom push notifications), Chat Server no longer permits establishing a CometD connection if the specified Genesys Mobile Services (GMS) node is not registered. (CHAT-3593)


Chat Server now correctly initializes flex-push-timeout when the web chat application establishes a new CometD connection without closing the existing CometD connection. Previously, in certain instances, the flex-push-timeout initialization could lead to the premature removal of the chat participant from the chat session during an active CometD connection. (CHAT-3589)


Chat Server now sets the most recent async status (GCTI_Chat_AsyncStatus) after the session is restored. Previously Chat Server would automatically set the status with 2 after a session restoration. (CHAT-3576)


Chat Server now reports the correct value in the KPI health counters for sessions_waiting_agent after a session restoration. (CHAT-3565)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.309.17.

This page was last edited on September 18, 2020, at 13:43.

Feedback

Comment on this article:

blog comments powered by Disqus