CiscoJTAPI delivers a new event CiscoAddrMonitoringTerminatedEv when the monitoring session is torn down. This event is delivered to the Supervisor who had started the secured monitoring session but had dropped off from the monitoring call. The APIs getCiscoAddrMonitoringTerminatedEvFilter() and setCiscoAddrMonitoringTerminatedEvFilter() have been added to the interface CiscoAddrEvFilter for applications to get or set the filter value for the CiscoAddrMonitoringTerminatedEv. By default, the filter is set to True and the event is delivered. To stop receiving this event, applications must set this filter to False. As before, When a monitoring call (call used by monitor initiator) is conferenced, the final call may not have any connection to monitor target. When monitor initiator conferences another party to a monitoring call, both parties can to listen to the audio between monitor target and caller. Secured Monitoring Interface Changes CiscoJtapiException, on page 416, CiscoTermConnMonitorInitiatorInfoEv, on page 587, CiscoTermConnMonitorTargetInfoEv, on page 589, CiscoAddrMonitorTerminatedEv, on page 288, CiscoAddrEvFilter, on page 305 Message Sequences Secured Monitoring Use Cases, on page 1282, Secured Recording, on page 1446 Backward Compatibility This feature is backward compatible. Single Sign-On The Single Sign-On feature allows Cisco JTAPI applications to use the single sign-on ticket to authenticate instead of a user ID and password. Applications fetch the service ticket for the OpenSSO server from the active directory and then pass the ticket to Cisco JTAPI in the string used in the getProivder(String str) API. Applications can set the single sign-on ticket as ssoticket = "ssotokenfromat". Only end users can use this feature. Applications using this feature need not specify the user ID and password in the getProvider string. If an application is used by an end user and has the Standard CTI Secure Connection role enabled, then a user ID is required in the provider string. No password is required. This solution is designed around an active directory with a Kerberos environment to achieve Windows desktop Single Sign-On. If an active directory with a Kerberos environment is unavailable, then an alternate equivalent setup is available, which includes a KDC, an authentication server, and a domain controller. Sample Code String ssoticket

getSSOticket(); //application implementation String providerString

cucmserver + ssoticket +";"; JtapiPeer peer

JtapiPeerFactory.getJtapiPeer ( null ); try { Provider provider

peer.getProvider (providerString); } catch (Exception exp ) Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 170 Features Supported by Cisco Unified JTAPI Single Sign-On