(Page 7 of 12 in this chapter)
3.6 Blocking and Unblocking Calls
- 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.
- To block calls on a specified port, invoke adiBlockCalls from any call control state. Blocking will only take effect when the port is in the 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 application will no longer receive any call control events or be allowed to place any outbound calls until the port is unblocked.
- AG Access supports two blocking methods, which are:
- Reverse-make-busy, which takes an active role (if the protocol supports it)
and notifies the telephone network by signaling that the line is not receiving
any calls.
- To unblock a port, invoke adiUnBlockCalls.
3.6.1 Call Blocking Parameters
- The ADI_CALLCTL_PARMS structure contains the blockmode parameter, which can be set to 0 to reject all incoming calls, or to 1 to respond with a reverse-make-busy signal.
3.6.2 Call Blocking Events
- When AG Access begins blocking calls, the ADIEVN_CALLS_BLOCKED event is generated. The application will not receive any subsequent call control events or be allowed to place any outbound calls until the port is unblocked.
- After adiUnBlockCalls 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)
tech_support@nmss.com
Copyright © 1997, Natural MicroSystems, Inc. All rights
reserved.