Blueworx Voice Response software does not start to initialize

When the Blueworx Voice Response hardware powers up and initializes correctly but the software does not start, check the following:

Did you use the vae.setuser tool to create the Blueworx Voice Response account ID?
Blueworx Voice Response starts initializing automatically when you log on to the account defined as the Blueworx Voice Response AIX account. If you try to start the software any other way, it might not start (and even if it does, it will not run correctly).

Create the account (with all of the correct privileges and environment definitions) by using the tool called vae.setuser. Blueworx Voice Response for AIX: Installation describes how to use vae.setuser.

Do you have enough disk space free?
To enable it to start, Blueworx Voice Response requires enough free space in both of the file systems it uses (/home and /usr).. To find out whether you have enough free space, log on as root, type df and press Enter. Check the amount of free space displayed. If you do not have enough, clean up the file systems and recover space. Check the /home/dirTalk/current_dir/oamlog directory for any old error log and oamtrace files that you no longer need and can delete to recover space.

If you have spare capacity on your hard disk, you can increase the size of some of you file systems. See Using SMIT to increase the size of your file system:.

Is the AIX maxuproc parameter set high enough?
AIX includes a parameter that defines the ceiling on how many processes can start. If the value of the parameter is too low, Blueworx Voice Response cannot start the processes it needs. If the parameter is set to a high-enough value but a large number of processes are already running, Blueworx Voice Response cannot start.

Blueworx Voice Response for AIX: Installation introduces user processes and describes how to find out and change the number allowed (if necessary). If the value of the maxuproc parameter is already high enough, type ps and press Enter to determine whether an unusually large number of processes are already running.

Is the tasklist.data file missing or is there more than one instance of it?
Blueworx Voice Response starts the processes listed in the tasklist.data file. If the file is missing, the system cannot start.

The tasklist.data file is located in the directory identified by the value of the $SYS_DIR variable in the profile for the Blueworx Voice Response AIX account ID. Blueworx Voice Response for AIX: Installation contains instructions for checking on the tasklist.data file.

Are the Blueworx Voice Response parameter files corrupted?
The Blueworx Voice Response configuration is defined by the values of the Blueworx Voice Response system parameters. The configuration includes initialization information (such as the status to assign to trunks at system initialization). Without the parameter file, the system cannot start.

The Blueworx Voice Response system parameter file is called rd.data and is stored in the directory identified by the value of $SYSPARM_DIR as defined in the profile for the Blueworx Voice Response AIX account ID. Blueworx Voice Response for AIX: Installation introduces the system parameter file and describes how to restore it if it is corrupted.

Has the ISDN custom server started?
You cannot run two ISDN custom servers at the same time; you must stop the first ISDN custom server before you can start another.

If you try to run two ISDN custom servers, the following message appears in the Blueworx Voice Response log:

29203
ISDN signaling process initialization failure

The message description field contains “es_init() failed”.

Another reason why the ISDN custom server can fail to start is the abnormal termination of the ISDNDL4 process. In this situation, even if you stop the ISDN custom server, you might not be able to restart it without first shutting down and restarting Blueworx Voice Response.

Are you using an SSI cluster?
If you are, ensure that:
  • The clients and servers are configured correctly
  • The network is available
  • The database and any voice servers are up and running
  • The voice and custom server filesystems of the correct server are NFS-mounted on the clients

For information on the above, see the section on creating and managing a single system image in Blueworx Voice Response for AIX: Configuring the System.