The PHONESTATE_ bit-flag constants describe various status items for a phone
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 PC is
plugged in with TAPI active.
The connection between the phone device and TAPI was just broken. This happens
when the wire connecting the phone set to the PC is unplugged while TAPI is
The number of owners for the phone device.
The number of monitors for the phone device.
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 for the appearance of new phone devices), the application
should reinitialize its use of TAPI.
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 that 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
to obtain the updated information.
Indicates that the device is being removed from the system by the service
provider (most likely through user action, through a control panel or similar
utility). A PHONE_STATE
message with this value will normally be immediately followed by a PHONE_CLOSE
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 that have negotiated TAPI
version 0x00010004 or above; applications negotiating a previous API version
will not receive any notification.
No extensibility. All 32 bits are reserved.
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages