McDewey

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

Page 327

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

Parameters hPhone Not used. dwCallbackInstance Not used. dwParam1 The dwDeviceID of the newly created device. dwParam2 Not used. dwParam3 Not used. PHONE_REMOVE The PHONE_REMOVE message gets sent to inform an application of the removal (deletion from the system) of a phone device. Generally, this method is not used for temporary removals, such as extraction of PCMCIA devices, but only for permanent removals in which the service provider would no longer report the device, if TAPI were reinitialized. CTI Manager cluster support, extension mobility, change notification, and user deletion from the directory can generate PHONE_REMOVE events. Note Function Details PHONE_REMOVE dwDevice = (DWORD) 0; dwCallbackInstance = (DWORD) 0; dwParam1 = (DWORD) dwDeviceID; dwParam2 = (DWORD) 0; dwParam3 = (DWORD) 0; Parameters dwDevice Reserved. Set to zero. dwCallbackInstance Reserved. Set to zero. dwParam1 Identifier of the phone device that was removed. dwParam2 Reserved. Set to zero. dwParam3 Reserved. Set to zero. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 295 Basic TAPI Implementation PHONE_REMOVE

Image 1 from page 327

Page 327 content