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 inform an application of the removal (deletion from the system) of a phone device. Generally, this is not used for temporary removals, such as extraction of PCMCIA devices, but only for permanent removals in which the device would no longer be reported by the service provider if TAPI were reinitialized.

Syntax 

PHONE_REMOVE

hDevice = (DWORD) 0;

dwCallbackInstance = (DWORD) 0;

dwParam1 = (DWORD) 
hDeviceID;

dwParam2 = (DWORD) 0;

dwParam3 = (DWORD) 0;

Parameters

hDevice

Reserved. Set to zero.

dwCallbackInstance

Reserved. Set to zero.

dwParam1

Identifier of the phone device that was removed.

dwParam2

Reserved. Set to zero.

dwParam3

Reserved. Set to zero.

Return Value

None.

Remarks and Backward Compatibility

Applications TAPI 2.0 or later are sent a PHONE_REMOVE message. This informs them that the device has been removed from the system. The PHONE_REMOVE message is preceded by a PHONE_CLOSE (TAPI)message on each phone handle, if the application had the phone open. This message is sent to all applications supporting TAPI 2.0 or later that have called the phoneInitializeExfunction, including those that do not have any phone devices open at the time.

Older applications that negotiated TAPI 1.4 or earlier are sent a PHONE_STATE (TAPI)message specifying PHONESTATE_REMOVED, followed by a PHONE_CLOSE message. Unlike the PHONE_REMOVE message, however, these older applications can receive these messages only if they have the phone open when it is removed. If they do not have the phone open, their only indication that the device was removed would be receiving a PHONEERR_NODEVICE when they attempt to access the device.

After a device has been removed, any attempt to access the device by its device identifier results in a PHONEERR_NODEVICE error. After all TAPI applications have shutdown so that TAPI can restart, and when TAPI is reinitialized, the removed device no longer occupies a device identifier.

Note:
It is TAPI that returns this PHONEERR_NODEVICE message after a PHONE_REMOVE message is received from a service provider; no further calls are made to that service provider using that phone device identifier.

Requirements

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

See Also