function returns which phone-state changes on the specified phone device will
generate a callback to the application.
| HPHONE hPhone,
| LPDWORD lpdwPhoneStates,
| LPDWORD lpdwButtonModes,
| LPDWORD lpdwButtonStates
A handle to the open phone device to be monitored.
A pointer to a PHONESTATE_ constant. These flags specify the set of phone
status changes and events for which the application wishes to receive notification
messages. The lpdwPhoneStates
parameter can return a value with zero, one, or multiple bits set. Monitoring
can be individually enabled and disabled for:
Phone-status items other than those listed below have changed. The application
should check the current phone status to determine which items have changed.
The connection between the phone device and TAPI was just made. This happens
when TAPI is first invoked or when the wire connecting the phone to the computer
is plugged in while TAPI is active.
The connection between the phone device and TAPI was just broken. This happens
when the wire connecting the phone set to the computer is unplugged while TAPI
The number of owners for the phone device has changed.
The number of monitors for the phone device has changed.
The display of the phone has changed.
A lamp of the phone has changed.
The ring mode of the phone has changed.
The ring volume of the phone has changed.
The handset hookswitch state has changed.
The handset's speaker volume setting has changed.
The handset's microphone gain setting has changed.
The speakerphone's hookswitch state has changed.
The speakerphone's speaker volume setting has changed.
The speakerphone's microphone gain setting state has changed.
The headset's hookswitch state has changed.
The headset's speaker volume setting has changed.
The headset's microphone gain setting has changed.
The application's use of the phone is temporarily suspended.
The application's use of the phone device is resumed after having been
suspended for some time.
The phone's device-specific information has changed.
Items have changed in the configuration of phone devices. To become aware of
these changes (as with the appearance of new phone devices) the application
should reinitialize its use of TAPI. The hDevice
parameter of the PHONE_STATE
message is left NULL for this state change, as it applies to any of the
phones in the system.
Indicates that, due to configuration changes made by the user or other
circumstances, one or more of the fields in the PHONECAPS
structure have changed. The application should use phoneGetDevCaps
to read the updated structure. If a service provider sends a PHONE_STATE
message containing this value to TAPI, TAPI will pass it along to applications
which have negotiated TAPI version 0x00010004 or above; applications negotiating a
previous API version will receive PHONE_STATE messages specifying
PHONESTATE_REINIT, requiring them to shutdown and reinitialize their connection to TAPI in
order to obtain the updated information.
Indicates that the device is being removed from the system by the service
provider (most likely through user action, via a control panel or similar utility).
A PHONE_STATE message with this value will normally be immediately followed by
message on the device. Subsequent attempts to access the device prior to TAPI
being reinitialized will result in PHONEERR_NODEVICE being returned to the
application. If a service provider sends a PHONE_STATE message containing this
value to TAPI, TAPI will pass it along to applications which have negotiated TAPI
version 0x00010004 or above; applications negotiating a previous API version
will not receive any notification.
A pointer to a . These flags specify the set of phone-button modes for which
the application wishes to receive notification messages. The lpdwButtonModes
parameter can return a value with zero, one, or multiple bits set. This
parameter uses the following PHONEBUTTONMODE_ constants:
The button is assigned to a call appearance.
The button is assigned to requesting features from the switch, such as hold,
conference, and transfer.
The button is one of the twelve keypad buttons, '0' through '9', '*', and '#'.
The button is a local function button, such as mute or volume control.
The button is a "soft" button associated with the phone's display. A phone set
can have zero or more display buttons.
A pointer to a DWORD-sized location that contains flags specifying the set of
phone button state changes for which the application wishes to receive
notification messages. The lpdwButtonStates
field can return a value with zero, one or multiple bits set. This parameter
uses the following PHONEBUTTONSTATE_ constants:
The button is in the "up" state.
The button is in the "down" state (pressed down).
Indicates that the up or down state of the button is not known at this time,
but may become known at a future time.
Indicates that the up or down state of the button is not known to the service
provider, and will not become known at a future time.
Returns zero if the request is successful or a negative error number if an
error has occurred. Possible return values are:
PHONEERR_INVALPHONEHANDLE, PHONEERR_NOMEM, PHONEERR_INVALPOINTER,
PHONEERR_RESOURCEUNAVAIL, PHONEERR_OPERATIONFAILED, PHONEERR_UNINITIALIZED.
An application can use phoneGetStatusMessages
to query the generation of the corresponding messages. Message generation can
be controlled by phoneSetStatusMessages
. All phone status messages are disabled by default.
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages