This topic describes how connections are cleared under the following circumstances:
The application requests clearing the outgoing connection by invoking TUPReleaseReq. The application is notified of the completion of the release procedure (the receipt of a release complete message) when it receives a TUP release confirm (EVTTUPRELCFM) event. The following illustration shows the process by which the application performs outgoing connection release:
If the far exchange initiates the release of the outgoing connection, the application receives a TUP release indication event from the TUP layer. The application then completes the connection release by invoking TUPReleaseReq to send the release message to the far exchange and wait for the TUP release confirm (EVTTUPRELCFM) event. The following illustration shows the process by which far exchange connection release for outgoing connections occurs:
If the far exchange initiates the release of its own outgoing connection, the application receives a TUP release indication (EVTTUPRELIND) event from its incoming connection of the TUP layer. The following illustration shows the process by which the application performs far exchange connection release for incoming connections:
To clear an incoming connection, the application starts with TUPStatusReq and waits for TUPReleaseInd to return. The application can then answer with TUPReleaseResp. The following illustration shows the process by which the application performs incoming connection release: