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 pointer used to retrieve information remains until specifically released.

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: lineDrop, lineDeallocateCall

TAPI 3: ITBasicCallControl::Disconnect releases all Call Object interface pointers associated with the session.