phoneDevSpecific

A version of this page is also available for

Windows Embedded CE 6.0 R3

4/8/2010

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 dwParam2 parameter of the corresponding PHONE_REPLY message 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.

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_DEVSPECIFIC message.

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.

Requirements

See Also

Reference

PHONE_REPLY