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.
A version of this page is also available for
4/8/2010

This function is called by TAPI in response to the receipt of a system plug-and-play notification of a new device associated with the TSP.

Syntax 

LONG TSPIAPI TSPI_providerCreatePhoneDevice(
  HKEY 
hActive, 
  LPCWSTR 
szDevKey, 
  LPCWSTR 
szDevName
);

Parameters

hActive

Handle to the open registry key for the active instance of the device key.

szDevKey

Registry path string to the device key.

szDevName

New name of the device, for example COM2.

Return Value

Returns zero if the request succeeds or an error number if an error occurs. The following table shows the return values for this method.

Value Description

LINEERR_BADDEVICEID

The device id is incorrect.

LINEERR_NOMEM

Not enough memory is available.

LINEERR_OPERATIONFAILED

The operation failed.

Remarks

TAPI calls the TSPI-provider CreatePhoneDevicewhen it receives a plug-and-play system notification that a new device, which is associated with the TSP, has been added to the system. This association is indicated in the registry key of the new device. If the TSP chooses to create a phone device, it should also send a PHONE_CREATEmessage to TAPI.

Requirements

Header tapicomn.h
Library coredll.lib
Windows Embedded CE Windows CE 3.0 and later
Windows Mobile Windows Mobile Version 5.0 and later