McDewey

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

Page 398

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

DWORD m_SRTP_Fixed_Element_Size Should be size of DWORD, it should be always 4. DWORD m_SRTPAlgorithm_Offset Offset from the beginning of the message buffer. This is offset where you start put algorithm ID array. Be aware that the dwSize should be recalculated based on size of the structure, m_SRTPAlgorithmCount and m_SRTP_Fixed_Element_Size. Note Explicit Acquire The CCiscoLineDevSpecificAcquire class gets used to explicitly acquire any CTI controllable device. If a Superprovider 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 above 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 CCiscoLineDevSpecific | +--CCiscoLineDevSpecificAcquire Class Details class CCiscoLineDevSpecificAcquire : public CCiscoLineDevSpecific{ public: CCiscoLineDevSpecificAcquire () : CCiscoLineDevSpecific(SLDST_ACQUIRE) {} virtual ~ CCiscoLineDevSpecificAcquire () {} 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 SLDST_ACQUIRE m_DeviceName[16] The DeviceName that needs to be explicitly acquired. Explicit De-Acquire The CCiscoLineDevSpecificDeacquire class is used to explicitly de-acquire the explicitly acquired device. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 366 Cisco Device-Specific Extensions Explicit Acquire

Image 1 from page 398

Page 398 content