The Call is Answered Elsewhere

This scenario is similar to a call without an owner, but the user answers the phone elsewhere on the line, and this answer is detected by the provider through the hardware. The call is reported as being in the connected state, though it is not connected to any application on the local computer. The call eventually goes idle, at which point each application (monitoring as well as all owner applications) must deallocate its handle.

The following steps describe what occurs in a scenario in which a line has only monitoring applications, the service provider is configured to not answer new calls by itself, and a call comes in:

• The service provider passes the call handle to TAPI.
• TAPI passes monitor handles to the monitoring applications.
• TAPI determines that the call is in the offering (not connected) state and lets the call "sit."
• The user picks up a ringing downline phone, and the call becomes connected.
• All monitoring applications are sent a corresponding LINE_CALLSTATE message.
• The user eventually hangs up the downline phone, and the call reverts to the idle state.
• The monitor applications are notified the call is idle and deallocate their handles, if they have not already done so.
• The last deallocation causes a TSPI_lineCloseCall.