(Page 2 of 9 in this chapter)
Introduction
This appendix lists the telephony protocol classifications shipped with this product, and their associated parameter structures. Pass pointers to these protocol-specific parameter structures to
adiStartProtocol
if you do not want to use the default values.
Please contact NMS Sales about the availability of other telephony protocol classes, such as MFC-R2.
The following protocol classifications are provided:
TCP File Name
Board
Description
nocc.tcp
Any AG board
No call control
did0.tcp
AG-T1 or AG-8/DID
Digital/Analog Wink-start (inbound only)
fdi0.tcp
AG-8/DID
Feature Group D (inbound only)
gst8.tcp
AG-T1
Digital Ground-start (OPS-FX)
gst9.tcp
AG-T1
Digital Ground-start (OPS-SA)
lps0.tcp
AG-8
Analog Loop-start
lps8.tcp
AG-T1
Digital Loop-start (OPS-FX)
lps9.tcp
AG-T1
Digital Loop-start (OPS-SA)
ogt0.tcp
AG-T1 or AG-8/DID
Digital/Analog Wink-start (outbound only)
wnk0.tcp
AG-T1 or AG-8/DID
Digital/Analog Wink-start
wnk1.tcp
AG-8/E&M
Analog Wink-start
About Executing Telephony Protocols
Executing a telephony protocol in the AG Access environment requires two steps. First, the protocol, which is embodied by a Trunk Control Program (a .
tcp
file), must be loaded to the AG board with
agmon
at board initialization. If it is not loaded to the AG board, it will not be available to an application on the host computer. The
ag.cfg
configuration file specifies which TCPs are loaded to the board. Make sure that all telephony protocols that your application uses are loaded. For detailed information about
agmon
, see the
AG Access Installation Manual
.
The application must start a telephony protocol on each open port by invoking
adiStartProtocol
. A special telephony protocol,
NOCC
, is available for scenarios in which call control is not needed.
(Page 2 of 9 in this chapter)
Tech_Support@nmss.com
Copyright © 1996, Natural MicroSystems, Inc. All rights reserved.
(Page 2 of 9 in this chapter) (Page 2 of 9 in this chapter)