_do_not_call_items
Section: General
Default Value: No default value
Valid Values: <integer>,<integer>,<integer>
Changes Take Effect: Immediately
Introduced: 8.5.224.00
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>
- where:
- 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.
8.5.230.06
Genesys Mobile Services Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 01/14/22 | General | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Support for Cassandra 4.0. For deployment information, see Configuring an External Cassandra. (GMS-8402)
- Support for Chat V2 push notification without Cassandra. GMS can now send push notifications (custom-http) using the Chat V2 API when GMS is deployed in chat-only mode, that is, with no connection to Cassandra. (GMS-8542)
Resolved Issues
This release contains the following resolved issues:
GMS may pause sessions if the conditions of the _do_not_call_items service option are met and it does not coincide with the operation hours. Now, in this scenario, you can resume or abandon/fail sessions using the following events:
- resume_session—Continue the session and disable the _do_not_call_items option for the session.
- fail_session—Exit the session.
To send the resume_session event to the Callback session, use the following request:
- On GMS (Forward API):
$ curl -v http://<GMS server: GMS port>/genesys/1/ors/scxml/session/<ORS session id>/event/resume_sessionOn ORS:
$ curl -v http://<ORS server: ORS port>/scxml/session/<ORS session id>/event/resume_sessionTo send the fail_session event to the Callback session, use the following request:
- On GMS (Forward API):
$ curl -v http://<GMS server: GMS port>/genesys/1/ors/scxml/session/<ORS session id>/event/fail_session- On ORS:
$ curl -v http://<ORS server: ORS port>/scxml/session/<ORS session id>/event/fail_session(GMS-8490)
This release includes important security fixes related to the CVE-2021-45105 vulnerability. In particular, the Apache log4j 2 version has been upgraded to 2.17.1. (GMS-8566)
Upgrade Notes
Further instructions are available in the upgrade section of the Genesys Mobile Service Deployment Guide.