Call Control Function
3.6 Blocking Calls
(Page 7 of 12 in this chapter)
- AG Access provides the capability for the application to block incoming calls and
prevent placement of outbound calls. While calls are being blocked, no call
control events are generated.
- The application blocks calls by invoking the adiBlockCalls function in any call
control state. Blocking will only take effect when the port is in the call idle state.
If the port has an active call when the function is invoked, blocking will be
deferred until the call is released.
- When AG Access begins blocking calls, the ADIEVN_CALLS_BLOCKED event is
generated. The application will no longer receive any call control events or be
allowed to place any outbound calls until the port is unblocked.
- The method by which calls are blocked is defined in the call control blockmode
parameter. The two blocking methods are:
- The former method is a passive rejection and behaves as though the application
has pre-responded to each call with an adiRejectCall (e.g., on loop-start lines the
call is not answered; on wink-start lines reorder tone is played). The latter method
takes an active role (if the protocol supports it) and notifies the network via
signaling that the line is not receiving any calls.
- The port is unblocked by invoking adiUnBlockCalls. After the function is
executed, the ADIEVN_CALLS_UNBLOCKED event is generated, the port returns
to the call control idle state, and new calls may be established.
(Page 7 of 12 in this chapter)
Copyright 1996 Natural MicroSystems, Inc. All Rights Reserved.