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 message is sent to the PHONEEVENTcallback function to create a new device.

Syntax 

PHONE_CREATE

htPhone = (HTAPIPHONE) 0; 

dwMsg = (DWORD) PHONE_CREATE; 

dwParam1 = (DWORD) 
hProvider; 

dwParam2 = (DWORD) 
lpdwDeviceId; 

dwParam3 = (DWORD) 0;

Parameters

htPhone

Not used.

dwMsg

The value PHONE_CREATE.

dwParam1

The service provider handle (hProvider) as received in TSPI_providerEnumDevices.

dwParam2

Contains a pointer to a device identifier, which TAPI will fill.

dwParam3

Not used.

Return Value

None.

Remarks

This message is sent to the PHONEEVENTcallback entry point in TAPI. The service provider receives a pointer to this callback in the TSPI_providerEnumDevicesfunction and in each TSPI_phoneOpenfunction; the PHONE_CREATE message can be sent to the PHONEEVENTcallback function given to any open phone or at startup.

Devices cannot be removed dynamically. If a service provider wants to remove a phone from service, it sends a PHONE_STATE (TSPI)(PHONESTATE_DISCONNECTED) message. It can then refuse (for example, by returning PHONEERR_INVALPHONESTATE) to perform any operation with the device until it returns to service or the provider is shut down and restarted (in which case the device could be not declared in TSPI_providerEnumDevices, effectively removing it from the system).

For backward compatibility, older service providers are not expected to send this message. If they do, the message is treated in the same manner as described above for new service providers.

Requirements

Header tapi.h
Windows Embedded CE Windows CE 3.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also