The ADSI custom server

The ADSI custom server is called by the supplied ADSI state tables. It generates ADSI data streams from server download control (SDC) and feature download management (FDM) files.

The ADSI custom server is responsible for:

• Receiving a request from the ADSI, ADSI_I or ADSI_FDM_* state tables to communicate with the ADSI device
• Locating the requested ADSI SDC function or FDM script, and converting the binary information into 1200 baud modem encoded data
• Transmitting the data to the ADSI telephone
• Handling any requests to retransmit if the ADSI device detects errors on received data

Controlling the ADSI custom server

You can control the ADSI custom server in the same way as you control any other Blueworx Voice Response custom server:

• To start and stop the custom server, use the Custom Server Manager window.
• To change the properties of the custom server, use the Properties option of the Custom Server Development window.

ADSI custom server properties

You can set the following options for the ADSI custom server in the Properties window as follows:

1. From the Welcome Window, click Applications —> Custom Servers.
2. Select and open the ADSI custom server by double-clicking the ADSI entry in the list.
3. Click File —> Properties, then specify the following properties in the main() args window. If you want to specify more than one property, you must put each on a separate line in the window.

   -a

   For E1 trunk connection (A-law).

   -v

   Verbose mode (prints trace information).

   -V

   Very verbose mode (prints trace information and hex data).

   -r

   Dynamically reloads SDC and FDM scripts each time they are required; that is, the custom server does not cache them. This property is useful when you are developing scripts, but it could reduce performance on a busy system. It is better that you do not to use this property on a production system because it reduces the performance of the system.

   -c

   Dynamically recompiles each SDC and FDM script as it is required. It is better that you do not to use this property on a production system because it reduces the performance of the system.

   Note: If you change a script, and the -r and -c options are not in use, you must stop and restart the ADSI custom server to reset the internal caching algorithm.
4. If you change the properties, click OK in the Properties window. Then click File —> Save in the Custom Server (ADSI) window.

For general information on custom servers, see the Blueworx Voice Response for AIX: Managing and Monitoring the System information. For more information on custom server properties, see the Blueworx Voice Response for AIX: Custom Servers information.