Jump to: navigation, search

callback.ringing-bell

Section: interaction-workspace
Default Value: Sounds\Ring.mp3|10|-1|primary
Valid Values: All special characters that are valid Windows file path, '|' separator and numeric values.
Changes Take Effect: At the next interaction.
Introduced: 8.5.115.17

Specifies the path of the sound file that is played when a Callback Preview Invitation is delivered to the agent. For example: "Sounds\Ring.mp3|10|-1|primary" The value has four components that are separated by the character '|':

1) The file name and folder relative to the application folder. It may happen that on some virtual desktop, MP3 or other sounds format cannot be rendered by Direct Show filters. Files format that can be played (.wav, …) with Direct Show must be used here.
2) The priority. The higher the integer the higher the priority.
3) The duration:
a) -1 means plays and repeats until an explicit message stops it (I.e.: the established event stops the ringing sound).
b) 0 means play the whole sound one time.
c) An integer > 0 means a time, in milliseconds, to play and repeat the sound.
4) The output devices:
a) primary means plays on the default output device.
b) secondary means plays on the output device specified by the application.secondary-audio-out-device option.
c) both means plays on both default output device and the output device specified by the application.secondary-audio-out-device option.

callback.gms-url

Section: interaction-workspace
Default Value:
Valid Values: A valid URL in the following format: http://<gms-host>:<gms-port>/
Changes Take Effect: At next callback request.
Introduced: 8.5.111.21

Specifies the URL of the Genesys Mobile Server (GMS) that will be used for Callback requests.

callback.callback-types-business-attribute

Section: interaction-workspace
Default Value:
Valid Values: A valid Business Attribute Name.
Changes Take Effect: At the next interaction.
Introduced: 8.5.111.21

A character string that specifies the name of the Business Attribute that contains the Attribute Values that are used as available "Callback Types" when scheduling a Callback.

callback.callback-information.header-foreground-color

Section: interaction-workspace
Default Value: #FFFFFFFF
Valid Values: The hexadecimal Alpha (from '00' for fully transparent color to 'FF' for regular plain color) followed by the RGB hexadecimal color code (3 values in the '00'-'FF' range).
Changes Take Effect: At the next interaction.
Introduced: 8.5.111.21

Specifies the color of the text of the Callback Information view header of Callback interactions. Example #FFFFFFFF for white color. This option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy.

callback.callback-information.frame-color

Section: interaction-workspace
Default Value:

  1. FF17849D

Valid Values: The hexadecimal Alpha (from '00' for fully transparent color to 'FF' for regular plain color) followed by the RGB hexadecimal color code (3 values in the '00'-'FF' range).
Changes Take Effect: At the next interaction.
Introduced: 8.5.111.21

Specifies the background color of the Callback Information view header of Callback interactions. Examples: #FFFFBA00 for a Gold color, #FF6F7074 for a Silver color, #FFB8400B for a Bronze color. This option can be overridden by a routing strategy, as described in Overriding Options by Using a Routing Strategy.

callback.callback-information.content

Section: interaction-workspace
Default Value: DesiredTime, Type, Number, Instructions
Valid Values: A comma separated list of items within the following list: DesiredTime, Type, Number, Instructions.
Changes Take Effect: At the next interaction.
Introduced: 8.5.111.21

Defines the Callback data that is displayed in the Callback Information Area. The Callback data entries are displayed in the order in which they appear in the list.

This page was last edited on July 21, 2020, at 16:15.
Comments or questions about this documentation? Contact us for support!