/mcpdwPhoneStates These flags specify the set of phone status changes and events for which the application can receive notification messages. This parameter can have zero, one, or more bits set. This parameter uses the following PHONESTATE_ constants: • PHONESTATE_OTHER -Phone status items other than those in the following list changed. The application should check the current phone status to determine which items changed. • PHONESTATE_OWNER -The number of owners for the phone device changed. • PHONESTATE_MONITORS -The number of monitors for the phone device changed. • PHONESTATE_DISPLAY -The display of the phone changed. • PHONESTATE_LAMP -A lamp of the phone changed. • PHONESTATE_RINGMODE -The ring mode of the phone changed. • PHONESTATE_SPEAKERHOOKSWITCH -The hookswitch state changed for this speakerphone. • PHONESTATE_REINIT -Items 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. New phoneInitialize, phoneInitializeEx, and phoneOpen requests get denied until applications have shut down their usage of TAPI. The hDevice parameter of the PHONE_STATE message stays NULL for this state change because it applies to any line in the system. Because of the critical nature of PHONESTATE_REINIT, you cannot mask such messages, so the setting of this bit gets ignored, and the messages always get delivered to the application. • PHONESTATE_REMOVED -Indicates that the service provider is removing the device from the system (most likely through user action, through a control panel or similar utility). A PHONE_CLOSE message on the device immediately follows a PHONE_STATE message with this value. Subsequent attempts to access the device prior to TAPI being reinitialized result in PHONEERR_NODEVICE being returned to the application. If a service provider sends a PHONE_STATE message that contains this value to TAPI, TAPI passes it along to applications that negotiated TAPI version 1.4 or later; applications that negotiated a previous TAPI version do not receive any notification. dwButtonModes The set of phone-button modes for which the application can receive notification messages. This parameter can have zero, one, or more bits set. This parameter uses the following PHONEBUTTONMODE_constants: • PHONEBUTTONMODE_CALL -The button is assigned to a call appearance. • PHONEBUTTONMODE_FEATURE -The button is assigned to requesting features from the switch, such as hold, conference, and transfer. • PHONEBUTTONMODE_KEYPAD -The button is one of the 12 keypad buttons, ‘0’ through ‘9’, ‘*’, and ‘#’. • PHONEBUTTONMODE_DISPLAY -The button is a “soft” button that is associated with the phone display. A phone set can have zero or more display buttons. dwButtonStates The set of phone-button state changes for which the application can receive notification messages. If the dwButtonModes parameter is zero, the system ignores dwButtonStates. If dwButtonModes has one or Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 289 Basic TAPI Implementation phoneSetStatusMessages