Jump to: navigation, search


Section: General
Default Value: No default value
Valid Values: <integer>,<integer>,<integer>
Changes Take Effect: Immediately

For calls placed via a Routing Point (RP) this option defines time checks that the callback service must perform before calling the customer. The value for this option matches the following formatting:

<threshold>,<earliest call time>,<latest call time>
  • threshold defines the maximum time difference in seconds between the callback desired time and the current time.
  • earliest call time is the 24-hour earliest time that the callback service is allowed to launch a call if the current time matches the defined threshold value.
  • latest call time is the 24-hour latest time that the callback service is allowed to launch a call if the current time matches the defined threshold value.
Important: All of the above times are based on the local time of the Orchestration server(s).

For example, if _do_not_call_items=3600,9,21, the callback service does not proceed with calling the customer if the local time is not between 9 AM and 9 PM local time on the Orchestration Server. Additionally, before launching the call, it also checks that the current local time matches the customer call's desired time within 3600 seconds.

Genesys Mobile Services Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
03/04/21 Update X X

Helpful Links

What's New

This release contains the following new features and enhancements:

  • The _do_not_call_items option was introduced to perform several time checks based on the ORS current local time before launching the call to a customer. (GMS-8213)

Resolved Issues

This release contains the following resolved issues:

The GMS callback service now properly handles target expressions that include a threshold. (GMS-8234)

In a customer-first scenario where the plugin returns the route-to-rp option, the callback service now correctly redirects the customer call to the requested route point. (GMS-8231)

When configuring multiple ORS instances and using GMS in the ORS LoadBalancer strategy, if all ORS nodes are flagged as unhealthy, GMS now attempts to submit the interaction to the first node of the list. (GMS-8239)

The Office Hours service panel of the Admin UI no longer uses localized weekdays for storing the calendar configuration in the backend. The localization of weekdays is also disabled to avoid display and configuration issues for Office Hours. (GMS-8254)

Upgrade Notes

Further instructions are available in the upgrade section of the Genesys Mobile Service Deployment Guide.

This page was last edited on March 4, 2021, at 09:53.
Comments or questions about this documentation? Contact us for support!