_urs_vq_priority_boost_on_connect
Section: URS Queueing
Default Value: 500
Valid Values: integer
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Priority to be added to the virtual interaction after connecting the customer call or chat session. This option only applies to scenarios where _userterminated_first_connect_party=CUSTOMER.
To use this option, import the GMS_URS_Strategy_85109_v2.58.zip strategy file available for download in the Callback Solution guide.
enable_notification_hybrid_mode
Section: chat.service-name
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.111.04
Discontinued: 8.5.112.05
Enables hybrid notification mode for Chat V2 CometD API. This option is dynamic and defined on a media level only.
- If false, the Chat V2 API requests will fail with an error code 240, statusCode=2 and chatEnded=true.
- If true, the GMS node will process correctly Chat V2 API requests against the session started using Chat V2 With CometD API.
stored-classes
Section: profiler
Default Value: Empty string
Valid Values: String
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Comma-separated list of classes that must store profiling information in the database. For example: "AdminController,TasksController"
The list of supported classes is the following:
- AdminController
- CallbackController
- ServiceController
- ServicesCompositeController
- ServicesController
- StatesController
- StorageController
- TasksController
logged-classes
Section: profiler
Default Value: Empty string
Valid Values: String
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Comma-separated list of classes that should print profiling information in the log. For example: "ServicesController,TasksController"
The list of supported classes is the following:
- AdminController
- CallbackController
- ServiceController
- ServicesCompositeController
- ServicesController
- StatesController
- StorageController
- TasksController
enable
Section: profiler
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Enables logging of profiled values and/or storage in Cassandra.
_max_queue_wait
Section: URS Queueing
Default Value: 0
Valid Values: integer
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Maximum time (in seconds) for the virtual interaction to wait in queue prior to contacting the customer if the virtual interaction has not been selected for routing. If set to 0 (default), this option is ignored. If you set this option, configure _urs_ewt_estimation_method = ursdial.
This option only applies to user-terminated delayed scenarios where _userterminated_first_connect_party=CUSTOMER. If max-queue-wait is configured, and if its value is exceeded, the system adds the GMS_Max_Queue_Wait user data to the outbound interaction.
_urs_vq_priority_boost_on_connect
Section: URS Queueing
Default Value: 500
Valid Values: integer
Changes Take Effect: Immediately
Introduced: 8.5.112.05
Priority to be added to the virtual interaction after connecting the customer call or chat session. This option only applies to scenarios where _userterminated_first_connect_party=CUSTOMER.
To use this option, import the GMS_URS_Strategy_85109_v2.58.zip strategy file available for download in the Callback Solution guide.
8.5.112.05
Genesys Mobile Services Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 11/16/17 | General | X | X |
Contents
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Support for tuning the queue priority increment in Callback scenarios where the customer dialed first. By setting a value for the new service-level option named _urs_vq_priority_boost_on_connect, the priority increment is applied to the voice interaction as soon as the customer is connected.
- The new option named _max_queue_wait enables you to configure a maximum time for the Callback virtual interaction to remain in queue waiting for an agent. When this time expires, the outgoing call will be dialed, regardless of agent availability.
- GMS can now send Mobile Push Notifications to Android devices using Firebase Cloud Messaging (FCM) if you configure the new related fcm options.
- GMS Server can now print service execution time in log files if you configure the following options in the new profiler section: enable, logged-classes, stored-classes.
- Chat V2 with CometD was enhanced with the following features:
- Support for Chat Session File Transfer operations, such as fileGetLimits, fileUpload, fileDownload, and fileDelete.
- The option enable_notification_hybrid_mode is now deprecated. Chat sessions started over Chat API V2 with CometD API no longer allow regular requests over Chat API V2.
- For usability purposes, the operation parameters alias, userId, and chatId are no longer required and can be omitted from your queries. For backward compatibility, GMS will keep sending events that include these parameters, populated with bogus values. (GMS-5546)
Resolved Issues
This release contains the following resolved issues:
The Genesys Mobile Services Custom Callback Plugin Sample was updated and is available for download. (GMS-5765)
Callbacks in PAUSED state are now displayed in the Callback UI. (GMS-5713)
Upgrade Notes
To use the new _urs_vq_priority_boost_on_connect option, you need to import the GMS_URS_Strategy_85109_v2.58.zip strategy available for download in the Callback Solution guide. Further instructions are available in the upgrade section of the Genesys Mobile Service Deployment Guide.
Supported Languages
The following table lists the languages supported by this release.
| ARA | CSY | CHS | CHT | DEU | ENU | ESN | FRA | FRC | ITA | JPN | KOR | PLK | PTB | RUS | TRK |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| X | X | X |