McDewey

more bits set, this parameter also must have at least one bit set. This parameter uses the following PHONEBUTTONSTATE_constants: • PHONEBUTTONSTATE_UP -The button is in the “up” state. • PHONEBUTTONSTATE_DOWN -The button is in the “down” state (pressed down). • PHONEBUTTONSTATE_UNKNOWN -The up or down state of the button is unknown at this time but may become known later. • PHONEBUTTONSTATE_UNAVAIL -The service provider does not know the up or down state of the button, and the state will not become known. phoneShutdown The phoneShutdown function shuts down the application usage of the TAPI phone abstraction. If this function is called when the application has open phone devices, these devices are closed. Note Function Details LONG WINAPI phoneShutdown( HPHONEAPP hPhoneApp ); Parameter hPhoneApp The application usage handle for TAPI. Return Values Returns zero if the request succeeds or a negative number if an error occurs. Possible return values follow: PHONEERR_INVALAPPHANDLE, PHONEERR_NOMEM, PHONEERR_UNINITIALIZED, PHONEERR_RESOURCEUNAVAIL. TAPI Phone Messages Messages notify the application of asynchronous events. All messages get sent to the application through the message notification mechanism that the application specified in lineInitializeEx. The message always contains a handle to the relevant object (phone, line, or call), of which the application can determine the type from the message type. The following table describes TAPI Phone messages. Table 19: TAPI Phone Messages TAPI Phone Messages PHONE_BUTTON, on page 291 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 290 Basic TAPI Implementation phoneShutdown