This event is called when a PHONE_REPLY message was received from TAPI. This allows all TAPI reply messages to be captured. You have to handle reply messages when you are working directly with asynchron TAPI functions or when you are using the ThbTapiPhone component in an asynchron modus by setting the ThbTapiPhone.Options.SyncMode property to False.

Many function 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 and LastRequestID for further Information.

Availability

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

Declaration

procedure (Sender: TObject; RequestID: DWORD; ReplyCode: ThbTapiResult);
property OnTapiReply : ThbTapiReplyEvent;

Remarks

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

See Also

ThbTapiPhone.LastRequestID | OnTapiTimeout, Options.SyncMode and ReplyTimeout,