/mcpParameters hPhoneApp A handle by which the application is registered with TAPI. dwDeviceID The phone device to be opened. lphPhone A pointer to an HPHONE handle that identifies the open phone device. Use this handle to identify the device when invoking other phone control functions. dwAPIVersion The API version number under which the application and telephony API agreed to operate. Obtain this number from phoneNegotiateAPIVersion. dwExtVersion The extension version number under which the application and the service provider agree to operate. This number is zero if the application does not use any extensions. Obtain this number from phoneNegotiateExtVersion. dwCallbackInstance User instance data that is passed back to the application with each message. The telephony API does not interpret this parameter. dwPrivilege The privilege requested. The dwPrivilege parameter can have only one bit set. This parameter uses the following PHONEPRIVILEGE_constants: • PHONEPRIVILEGE_MONITOR -An application that opens a phone device with this privilege gets informed about events and state changes that occur on the phone. The application cannot invoke any operations on the phone device that would change its state. • PHONEPRIVILEGE_OWNER -An application that opens a phone device in this mode can change the state of the lamps, ringer, display, and hookswitch devices of the phone. Having owner privilege to a phone device automatically includes monitor privilege as well. phoneSetDisplay The phoneSetDisplay function causes the specified string to display on the specified open phone device. Prior to Release 4.0, Cisco Unified Communications Manager messages that were passed to the phone would automatically overwrite any messages sent to the phone by using phoneSetDisplay(). In Cisco Unified Communications Manager 4.0, the message sent to the phone in the phoneSetDisplay() API remains on the phone until the phone is rebooted. If the application wants to clear the text from the display and see the Cisco Unified Communications Manager messages again, a NULL string, not spaces, should be passed in the phoneSetDisplay() API. In other words, the lpsDisplay parameter should be NULL and the dwSize should be set to 0. Note Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 287 Basic TAPI Implementation phoneSetDisplay