/mcpconfiguration. Applications can use this interface to determine whether they have sufficient capability to invoke the createTerminal(terminalName) interface. If the application does not have sufficient capability and this interface is invoked, JTAPI throws a PrivilegeViolationException. If the application provides a terminalName that does not exist in the Cisco Unified Communications Manager cluster, JTAPI throws a InvalidArgumentException. Superprovider and Change Notification Superprovider enhancements for JTAPI in this release consist primarily of the following changes. When the “Superprovider privilege” gets disabled from Cisco Unified Communications Manager Administration after a provider opens, JTAPI gets notified through a CTI Change Notification Event and cleans up all the devices that it has opened that are not in its control list. JTAPI informs applications about the change using the “CiscoProviderCapabilityChangedEvent.” This new event gets issued when the flag changes and indicates whether the flag has been enabled or disabled. When a device that is not in the control list is opened in the Superprovider mode, then moved to the control list, JTAPI moves the device into its control list. • When a normal application receives a “CiscoProviderCapabilityChangedEvent” with the flag set, it means the Superprovider privilege has been granted to it, and it can start acquiring devices not in its control list. • When a Superprovider application receives a “CiscoProviderCapabilityChangedEvent” with the Superprovider flag not set, it means that the Superprovider privilege has been removed for it. The following sequence of events then occurs: • Applications receive a Provider OOS event and all devices acquired/opened by it are closed. • Applications receive a CiscoTermRemovedEv for all devices not in the control list that have been acquired or opened. • Applications receive a Provider inService event when JTAPI succeeds in reconnecting to CTI as a normal user. • Applications receive device and line information. • Applications receive CiscoTermCreatedEv for all controlled devices that were open before the provider went OOS. • JTAPI notifies applications by using the “CiscoProviderCapabilityChangedEvent” when the “park DN monitoring” flag is changed from Cisco Unified Communications Manager Administration. • When an application receives this event with the flag set, it does a register feature for the controlling park DN. • When an application receives this event with the flag not set, JTAPI again informs applications by using a “CiscoProviderCapabilityChangedEvent” and closes all the park DN addresses. • JTAPI notifies applications by using the CiscoProviderCapabilityChangedEvent” when the “change calling party number” flag is changed from Cisco Unified Communications Manager Administration. • When an application receives this event with the flag set, it can change the calling party number. • When an application receives this event with the flag not set, it cannot change the calling party number. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 181 Features Supported by Cisco Unified JTAPI Superprovider and Change Notification