Terminate a Session

Session termination may originate with a user request, remote disconnection by the other party, or for application-specific reasons. When a session is terminated, the session identifier remains valid until specifically released and can be used to gather post-connection data.

Session termination is completed by deallocating and releasing the resources associated with the session. If a session is merely dropped or disconnected but resources are not released, the result is a memory leak in the application and possibly in the service provider as well.

TAPI 2.x: See lineDrop, lineDeallocateCall.

TAPI 3.x: See ITBasicCallControl::Disconnect, perform a standard COM release on the Call object pointer.