/mcpReturns a CiscoMonitorInitiatorInfo that exposes the terminal name and address of the monitor target. Two new error codes notify applications about monitoring failures: • CTIERR_PRIMARY_CALL_INVALID is returned by CiscoException.getErrorCode() for exceptions that occur when a monitoring request fails due to the call going idle or getting transferred. • CTIERR_PRIMARY_CALL_STATE_INVALID is returned when the monitoring request fails due to the call transitioning to a different state where monitoring cannot be invoked. This release introduces a new AddressType, MONITORING_TARGET. JTAPI creates a connection on an address of this type for a monitoring target address; CiscoAddress.getType() returns this value. Backward Compatibility This feature is backward compatible. Applications will not see any new events unless this feature is configured and used on one of the application-controlled addresses. The administrator can enable this feature by adding Standard CTI Allow Call Monitor user groups. For detailed information about these interface changes, see the following topics: • CiscoJtapiException, on page 416 • Related Documentation, on page 289 • CiscoCall, on page 332 • CiscoMediaTerminal, on page 454 • CiscoMonitorTargetInfo, on page 466 • CiscoMonitorInitiatorInfo, on page 465 • CiscoProvider, on page 492 • CiscoProviderCapabilities, on page 504 • CiscoProviderCapabilityChangedEv, on page 506 • CiscoRecorderInfo, on page 511 • CiscoTerminalConnection, on page 636 • CiscoTermConnMonitorInitiatorInfoEv, on page 587 • CiscoTermConnMonitorTargetInfoEv, on page 589 Secured Monitoring With this enhancement a supervisor can monitor a secure call only if its device security capability is same as or more than that of the agent. If the security capability of the monitor initiator's device is less than that of the target, the request for monitor fails. Cisco JTAPI throws a PriviledgeViolationException with CTIERR_SECURITY_CAPABILITY_MISMATCH, when the monitoring request is rejected due to the supervisor not meeting the security capabilities of the agent. A new API getTransactionID() is added to CiscoTermConnMonitorInitiatorInfoEv and CiscoTermConnMonitorTargetInfoEv. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 169 Features Supported by Cisco Unified JTAPI Silent Monitoring