McDewey

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

Page 424

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

Be aware that this virtual class is provided for informational purposes only. Note CCiscoLineDevSpecificFeature Header File The file CiscoLineDevSpecific.h contains the corresponding constant, structure, and class definitions for the Cisco lineDevSpecificFeature extension classes. Class Detail class CCiscoLineDevSpecificFeature { public: CCicsoLineDevSpecificFeature(const DWORD msgType): m_MsgType(msgType) {;} virtual ~ CCicsoLineDevSpecificFeature() {;} DWORD GetMsgType(void) const {return m_MsgType;} void* lpParams(void) const {return (void*)&m_MsgType;} virtual DWORD dwSize(void) const = 0; private: DWORD m_MsgType; }; Functions lpParms() Function that can be used to obtain a pointer to the parameter block dwSize() Function that returns size of the parameter block area Parameter m_MsgType Specifies the type of message. The parameter value uniquely identifies the feature to invoke on the device. The PHONEBUTTONFUNCTION_ TAPI_Constants definition lists the valid feature identifiers. Currently, the only recognized value specifies PHONEBUTTONFUNCTION_DONOTDISTURB (0x0000001A). Each subclass of CCiscoLineDevSpecificFeature includes a unique value that is assigned to the m_MsgType parameter. Subclasses Each subclass of CCiscoLineDevSpecificFeature carries a unique value that is assigned to the m_MsgType parameter. If you are using C instead of C++, this represents the first parameter in the structure. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 392 Cisco Device-Specific Extensions Header File

Image 1 from page 424

Page 424 content