(Page 2 of 10 in this chapter)

2.1 Introduction

AG Access is designed to: Maximize performance by taking full advantage of concurrent processing between the host CPU and the AG board's control processor; Allow a single process or thread to control multiple AG ports/telephone network lines; and Maximize portability between operating systems.
The AG Access library contains sets of functions which accomplish the following telephony tasks: Call control Voice record and play Digit (DTMF) collection DTMF and tone generation DTMF, energy, and tone detection Echo cancelling Call progress analysis Low-level control of the AG board
AG Access employs asynchronous functions in its programming model in order to capitalize on the concurrent processing between AG control processors on the board and the host CPU. As shown in Figure 1, the application program starts telephony activities on the AG board using AG Access function calls, and receives AG Access events. . Figure 1. AG Access Architecture
Exact system startup sequences vary between operating systems. Setting up the environment and running an AG Access application follows the same general steps: System boot-up, at which time the AG driver is loaded. A startup command file runs agmon, which loads runtime and DSP software to the AG boards, configures each board's MVIP switch, initiates self-checks, and reports initial status. Note that agmon should be left running in the background so that it can continue to monitor the AG board(s)'s status. A startup command file launches AG Access application(s).

(Page 2 of 10 in this chapter)

tech_support@nmss.com