Jump to: navigation, search


Section: settings
Default Value: 10
Valid Values: Any integer from 1 to 600
Changes Take Effect: Immediately

Specifies, in seconds, the maximum allowable delay for the response to RequestPull sent to the node in the Interaction Server Cluster on behalf of routing clients, such as ORS. If this option is specified, the proxy modifies any RequestPull (those with a key 'pull-for-strategy' and value 1 in the extension) that it receives from routing clients. This helps to avoid situations when one server delays a response to RequestPull for a long time because it happens not to have interactions available, while other servers in the cluster do have interactions available.


Section: settings
Default Value: false
Valid Values: true, false, yes, no
Changes Take Effect: Immediately

Specifies whether Interaction Server Proxy will add a new pair with the key 'InternalRequestReason' in the request's extension. This new pair is a mark, strictly for debugging, to distinguish messages sent by the client from those generated by the proxy.


Section: settings
Default Value: 10000
Valid Values: Any integer from 100 to 10,000,000
Changes Take Effect: Immediately

Specifies the size of the internal interaction cache. The cache holds information about processed and queued interactions, so the Proxy knows to which server it should forward interaction-related requests. When maximum capacity is reached, the oldest entries are replaced with new ones.

Interaction Server Proxy Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
05/20/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:

  • Interaction Server Proxy now supports connections from client types like Media Server (such as Chat Server) and Routing Engine (such as Orchestration Server). It also supports connections using the ESP protocol and can process those requests. Previously only connections from Agent Application (Desktop) and Reporting Engine client types (such as Stat Server) were supported.
  • This release supports multiple Interaction Servers in a single tenant, managing the same agents.
  • Red Hat Enterprise Linux (RHEL) 7 64-bit native is supported.
  • The following options have been added to the settings section: interaction-cache-size, mark-internal-requests, and pull-hold-timeout.

Resolved Issues

This release contains no resolved issues.

Upgrade Notes

In an Interaction Server Cluster environment the Proxy attempts to hide from the Clients some activities on the cluster nodes, particularly disconnection and/or restart of the node. In several scenarios Clients like Agent Desktop should be notified about such changes, and EventHint is used for such cases. For example, if the Desktop is handling an interaction and the Interaction Server node is unexpectedly disconnected, the Desktop client will be notified with this event that interactions processed by that node are not available. You must configure the Desktop to handle this situation correctly. If the node reconnects, the Proxy attempts to restore the status of the interaction and notify the Desktop again. (ESR-11212)

In this release, EventHint is sent only for interactions acquired by the Desktop using RequestPull or RequestSubmit. Interactions handled by the Desktop after EventInvite and subsequent RequestAccept are not monitored by the Proxy. (ESR-12266)
This page was last edited on November 4, 2016, at 15:14.
Comments or questions about this documentation? Contact us for support!