2.7 Network Protocols

 (Page 8 of 11 in this chapter)
The AG board provides a protocol engine called the Generalized Trunk Protocol (GTP) engine. The GTP engine executes network protocol procedures based upon events received from the network and the application. Sample network protocols include:

Every Channel Associated Signaling (CAS) protocol supported by AG Access has a corresponding Trunk Control Program (TCP). TCPs are downloaded by the agmon program to the AG board when the board is initialized. The following are examples of specific TCPs:

Every AG Access port must be associated with a protocol. The AG DSP functions are not accessible until the port's protocol has started.

Once a protocol is executing on a port, AG Access provides protocol-independent call control functionality. These call control functions abstract network connection functions, thus relieving the application of network signaling details. Call control functions are discussed in Chapter 3.

Note: The AG board supports a null protocol called NOCC (no call control). NOCC is stateless and does not generate any call control events. Developers use NOCC under one of the following conditions:

When running NOCC, all DSP functions are available once the protocol is started.

Throughout this document, statements are made about certain functions only being valid in the "call control connected" or "line connected" state. These statements do not apply to NOCC.

(Page 8 of 11 in this chapter)

Copyright 1996 Natural MicroSystems, Inc. All Rights Reserved.