McDewey

TAPI Phone Messages PHONE_CLOSE, on page 294 PHONE_CREATE, on page 294 PHONE_REMOVE, on page 295 PHONE_REPLY, on page 296 PHONE_STATE, on page 296 PHONE_BUTTON The PHONE_BUTTON message notifies the application that button press monitoring is enabled if it has detected a button press on the local phone. Function Details PHONE_BUTTON hPhone = (HPHONE) hPhoneDevice; dwCallbackInstance = (DWORD) hCallback; dwParam1 = (DWORD) idButtonOrLamp; dwParam2 = (DWORD) ButtonMode; dwParam3 = (DWORD) ButtonState; Parameters hPhone A handle to the phone device. dwCallbackInstance The callback instance that is provided when the phone device for this application is opened. dwParam1 The button/lamp identifier of the button that was pressed. Button identifiers zero through 11 always represent the KEYPAD buttons, with ‘0’ being button identifier zero, ‘1’ being button identifier 1 (and so on through button identifier 9), and with ‘*’ being button identifier 10, and ‘#’ being button identifier 11. Find additional information about a button identifier with phoneGetDevCaps, on page 276. dwParam2 The button mode of the button. The button mode for each button ID gets listed as shown in the table below. The TAPI service provider cannot detect button down or button up state changes. To conform to the TAPI specification, two messages are sent to simulate a down state followed by an up state in dwparam3. This parameter uses the following PHONEBUTTONMODE_constants: • PHONEBUTTONMODE_CALL -The button is assigned to a call appearance. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 291 Basic TAPI Implementation PHONE_BUTTON