|
|
|
|
|
The AD process listens to new calls that arrive on the network, finds an application to handle the call, and starts the associated application with irExec. AD uses call information stored in the AD tables (such as DNIS, ANI, and the port number) to associate applications with calls. The OA&M system can establish, break, and query this association through the IRAPI. AD holds all idle channels and releases them upon receiving a request. For example, the soft_szr command causes TSM to request a channel from AD to run a TSM script.
Applications can change the behavior of AD via the AD-API. The AD-API allows users to add entries to the AD table, query the AD table, and remove entries from the AD table (See Application Dispatch tables). AD can be instructed to dispatch calls for a subset of the channels in the system. It is also possible to substitute an alternative AD that implements some other dispatch logic. For example, an alternative AD might not use fixed tables, but would rather consult an network control point (NCP) over a network to make the routing decision.
Note:
You can administer the DNIS and ANI tables using the assign, delete, and display commands.
When a new call arrives, if AD is the application owner for the channel, it starts the application.
Note:
AD need not be the agent for starting applications. Users can develop and use their own processes that handle the AD function, or they can rely on the applications to allocate channels and start themselves up in response to new calls.
