Writing ADSI scripts

Blueworx Voice Response communicates with ADSI telephones by sending and receiving streams of data through the normal voice channel. The data that is sent to the telephone can be in one of two formats: server display control (SDC) and feature download management (FDM), as described in Introduction.

The ADSI data streams are generated by Blueworx Voice Response from files called scripts. You create the script source files by using any ASCII text editor. They contain ADSI instructions, or statements, that can be interpreted by ADSI telephones. You must compile the source files into a format that is suitable for transmission to the telephones.

The source files can have any valid AIX file name and extension. But if you want them to be recognized as ADSI script source files when you compile them, give SDC script source files an extension of .sdc and FDM files an extension of .fdm.

Note: In versions of IBM WebSphere Voice Response before Version 2.2, SDC and FDM files were stored in $CUR_DIR/adsi, which is not backed up by the usual Blueworx Voice Response save and restore tools.

It is better that you store SDC and FDM files in $CUR_DIR/ca/ADSI_dir, which is backed up by the standard save and restore tools.

The statements that you can use are described in ADSI script statements. The statements that are supported by Blueworx Voice Response are similar to those that are defined in the Bellcore Specifications SR-INS-002461 and TR-NWT-001273. Many of the statements are common both to SDC and FDM scripts, but there are a number of differences between the two script types and they are handled separately in the following sections.

If you want to add comments to your script file to explain the statements you use, start each comment line with the two characters //.