See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This function is used as a general extension mechanism to enable a Telephony API implementation to provide features not described in the other TAPI functions. The meanings of these extensions are device specific.
Syntax
LONG WINAPI phoneDevSpecific( HPHONE hPhone, LPVOID lpParams, DWORD dwSize ); |
Parameters
- hPhone
-
Handle to a phone device.
- lpParams
-
Pointer to a memory area used to hold a parameter block. Its interpretation is device specific. The contents of the parameter block are passed unchanged to or from the service provider by TAPI.
- dwSize
-
Size, in bytes, of the parameter block area.
Return Value
Returns a positive request identifier if the function is completed asynchronously or a negative error number if an error occurs. The dwParam2parameter of the corresponding PHONE_REPLYmessage is zero if the function succeeds or it is a negative error number if an error occurs. The following table shows the return values for this function.
| Value | Description |
|---|---|
|
PHONEERR_INVALPHONEHANDLE |
The handle to the phone device is invalid. |
|
PHONEERR_NOMEM |
Not enough memory is available. |
|
PHONEERR_INVALPOINTER |
The pointer is invalid. |
|
PHONEERR_RESOURCEUNAVAIL |
The resources are unavailable. |
|
PHONEERR_OPERATIONUNAVAIL |
The operation is unavailable. |
|
PHONEERR_UNINITIALIZED |
A parameter is uninitialized. |
|
PHONEERR_OPERATIONFAILED |
The operation failed. |
Additional return values are device specific.
Remarks
This operation provides a generic parameter profile. The interpretation of the parameter block is device specific. Indications and replies that are device specific should use the PHONE_DEVSPECIFICmessage.
A service provider can provide access to device-specific functions by defining parameters for use with this operation. Applications that want to make use of these device-specific extensions should consult the device-specific (vendor-specific) documentation that describes which extensions are defined. Typically, an application that relies on these device-specific extensions is not portable to work with other service-provider environments.
 Note: |
|---|
| This function is for TAPI version 2.0 and later. |
Requirements
| Header | tapi.h |
| Library | coredll.lib |
| Windows Embedded CE | Windows CE 3.0 and later |
| Windows Mobile | Windows Mobile Version 5.0 and later |