The Juke Box configuration file

When the Juke_Box custom server starts, it reads a configuration file to build the music catalog. The supplied music_catalog configuration file is ready to use on T1 systems. The music_catalog_u_law file is a backup copy of this file. If you are using an E1 system, you must remove the music_catalog file, and copy the music_catalog_a_law file:

cp music_catalog_a_law music_catalog

Defining a tune in the configuration file

Before playing a tune, it must be defined to the Juke_Box custom server, either in the configuration file or dynamically, by the state table.

You modify the configuration file using a text editor. The Juke_Box custom server reads the configuration file only when it starts, so to make changes effective immediately you must stop and restart the Juke_Box custom server.

The name of the configuration file is passed to the Juke_Box custom server's main() function as a parameter. If you want to use a configuration file other than the default (music_catalog), you must change the properties on the Juke_Box custom server and restart it.

Note: If you are using the Juke_Box custom server on a cluster of Blueworx Voice Response systems that are configured as a single system image, files that the configuration file specifies must exist either:

On the database server node of the single system image
or:
On every system that is part of the single system image

If you don't specify a configuration file, or there is a problem with it, the Juke_Box custom server generates a yellow alarm. The Juke_Box custom server continues without a configuration file, that is, it starts with an empty music catalog. You can still use background music in your application by configuring tunes dynamically from your state table.

Configuration file format

Each tune in the configuration file has three fields; each field is surrounded by double quotation marks, as shown in Figure 1. Lines starting with # are treated as comments; blank lines are ignored. For an explanation of the music title, music player name, and parameters, see the parameter descriptions for the juke_box_configure_music custom server command in the Blueworx Voice Response for AIX: Application Development using State Tables information.

Figure 1. Example of a configuration file for the Juke_Box custom server

# Configuration File for use by Juke_Box custom server.
 # music title                     music player name     parameters
 # ===========                     =================     ==========
 “Blueworx Voice Response Theme 1”  “juke_box_dir/pl_seg”   “-l 1 -d music_u_law -s 1 -a”
“Blueworx Voice Response Theme 2”  “juke_box_dir/pl_seg”   “-l 1 -d music_u_law -s 2 -a”
 “Blueworx Voice Response Theme 3”  “juke_box_dir/pl_elem”  “-f juke_box_dir/dt_theme_1_u_law.elem -a”
 “Blueworx Voice Response Theme 4”  “juke_box_dir/pl_elem”  “-f juke_box_dir/dt_theme_2_u_law.elem -a”
 # End of the configuration file.