3.5 Releasing Calls

 (Page 6 of 12 in this chapter)
In order for AG Access to release a call, both the application and the network must actively release it. The network can disconnect at any time regardless of the call control state.

After the call is released by both the network and the application, AG Access generates a call released event. Once the call is released, no more DSP-related events will be generated on the port and the application is eligible to receive and place new calls.

Procedures for both types of call releases are discussed below.

3.5.1 Network-Initiated Release

Network-initiated call release is a three-step process:

  1. AG Access detects the network disconnect and generates a call disconnected event (ADIEVN_CALL_DISCONNECTED). All active DSP functions are terminated and their done events are generated.

Note: After the application retrieves the disconnected event from the driver, AG Access will not allow DSP-related functions to be started on the port.
  1. In response to the disconnected event, the application invokes adiReleaseCall.

  2. AG Access generates a call released event (ADIEVN_CALL_RELEASED) when its internal state is reset to idle.

3.5.2 Application-Initiated Release

An application-initiated release is a two-step process:

  1. The application invokes adiReleaseCall. AG Access will not allow DSP-related functions to be started on the port.

  2. AG Access executes the network tear-down procedure, resets its internal state to IDLE, and generates a call released event. The application is now eligible to place and receive new calls.

(Page 6 of 12 in this chapter)

Copyright 1996 Natural MicroSystems, Inc. All Rights Reserved.