This event fiers, when no PHONE_REPLY message is received from TAPI within a time period of Options.ReplyTimeout milliseconds.

Many functions within TAPI work in an asynchronous manner. An asynhron functions returns immediatly but the operation is not completed at this time. The function returns an operation identifier, the RequestID, which is used to get the result of the operaton at a later time. TAPI signals the completion by sending a related PHONE_REPLY message to the application. The PHONE_REPLY message contains the RequestID and the ResultCode of the operation.

hbTapi Components is able to insulates you from these types of functions by stalling your code execution until the PHONE_REPLY message is returned. See the property Options.SyncMode for further Information. If ThbTapiPhone works in asynchron mode, you have to handle the replys on your own by using the OnTapiReply and OnTapiTimeout events.

Availability

Design-Time: Read, Write / Run-Time: Read, Write

Declaration

procedure (Sender: TObject; RequestID: DWORD);
property OnTapiTimeout: ThbTapiTimeoutEvent;

Description

Please refer to the section "PHONE_REPLY" in TAPI's documentation for a more detailed information.

See Also

ThbTapiPhone.Options.SyncMode and ReplyTimeout ,ThbTapiPhone.LastRequestID