|
|
|
|
|
The IRAPI is composed of several elements. The Resource Manager (RM) pseudo-driver manages system resources and call profiles for each active channel. The call profile is a collection of data about a call including the channel number, ANI, DNIS, and the start time of the call. The voice response output process (VROP) manages interactions between the file system and speech resources. The IRAPI library is linked to processes that use the IRAPI. The library uses the speech resources and network interface (NI) cards, VROP and RM to manage applications. The library communicates with the maintenance subsystem via the logger. The Application Dispatch (AD) process is responsible for examining new calls for DNIS, ANI and channel information in the call profile and starting the appropriate application based on the call profile.
All processes that use the IRAPI are considered IRAPI applications. TSM is a multi-channel IRAPI application that runs applications that are driven by information in scripts. Scripts use the IRAPI to manage speech pools. Other applications that use the IRAPI might be user processes, custom applications or conventional Avaya IR system data interface processes (DIPs).
The IRAPI is linked into all processes that use it. Instances of the following processes linked to the IRAPI maintain per-process private data for managing the application/platform interface.
This is an application that starts when invoked only when an application should run on a channel. The application can start in response to an incoming call or in preparation to make an outbound call. The application uses the IRAPI to interface to the voice system. A transient process can handle one or more channels.
This is an application that starts once (usually at system startup). The application uses the IRAPI to interface to the voice system. It handles one or more channels of some application.
TSM is a multi-channel IRAPI application that runs TAS scripts.
AD receives new call indications and determines what application should be started based on the caller's channel and dialed number, and uses irExec to start that application. By default, channel ownership reverts to AD when applications fail abruptly or release channels.
