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.

unsubscribe-delay

Section: notification
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: Immediately
Introduced: 8.5.109.05

Time in seconds to wait for deleting notification subscriptions. In scenarios where the publish notification and the delete subscription requests are received concurrently, the subscription may be deleted before the notification gets published. If you set this option to a value greater than 0, you will force GMS to wait for the specified duration before deleting the subscription and this will allow the pending push notifications to be sent out.

_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.

_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.

_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.

unsubscribe-delay

Section: notification
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: Immediately
Introduced: 8.5.109.05

Time in seconds to wait for deleting notification subscriptions. In scenarios where the publish notification and the delete subscription requests are received concurrently, the subscription may be deleted before the notification gets published. If you set this option to a value greater than 0, you will force GMS to wait for the specified duration before deleting the subscription and this will allow the pending push notifications to be sent out.

_paused_services_list

Section: General
Default Value: GMS_Paused_Services
Valid Values: string
Changes Take Effect: Immediately
Introduced: 8.5.109.05

Name of the Transaction list entry that controls pausing of callbacks.

Tip
This is an advanced parameter. To modify the value of an advanced parameter, you must enable Advanced Parameters in the Service Management UI.

_paused_services_id

Section: General
Default Value:
Valid Values: string
Changes Take Effect: Immediately
Introduced: 8.5.109.05

ID of the service in the Paused Service Transaction List. If you set this option, its value is used to look up the service in the Paused Service Transaction List. If you do not set any value, the service name is used instead.

Tip
This is an advanced parameter. To modify the value of an advanced parameter, you must enable Advanced Parameters in the Service Management UI.

_throttle_request_parameters

Section: callback
Default Value: _customer_number
Valid Values: String
Changes Take Effect: Immediately


Added in: 8.5.109.05
Specifies a comma-separated list of request parameters to which the _throttle_customer_number_limit option applies. For example, _throttle_request_parameters=_customer_number, _target

_throttle_customer_number_limit

Section: callback
Default Value: 6
Valid Values: Any positive integer
Changes Take Effect: Immediately
Introduced: 8.5.109.05
Discontinued: 8.5.110.07

Specifies the maximum number of immediate callback requests that a given customer number can request per day. You can set the list of parameters to apply this throttling in the option _throttle_request_parameters.

Starting in 8.5.110.07, this option is discontinued. Use option _throttle_request_parameters_limit instead.

_throttle_ttl_2

Section: callback
Default Value: 3600
Valid Values: Any positive integer
Changes Take Effect: Immediately


Added in: 8.5.109.05
Specifies the duration in seconds used for the callbacks limit set in _throttle_callbacks_per_service_2. A second limitation can be introduced with the options _throttle_callbacks_per_service_1 and _throttle_ttl_1. Genesys recommends using these options to prevent high rates of callback requests in a given period of time. For instance, to set a limit of 500 callbacks in 5 minutes, but not more than 1000 callbacks in 1 hour, use the following configuration:

_throttle_callbacks_per_service_1=500
_throttle_ttl_1=300
_throttle_callbacks_per_service_2=1000
_throttle_ttl_2=3600

_throttle_callbacks_per_service_2

Section: callback
Default Value: 1000
Valid Values: Any positive integer
Changes Take Effect: Immediately
Introduced: 8.5.109.05

Specifies the maximum number of callbacks per service for the duration set in _throttle_ttl_2. A second limitation can be introduced with the options _throttle_callbacks_per_service_1 and _throttle_ttl_1. Genesys recommends using these options to prevent high rates of callback requests in a given period of time. For instance, to set a limit of 500 callbacks in 5 minutes, but not more than 1000 callbacks in 1 hour, use the following configuration:

_throttle_callbacks_per_service_1=500
_throttle_ttl_1=300
_throttle_callbacks_per_service_2=1000
_throttle_ttl_2=3600

_throttle_ttl_1

Section: callback
Default Value: 300
Valid Values: Any positive integer
Changes Take Effect: Immediately


Added in: 8.5.109.05
Specifies the duration in seconds used for the callbacks limit set in _throttle_callbacks_per_service_1. A second limitation can be introduced with the options _throttle_callbacks_per_service_2 and _throttle_ttl_2. Genesys recommends using these options to prevent high rates of callback requests in a given period of time. For instance, to set a limit of 500 callbacks in 5 minutes, but not more than 1000 callbacks in 1 hour, use the following configuration:

_throttle_callbacks_per_service_1=500
_throttle_ttl_1=300
_throttle_callbacks_per_service_2=1000
_throttle_ttl_2=3600

_throttle_callbacks_per_service_1

Section: callback
Default Value: 500
Valid Values: Any positive integer
Changes Take Effect: Immediately
Introduced: 8.5.109.05

Specifies the maximum number of callbacks per service for the duration set in _throttle_ttl_1. A second limitation can be introduced with the options _throttle_callbacks_per_service_2 and throttle_ttl_2. Genesys recommends using these options to prevent a high rate of callback requests in a given period of time. For instance, to set a limit of 500 callbacks in 5 minutes, but not more than 1000 callbacks in 1 hour, use the following configuration:

_throttle_callbacks_per_service_1=500
_throttle_ttl_1=300
_throttle_callbacks_per_service_2=1000
_throttle_ttl_2=3600

8.5.109.05

Genesys Mobile Services Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
05/05/17 General X X

Helpful Links

What's New

This release contains the following new features and enhancements:


Resolved Issues

This release contains the following resolved issues:


GMS now correctly updates final callback status for Callback calls. Previously, an issue sometimes occurred when, after successfully connecting a callback to a customer, an unwanted second call was placed to the same customer because the final status of the callback was not updated properly. (GMS-4797)


If an agent selects a retry_now or retry_later disposition, the Callback is queued again and the status is updated to QUEUED. Previously, the status remained PROCESSING. (GMS-4794)


When using an Avaya switch, some timing-related conditions no longer result in the session terminating prematurely. (GMS-4793)


In a preview scenario that involves an Avaya switch, if the agent rejects the preview request for Callback, the session will wait for the next selected agent and will process the Callback normally. Previously, when the agent selected the reject action, Callback was no longer processing the request and eventually timed out. (GMS-4792)


The count of logged-in agents now only includes voice agents in the GMS Admin UI's callback diagnostic data. (GMS-4722)


You can now add a delay to the callback subscription deletion to be able to receive the last notification changes by configuring the option unsubscribe-delay. Previously, when the publish notification and the delete subscription requests were received concurrently, the subscription may have been deleted before the notification gets published. (GMS-4608)


The "waiting for next available agent" prompt is now played to the customer when the agent does not accept the transfer of the callback call. (GMS-4577)


If you are using an external cassandra cluster and TLS connection between GMS nodes, the Monitor panel of the Admin UI now correctly shows the GMS nodes in alive status (green). (GMS-4412)


For security reasons, stack traces have been removed from GMS HTTP Response. Stack Trace messages are still available in GMS logs in debug mode. (GMS-4327)


The callback SCXML now parses correctly the option _plugin_on_dial_invoke_on_call_failed. (GMS-3359)



Upgrade Notes

If you are upgrading from 8.5.104 or earlier, install release 8.5.109.05 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 (version 2.33+) from the new GMS installation directory. Start the Service Management UI and upload the <GMS Installation Directory>/service_templates/callback.zip file.

IRD Strategy WaitForTarget should be updated to version 2.4+.

If you are upgrading to version 8.5.109.05, you may need to modify the new configuration option _enable_in_queue_checking. By default, this option blocks all the Callback requests issued from a customer number that is already two times 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 November 8, 2019, at 20:07.
Comments or questions about this documentation? Contact us for support!