Jump to: navigation, search

sounds.preloadfiles

Section: interaction-workspace
Default Value: Sounds\Ring.mp3
Valid Values: A comma-separated list of valid Windows directory paths and file names. '|' character after the file name must be followed by the output device definition.
Changes Take Effect: When the application is started or restarted..
Dependencies: application.secondary-audio-out-device
Related Options: voice.ringing-bell, chat.new-message-bell

Specifies the name and location in the application folder of audio files that are to be pre-loaded when an agent logs in. For Example: "Sounds\Ring.mp3|primary,Sounds\bell|secondary.mp3,Sounds\chord.mp3|both,Sounds\warning.mp3". The audio files are defined by the options that control sounds, such as voice.ringing-bell and chat.new-message-bell. Files that are not specified by this option are loaded whenever they are needed. The file value has two components that are separated by the character '|':

  1. The file name and folder relative to the application folder. In some virtual desktop environments, MP3 and other sound file formats cannot be rendered by Direct Show filters. In this scenario, use Direct Show compatible formats such as .wav.
  2. The priority. The higher the integer the higher the priority.
  3. The duration:
    1. -1 means play and repeat until an explicit message stops it. For example, the established event stops the ringing sound.
    2. 0 means play the whole sound one time.
    3. An integer > 0 means a time, in milliseconds, to play and repeat the sound.
  4. Specify whether tones are played on the default audio device, a secondary audio device, or both. If no value is specified for this flag, the value |primary is used by default.

Sounds options

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.

Related Resources

The following topic discusses the implementation of these options:

This page was last edited on September 20, 2021, at 07:33.
Comments or questions about this documentation? Contact us for support!