McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 328

↗ View in doc context
page
328
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::338

PHONE_REPLY The TAPI PHONE_REPLY message gets sent to an application to report the results of function call that completed asynchronously. Function Details PHONE_REPLY hPhone = (HPHONE) 0; dwCallbackInstance = (DWORD) hCallback; dwParam1 = (DWORD) idRequest; dwParam2 = (DWORD) Status; dwParam3 = (DWORD) 0; Parameters hPhone Not used. dwCallbackInstance Returns the application callback instance. dwParam1 The request identifier for which this is the reply. dwParam2 The success or error indication. The application should cast this parameter into a LONG. Zero indicates success; a negative number indicates an error. dwParam3 Not used. PHONE_STATE TAPI sends the PHONE_STATE message to an application whenever the status of a phone device changes. Function Details PHONE_STATE hPhone = (HPHONE) hPhoneDevice; dwCallbackInstance = (DWORD) hCallback; dwParam1 = (DWORD) PhoneState; dwParam2 = (DWORD) PhoneStateDetails; dwParam3 = (DWORD) 0; Parameters hPhone A handle to the phone device. dwCallbackInstance The callback instance that is provided when the phone device is opened for this application. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 296 Basic TAPI Implementation PHONE_REPLY

Page 328 content