McDewey

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

Page 430

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

DWORD m_DeviceData This character buffer contains the XML data that is to be sent to phone device. Be aware that MAX_DEVICE_DATA_PASSTHROUGH_SIZE = 2000. Note A phone can pass data to an application and it can get retrieved by using PhoneGetStatus (PHONESTATUS:devSpecificData). See PHONESTATUS description for further details. Set Status Msgs PhoneDevSpecificSetStatusMsgs allows the application to set status bit map to enable specific DEVICE_DEVSPECIFIC messages to be sent to the application. The application must open a TAPI phone device with minimum extension version 0x00030000 to use this feature. Be aware that this extension requires applications to negotiate extension version as 0x00030000. Note CCiscoPhoneDevSpecific | +--CCiscoPhoneDevSpecificSetStatusMsgs Class Detail class CCiscoPhoneDevSpecificSetStatusMsgs:public CCiscoPhoneDevSpecific{ public: CCiscoPhoneDevSpecificSetStatusMsgs() : CCiscoPhoneDevSpecific (CPDST_SET_DEVICE_STATUS_MESSAGES) {;} virtual ~CCiscoPhoneDevSpecificSetStatusMsgs() {;} DWORD m_DevSpecificStatusMsgFlags ; // PHONE_DEVSPECIFIC // subtract virtual function table pointer virtual DWORD dwSize(void) const {return (sizeof (*this) -4) ; } } ; Parameters DWORD m_MsgType equals CPDST_SET_DEVICE_STATUS_MESSAGES. DWORD m_DevSpecificStatusMsgFlags Bit map of PHONE_DEVSPECIFIC event flag const DWORD DEVSPECIFIC_DEVICE_DATA_PASSTHROUGH_EVENT = 0x00000001; const DWORD DEVSPECIFIC_DEVICE_SOFTKEY_PRESSED_EVENT = 0x00000002; const DWORD DEVSPECIFIC_DEVICE_STATE_EVENT = 0x00000004; const DWORD DEVSPECIFIC_DEVICE_PROPERTY_CHANGED_EVENT = 0x00000008; Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 398 Cisco Device-Specific Extensions Set Status Msgs

Image 1 from page 430

Page 430 content