IC Connector at Runtime

CTI and IC Connectors > About the IC Connector > IC Connector at Runtime

	IC Connector at Runtime

At runtime, the IVR system that uses the Dialog Designer speech application configured for IC and the IC system must both be configured to monitor the same channel for incoming calls. The IVR system can be either an Avaya IR or an Avaya Voice Portal system.

As a call comes in on a channel that the IC system is monitoring, the switch notifies the IC system. When the call is recognized on the IVR system, the Dialog Designer application running on the IVR system sends a new call command to the IC system. The IC system, in return, creates a new EDU and returns the ID to the application on the IVR system, where it populates the vdu id variable field value. This establishes a pipeline to the IC system for the call, thus making IC functionality available for use during that session.

Note:

The Avaya Voice Portal system does not use the concept of channels in routing calls, but rather of extensions. So, if you are using the IC connector in an application on a Voice Portal system, the channel that the IC system is monitoring on the switch must be mapped to a specific extension on the Voice Portal system. That is, if the IC system is using channel 1234, the extension you use on the Voice Portal system must be 1234. See the Avaya Voice Portal documentation library.

If this dual connection cannot be established within a period of time configurable on the IC system, the IVR system generates an error and discontinues the call.

At the end of the call, the speech application sends a call gone command to the IC system to signal that it can also disconnect the call.

IC will set the session.lasterror field when an error occurs during execution of an IC command. You can check this field to obtain detailed error information. If empty, no error has occurred.

You may also choose to disable runtime exceptions by setting the flag sage.ic.throwexceptions to false (default is true) in the speech application's web descriptor parameters. When an IC error has occurred, you can check the lasterror field to determine if the IC call was successful.

In Dialog Designer 5.0, the preferred way to catch errors is to "catch" SCERuntimeException. See Catch (VXML Events).

WARNING:

If IC exceptions are disabled, you must check this field after every call or you risk missing errors that might have occurred.