Network problems

Blueworx Voice Response does not initiate outbound calls

When Blueworx Voice Response does not initiate outbound calls, check the following:

Are you using a signaling process you developed yourself?
Have you configured Blueworx Voice Response to use your signaling process?

Check that your signaling process is still running. Error 32011 in the error log indicates that a signaling process has terminated.

Check that your signaling process is receiving the SL_TRUNK_RECONFIG_REQ primitive, and is successfully sending SL_TRUNK_RECONFIG_CNF.

Check that your signaling process is receiving the SL_CALL_SETUP_REQ primitive.

Check that your signaling process is returning the SL_CALL_SETUP_CNF primitive to Blueworx Voice Response, and that the sl_send_confirm() subroutine is returning successfully.

Use signaling interface tracing the see the primitive sent by Blueworx Voice Response to your signaling process. For information on tracing signaling interfaces, see Tracing the signaling interface.

Blueworx Voice Response does not answer the phone

When Blueworx Voice Response does not answer the telephone, check the following:

Are you using a signaling process that you developed yourself?
Have you configured Blueworx Voice Response to use your signaling process?

Check that your signaling process is still running. Error 32011 in the error log indicates that a signaling process has terminated.

Check that your signaling process is receiving the call from the network.

Check that your signaling process is sending the SL_CALL_SETUP_IND primitive to Blueworx Voice Response, and that the sl_send_indication() subroutine is returning successfully.

Use signaling interface tracing the see the primitive sent to your signaling process by Blueworx Voice Response. For information on tracing signaling interfaces, see Tracing the signaling interface.

Blueworx Voice Response is not receiving information from the exchange data link

Certain switches transmit call information out of band using a serial line called the exchange data link. When Blueworx Voice Response is directly connected to such a switch and is not receiving the call information, check the following:

Are you using a signaling process that you developed yourself?
Have you configured Blueworx Voice Response to use your signaling process?

Check that your signaling process is still running.

Check that your signaling process is receiving the call from the network.

Check that your signaling process is sending the SL_CALL_SETUP_IND primitive to Blueworx Voice Response, and that the sl_send_indication() subroutine is returning successfully. Check that the sl_call_data_st structure in the SL_CALL_SETUP_IND primitive has been filled in correctly.

Use signaling interface tracing the see the primitive sent to your signaling process by Blueworx Voice Response. For information on tracing signaling interfaces, see Tracing the signaling interface.

Telephone channel is hung

When a telephone channel remains in an off-hook state after the caller has hung up, check the following:

Are you using a signaling process that you developed yourself?
Have you configured Blueworx Voice Response to use your signaling process?

Check that your signaling process is still running. Error 32011 in the error log indicates that a signaling process has terminated.

The usual cause of this problem is that your signaling process has not cleared a call correctly. Error 32012 in the error log indicates that your signaling process has ignored an SL_CALL_ABORT_REQ primitive. This is an error in your signaling process. See the description of error 32012 in the Problem Determination information and the SL_CALL_ABORT_REQ primitive.

Use signaling interface tracing the see the primitive sent to your signaling process by Blueworx Voice Response. For information on tracing signaling interfaces, see Tracing the signaling interface.

Cannot enable trunk

Blueworx Voice Response cannot use a trunk unless a digital trunk adapter is installed in the pSeries computer to process the signals transmitted by the switch. A trunk status of Available indicates that a digital trunk adapter is physically present (is available) to handle the signals from that trunk.

Blueworx Voice Response is always delivered with at least one digital trunk adapter (for the 12 signaling channels delivered with the system). The value of the trunk status parameter in the default system configuration is therefore Available for the first trunk, since the system includes a digital trunk adapter for that trunk. However, the value of the parameter for all other trunks is Defined, since the system does not know whether there are any additional digital trunk adapters installed. When you start Blueworx Voice Response the very first time, the status of the first trunk is Available and the status of all other trunks is Defined.

The way to inform Blueworx Voice Response that additional digital trunk adapters are installed is to enable the trunks to which they are connected. Enabling a trunk informs Blueworx Voice Response that the digital trunk adapter has been installed and is connected to the pack. (If you are looking at the System Monitor, you can see that after you enable a trunk, the trunk status displayed at the top of the graphic is Available.) When you cannot enable additional trunks, check on the following:

Are you using a signaling process that you developed yourself?
Check that your signaling process is still running. Error 32011 in the error log indicates that a signaling process has terminated.

Check that your signaling process is receiving the SL_TRUNK_ENABLE_REQ primitive.

Check that your signaling process is returning the SL_TRUNK_ENABLE_CNF primitive to Blueworx Voice Response and that the sl_send_confirm() subroutine is returning successfully.

Use signaling interface tracing the see the primitive sent to your signaling process by Blueworx Voice Response. For information on tracing signaling interfaces, see Tracing the signaling interface.