(Page 3 of 6 in this chapter)

1.2 Basic Terminology

Familiarize yourself with the following terms and concepts as you work with AG Access. Some of the most frequently used terms in this manual are used in a way specific to AG Access.
A port is the object on which telephony functions are performed, and it contains physical and logical resources on the AG board. A port is represented by a context and a context handle (ctahd), a software handle that enables the application (and its developer) to keep track of software activities. This manual refers to ports and contexts almost interchangeably, but keep in mind that the term port connotes an object, typically connected to a telephony network and used to process calls, and the term context refers to a software handle.
In order to access most functionality on a port, the application must associate a telephony protocol with the port. The telephony protocol is embodied by a Trunk Control Program (TCP), and must be loaded during board initialization. NMS provides TCPs for most standard telephone line interfaces. Starting a protocol enables the use of call control functions. Almost all functions require a protocol to be loaded. For applications that do not use call control functions, or choose to manage the line interface manually, a special TCP is provided called "NOCC" for "no call control."
In this manual, operation refers to an active process, such as a recording operation, or a digit collecting operation. Function refers specifically to a function call.

(Page 3 of 6 in this chapter)

Tech_Support@nmss.com