Jump to: navigation, search

_enable_in_queue_checking

Section: callback
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately


Added in: 8.5.109.05
If true, prevents the callback creation if the same customer number has already two callbacks in the queue; if false, does not check whether the customer is already in queue when creating the callback. This option applies to both immediate and scheduled callbacks.

8.5.110.08

Genesys Mobile Services Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
08/23/17 Hot Fix X X

Helpful Links

What's New

This release includes only resolved issues.



Resolved Issues

This release contains the following resolved issue:


A GMS node now properly closes a connection with the Chat Server after creating a chat session over Chat API V2 with CometD. Previously, the GMS node kept the connection open, causing the number of established connections to grow between the GMS node and the Chat Server by one for each new chat session. (GMS-5336)




Upgrade Notes

If you are upgrading from 8.5.104 or earlier, install release 8.5.110.08 as usual, then update the DFM files to ensure correct callback processing.

If GMS has external Cassandra configured, when you upgrade GMS, you need to import the Callback Template from the new GMS installation directory. Start the Service Management UI and upload the <GMS Installation Directory>/service_templates/callback.zip file.

Release 8.5.110.08 requires the download and update of the following strategies:

  • WaitForTarget version 2.5+
  • SetRouteDelay version 2.1+

If you are upgrading from a version older than 8.5.109.05, you may need to modify the configuration option _enable_in_queue_checking. By default, this option blocks all the Callback requests issued from a customer number that has already appeared twice in queue. If you wish to keep the previous behavior (with no automatic blocking), set this option to false.

This page was last edited on August 23, 2017, at 23:42.
Comments or questions about this documentation? Contact us for support!