function queries a specified phone device to determine its telephony
| HPHONEAPP hPhoneApp,
| DWORD dwDeviceID,
| DWORD dwAPIVersion,
| DWORD dwExtVersion,
| LPPHONECAPS lpPhoneCaps
The handle to the application's registration with TAPI.
The phone device to be queried.
The version number of the Telephony API to be used. The high-order word
contains the major version number; the low-order word contains the minor version
number. This number is obtained with the function phoneNegotiateAPIVersion
The version number of the service provider-specific extensions to be used.
This number is obtained with the function phoneNegotiateExtVersion
. It can be left zero if no device-specific extensions are to be used.
Otherwise, the high-order word contains the major version number; the low-order word
contains the minor version number.
A pointer to a variably sized structure of type PHONECAPS
. Upon successful completion of the request, this structure is filled with
phone device capabilities information.
Returns zero if the request is successful or a negative error number if an
error has occurred. Possible return values are:
PHONEERR_INVALAPPHANDLE, PHONEERR_INVALPOINTER, PHONEERR_BADDEVICEID,
PHONEERR_OPERATIONFAILED, PHONEERR_INCOMPATIBLEAPIVERSION, PHONEERR_OPERATIONUNAVAIL,
PHONEERR_INCOMPATIBLEEXTVERSION, PHONEERR_NOMEM, PHONEERR_STRUCTURETOOSMALL,
PHONEERR_RESOURCEUNAVAIL, PHONEERR_NODRIVER, PHONEERR_UNINITIALIZED,
Before using phoneGetDevCaps
, the application must negotiate the TAPI version number to use, and
optionally, the extension version to use.
TAPI and extension version numbers are those under which TAPI, Telephony DLL,
and service provider must operate. If version ranges do not overlap, the
application and API or service-provider versions are incompatible and an error is
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages