3.1 Introduction
(Page 2 of 12 in this chapter)
This section describes the protocol-independent call control functions. These functions relieve the programmer of network signaling and procedures required for establishing and maintaining connections.
The protocol-indenpendent functions require the port to execute a Channel Associated Signaling (CAS) protocol. A protocol must first be bound to a port via
adiStartProtocol
which is discussed in
Section 7.3.4,
Starting a Protocol
.
Protocol-specific events are mapped to AG Access call control events which are semantically identical across all protocols. This independence promotes portability and accelerates application development.
There are two methods for establishing connections -- placing outbound calls and receiving inbound calls. In either case, AG Access and the application exchange commands and events to advance the port to a call connected state. Eventually, AG Access and the application cooperatively release the call.
There are five functional groupings within the protocol-independent call control set:
Inbound Trunks
Outbound Trunks
Releasing Calls
Blocking Calls
Call Transfers
Following is the list of call control functions which are discussed throughout this section:
Function
Description
adiAnswerCall
Answers an incoming call.
adiBlockCalls
Blocks subsequent calls.
adiGetCallStatus
Retrieves the current call control status.
adiPlaceCall
Places an outbound call.
adiPlaceSecondCall
Places first call on hold; dials second number/extension.
adiRejectCall
Rejects an incoming call.
adiReleaseCall
Releases a call.
adiReleaseSecondCall
Releases second call; retrieves first call.
adiTransferCall
Transfers a call.
adiUnBlockCalls
Unblocks previously blocked calls.
(Page 2 of 12 in this chapter)
(Page 2 of 12 in this chapter) (Page 2 of 12 in this chapter)