Initialization and Shutdown
For an application to use any of TAPI's 30 supplementary phone functions, it
needs a connection to TAPI, through which it can receive messages. The
application establishes this connection using the
phoneInitializeEx function. In this function, the application specifies the notification
mechanism by which TAPI informs the application of changes in the state of the phone
and of asynchronous completion of phone functions.
The
phoneInitializeEx function returns two pieces of information to the application: an
application handle, and the number of phone devices. The application handle represents the
application's usage of TAPI. The TAPI functions that use phone handles do not
require the application handle, as this handle is derived from the specified phone
handle.
The second piece of information returned by
phoneInitializeEx is the number of phone devices available to the application through the
Telephony API. Phone devices are identified by their device identifier (
device ID). Valid device IDs range from zero to the number of phone devices minus one.
For example, if
phoneInitializeEx reports that there are two phone devices in a system, then valid phone device
IDs are 0 and 1. Once an application is finished using the phone functions of
TAPI, it invokes
phoneShutdown, passing its application handle to shut down its usage of TAPI. This allows
TAPI to free any resources assigned to the application.
Both
phoneInitializeEx and
phoneShutdown operate synchronously. That is, these functions either return a success or
failure indication, and never return an asynchronous Request ID.
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database