Use the dtjplex script, command, or batch file to make voice segments available to voice applications. To use dtjplex, the HostManager must be running and, for many of the actions, the voice response node and base Blueworx Voice Response system must also be running. The actions take effect immediately.
This is a summary of the dtjplex actions:
You can also list available voice segments
Copy or rename them
And delete them
Full reference information is given in dtjplex script.
To use many of the dtjplex actions (addVS, copyVS, deleteVS, exportVoiceHost, importVoiceHost, importVoiceAll), you also need a dtjplex control file to specify the names and other relevant attributes of the voice segments you want to operate on. Specify the control file using the -controlfile parameter. For example, dtjplex -action addVS -controlfile pizzavsegs.txt.
You can specify the name of the control file using the -controlfile parameter in the dtjplex command. The default name depends on the action:
The control file contains one or more entries each of which is ended by a line containing only a semicolon (;). The action is performed for each entry.
Each entry contains one or more lines. If the first nonblank character on a line is a pound or hash symbol (#), the remainder of the line is ignored (treated as a comment). Otherwise, the line must contain one, and only one, “parameter=value” pair. The parameters are not case sensitive but the values are. The parameters and their values are listed in detail in dtjplex script and the sections that follow it.
For each entry, parameter values are gathered from top to bottom and then the action is performed: if you do not specify a mandatory parameter in an entry, the value last specified for it in a previous entry is used.
To unset a parameter value, set it to null (“parameter=”): in this case, the default value is used.
You can use the character_encoding keyword in the control file to specify the encoding of the content of control file: see individual action information in dtjplex script.
The dtjplex command displays messages which you should check need to be sure you have operated on the correct voice segments. If you are using national characters (8-bit ASCII or DBCS encoding), the messages may display the “wrong” characters. If you are worried that, for example, you have not added the correct voice segments to the Java voice segment space, use the dtjplex listVS command to list the voice segments.
You can use the -encoding parameter to specify the character encoding used by the listvs action to list the voice segments.
If there is a syntax error in the control file an error message is displayed and processing stops. Entries in the control file are processed up to the syntax error, but no further entries are processed. If the action fails on the target host for an entry, an error message is displayed, and processing continues to the next entry in the control file.
Figure 1 shows a dtjplex control file that could be used to add three voice segments from the Pizzas voice segment directory to the Pizzas category in the Java voice segment space. After this, three voice segments are added from the Sandwiches voice segment directory to the Sandwiches category. The purpose of this example is to show how parameter values are used repeatedly until a new value is specified.
# Example of control file for adding base voice segments # from two voice directories and two languages # to the Java voice segment space # # Set overall parameter values for Italian Pizza voice segments: base_voice_directory=Pizzas segment_category=Pizzasbase_language_identifier=10 base_language_compression=uncompressed segment_locale=it_IT # Set parameter values for individual segments: base_segment_identifier=1 segment_name=1;base_segment_identifier=2 segment_name=2;base_segment_identifier=3 segment_name=3; # Set overall parameter values for American Sandwich voice segments: base_voice_directory=Sandwiches segment_category=Sandwiches base_language_identifier=1 segment_locale=en_US# Set parameter values for individual segments: base_segment_identifier=1segment_name=1; base_segment_identifier=2segment_name=2;