Skip to main content

Managing audio files

Phone Password Manager is shipped with most of the audio files necessary for complete operation in English, however you must provide and configure the audio files for:

Adding custom authentication questions

In order to create custom questions with which to authenticate users of Phone Password Manager, you must configure the question definition on your Bravura Pass instance, and provide an audio file which Phone Password Manager will associate to that question.

Firstly, define your new authentication questions. See IVR with touch-tone authentication for more information on configuring question sets.

When you define the new question, the following conditions must be met:

  • The description field must be in the format: !!!DEFAULT_PREDEFQSET_<QID>_DESC

  • A KVG file has been configured in <Instance>\design\custom directory to translate the machine-readable question definition for each language you wish to support.

  • An audio file exists on your IVR server, in each <Instance>\audio\<Language> directory, titled QD-PREDEFINED_<QID>, that corresponds to the newly defined question.

To properly ID additional questions:

  1. Modify en-us-errmsg.kvg, located in the <instance>\design\src\common directory, to include a new tag for the additional question.

  2. Use the tag ID as the question description.

  3. Generate and install the new skin files.

The vocal should prompt the user to type the answer the question followed by pound; for example, "Enter the year you graduated high school, followed by the pound key."

See User Authentication for details.

Defining custom target systems

You can define prompts for each target system that users can reset their passwords or unlock their accounts for.

These files must be named reset_<target ID>.wav and unlock_<target ID>.wav respectively.

The vocal should prompt the user to perform the action for the specific target system; for example, "To unlock your account on Windows" or "To reset your password on Unix".

Phone Password Manager is shipped with a set of files for these common target systems:

  • Microsoft Active Directory – reset_AD.wav, unlock_AD.wav

  • Novell Directory Services (NDS) – reset_NDS.wav, unlock_NDS.wav

  • Microsoft Windows server – reset_NT.wav, unlock_NT.wav

If you want to use these shipped files, simply rename each file so that the <target ID> portion matches your actual target IDs.

Defining custom target system groups

When a user has accounts in more than one target system group, Phone Password Manager offers them the ability to select those groups when initiating a password reset.

In order to provide the user with a menu from which to select target groups, Phone Password Manager will individually spell out each letter of the custom group’s ID value.

In order to configure a custom audio file to present these target groups to users, create a new audio recording of the target group’s name, and save it to the appropriate <Instance>\Audio\<Language code> directory, depending on the language the audio file will be used for. The name of this file should exactly mirror the target group’s ID value: <Group ID>.wav .

You will need to restart your Phone Password Manager Windows services for the changes to take effect. Additional steps for Asterisk® backends may be required. For more information, see Asterisk® audio files .

Supporting custom call logic

You will need to configure the audio files for any modifications that you will make to the call logic scripts .

If you are not using the default call script, or if you have modified it, ensure that you have appropriate audio files for each PlayFile() or PlayFileEx() function. See the PSLang Manual (pslang.pdf) for more details on these functions.

All audio files used for play back must be stored in the <instance>\audio\<lang>-<locale> directory on the Phone Password Manager server. The value of<lang>-<locale> refers to the language and locale of the user. For example, use en-us for United States (us) English (en).

Additionally, all audio files must be recorded in the format specified in the idtel.cfg file . The default is a MuLaw-encoded, PCM Wave file, with 8 bit sample size, 8kHz sample rate, and 64kbps bit rate. Audio files should always be recorded in monaural format.

In this section: