Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The DeviceSpecific method enables service providers to provide access to device specific features not offered by other TAPI functions. The meaning of the extensions are device specific, and taking advantage of these extensions requires the application to be fully aware of them.
This method is provided for C and C++ applications. Automation client applications, such as those written in Visual Basic, must use the DeviceSpecificVariant method.
Syntax
HRESULT DeviceSpecific(
[in] BYTE *pParams,
[in] DWORD dwSize
);
Parameters
[in] pParams
Pointer to a memory area used to hold a parameter block. The format of this parameter block is device specific; TAPI passes its contents between the application and the service provider.
[in] dwSize
The size, in bytes, of the parameter block area.
Return value
This method can return one of these values.
| Return code | Description |
|---|---|
|
Method succeeded. |
|
Insufficient memory exists to perform the operation. |
|
The pParams parameter is not a valid pointer. |
Remarks
Caution
TAPI will write the returned data to the buffer referenced by pParams when the LINE_REPLY message is returned. This means that the buffer must remain valid until the LINE_REPLY message is returned; otherwise, data corruption and exceptions may occur.
Requirements
| Requirement | Value |
|---|---|
| Target Platform | Windows |
| Header | tapi3if.h (include Tapi3.h) |
| Library | Uuid.lib |
| DLL | Tapi3.dll |