/mcpmakes this possible. The CER application that initiates the emergency call sets FeaturePriority as FeaturePriority_Emergency. The application sets the feature priority only for emergency calls. In the case of normal calls, applications either do not set the feature priority at all or set it to FeaturePriority_Normal. Applications do not set FeaturePriority_Emergency in case of normal calls. When initiating feature calls such as intercom, applications must specify FEATUREPRIORITY_URGENT. The connect() API on CiscoCall does not support the FeaturePriority parameter. Note The application receives an exception if it tries to perform a getDNDStatus(), setDNDStatus(), or getDNDOption() before the device is in service. A Post condition is added to DND to handle a DB update failure or device out-of-service situations if they occur after the setDNDStatus() request is sent. If a DB update failure or device out-of-service condition occurs after the setDNDStatus() request is sent, setDNDStatus() delivers a CiscoTermDNDStatusChangedEv to the application. If this event is not received, a post-condition time-out occurs, and the following exception is thrown: could not meet post conditions of setDNDStatus(). Backward Compatibility This feature is backward compatible. Applications recognize new events if this feature is configured. You can filter the new events through the TerminalEventFilter interface (CiscoTermEvFilter). By default, this filter is disabled and the system does not deliver the new events. For additional information, see the following topics: • CiscoTerminal, on page 617 • CiscoTermDNDStatusChangedEv, on page 610 • CiscoTermEvFilter, on page 614 • CiscoCall, on page 332 • CiscoConnection, on page 386 • CiscoRouteSession, on page 523 • CiscoTermInServiceEv, on page 644 Do Not Disturb-Reject Do Not Disturb–Reject (DND–R) is an enhancement to the existing DND feature. Cisco Unified Communications Manager and JTAPI previously supported only the Ringer off DND. The user can reject calls with DND–Reject. You can set DND–R from the phone configuration window or the phone profile configuration window in Cisco Unified Communications Manager Administration. When DND–R is enabled, the call is not presented to the terminal that has Call Reject enabled. There is no audible or visual indication of incoming calls on that end point. To enable DND–R, set the DND Status as true and the DND option to Call Reject. FeaturePriority overrides DND. It can have any of the following values: • 1: Normal Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 84 Features Supported by Cisco Unified JTAPI Do Not Disturb-Reject