McDewey

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

Page 432

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

If a Super-provider application needs to open any CTI-controllable device on the Cisco Unified Communications Manager system, the application should explicitly acquire that device by using the preceding interface. After successful response, it can open the device as usual. Be aware that this extension is only available if extension version 0x00070000 or higher is negotiated. Note CCiscoPhoneDevSpecific | +--CCiscoPhoneDevSpecificAcquire Class Details class CCiscoPhoneDevSpecific Acquire : public CCiscoPhoneDevSpecific{ public: CCiscoPhoneDevSpecificAcquire () : CCiscoPhoneDevSpecific (CPDST_ACQUIRE) {} virtual ~ CCiscoPhoneDevSpecificAcquire () {} char m_DeviceName[16]; virtual DWORD dwSize(void) const {return sizeof(*this)-4;} // subtract out the virtual function table pointer }; Parameters DWORD m_MsgType Equals CPDST_ACQUIRE char m_DeviceName[16] The DeviceName that needs to be explicitly acquired. Explicit Deacquire The CCiscoPhoneDevSpecificDeacquire class gets used to explicitly de-acquire an explicitly acquired device. If a SuperProvider application explicitly acquired any CTI-controllable device on the Unified Communications Manager system, the application should explicitly de-acquire that device by using this interface. Be aware that this extension is only available if extension version 0x00070000 or higher is negotiated. Note CCiscoPhoneDevSpecific | +--CCiscoPhoneDevSpecificDeacquire Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 400 Cisco Device-Specific Extensions Class Details

Image 1 from page 432

Page 432 diagram