/mcpTAPI does not support TLS 1.3. Note Support for RSHA12 Algorithm Prior to the11.5 release, Cisco TSP had hardcoded the digest algorithm used for validating the signature of CTLFile to SHA1. From 11.5 release onwards, Cisco TSP is enhanced to use the digest algorithm based on DigestAlgorithm Tag mentioned in CTLFile. This way Cisco TSP validates CTLFile signed with SHA1 or SHA512. Backward Compatibility Issues: Cisco TSP versions prior to 11.5 will not be able to validate CTLFile signed using SHA512 if the parameter: “TFTP File Signature Algorithm Required Field” (System-> Enterprise Parameters Configuration) in Cisco Unified Communications Manager is set to RSASHA512. The secure connection fails as CiscoTSP supports only SHA1 and not SHA512 algorithm. Secured Monitoring and Recording This feature enhances the ability to monitor or record calls in a secure environment. In Unified Communications Manager (Cisco Unified CM), Release 8.0(1), Cisco Unified CM software has been enhanced to enable call monitoring and recording in a secure environment. So, secured calls can be monitored and recorded. The recording and monitoring session is created in a secure mode only when the Supervisor/Recording Device and the Agent has secure capabilities. Recording/Monitoring request is successful only when the Supervisor/Recording Device has higher than or meets the security capabilities of the Agent. TransactionID, which is unique for reach monitoring session, is exposed to the application in Call Attribute information, DevSpecific part of Call Info for the call on supervisor and agent. If the Silent Monitoring session is toned down when the Supervisor Security capabilities do not meet or exceed the capabilities of the agent, LINE_DEVSPECIFIC event is delivered with Param1 = SLDSMT_MONITORING_TERMINATED indicating the Monitoring Terminated event and Param2 = TransactionID of the call that is terminated. To receive the Monitoring Terminated event, the DEVSPECIFIC_SILENT_MONITORING_TERMINATED message flag must be set in applications by using the lineDevSpecific SLDST_SET_STATUS_MESSAGES request. The application has to determine the monitoring session to be terminated based on the TransactionID that TSP exposes in LINE_DEVSPECIFIC Event for the Monitoring Session Terminated Event: • Monitoring Terminated event is delivered to the original supervisor that initiated the Monitoring session and is longer present in monitoring the call. • Recording: Cisco Unified CM does not support recording on Authenticated devices and also when the Recording device is authenticated. • If the application monitors the Customer, Agent and Supervisor lines after Monitoring/Recording sessions start, CallReason will be LINECALLREASON_UNKNOWN for direct calls from the customer to the Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 92 Features Supported by TSP Support for RSHA12 Algorithm