(Page 7 of 10 in this chapter)
2.6 About Telephone Network Protocols
- The AG board control processor executes a protocol engine called the Generalized Trunk Protocol (GTP) engine. The GTP engine executes telephone network protocol procedures based upon events received from the telephone network and commands received from the application. For example, AG Access includes the capability to work with Loop-Start and DID/Wink-Start telephony protocols.
- Every telephony network protocol supported by AG Access has a corresponding Trunk Control Program (TCP). TCPs are downloaded by agmon to the AG board when the board is initialized. The following are examples of specific TCPs:
- wnk1 - Wink-start protocol for E&M on AG-8 boards in the USA.
- For a complete listing of telephony protocols shipped with AG Access and their related parameter structures, see Appendix C in the AG Access Function Reference Manual.
- Every AG Access port must be associated with a protocol. The AG DSP-related functions are not accessible until the protocol has been 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, which relieves 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 should use NOCC under one of the following conditions:
- The application is managing the protocol.
When an application is running NOCC, all functions that require DSP resources are available once the protocol is started.
(Page 7 of 10 in this chapter)
tech_support@nmss.com
Copyright © 1997, Natural MicroSystems, Inc. All rights
reserved.