/mcpIf the dwParm2 indicates option change with the value DoNotDisturb_OPTION_CHANGED, this parameter can comprise one of the following enum values: enum CiscoDoNotDisturbOption { DoNotDisturbOption_NONE = 0, DoNotDisturbOption_RINGEROFF = 1, DoNotDisturbOption_REJECT = 2 }; Cisco Phone Device-Specific Extensions The following table lists and describes the subclasses of CiscoPhoneDevSpecific. Table 24: Cisco Phone Device-Specific TAPI Functions Synopsis Cisco Functions The CCiscoPhoneDevSpecific class represents the parent class to the following classes. CCiscoPhoneDevSpecific, on page 395 Allows the application to send the Device Specific XSI data through CTI. Device Data PassThrough, on page 397 Allows the application to acquire any CTI-controllable device that can get opened later in superprovider mode. Explicit Acquire, on page 366 Allows the application to deacquire a CTI-controllable device that was explicitly acquired. Explicit De-Acquire, on page 366 Allows the application to request secure RTP indicator for calls on the device. Request Call RTP Snapshot, on page 401 Allows the application to set status bit map to enable specific DEVICE_DEVSPECIFIC messages to be sent to the application. Set Status Msgs, on page 398 Sets the Unicode display on the phone. Set Unicode Display, on page 399 CCiscoPhoneDevSpecific This section provides information on how to perform Cisco TAPI-specific functions with the CCiscoPhoneDevSpecific class, which represents the parent class to all the following classes. Be aware that this virtual class is provided for informational purposes only. Note CCiscoPhoneDevSpecific| +--CCiscoPhoneDevSpecificDataPassThrough | +--CCiscoPhoneDevSpecificSetStatusMsgs Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 395 Cisco Device-Specific Extensions Cisco Phone Device-Specific Extensions
