/mcpThe Local Universal Unique Identifer (localUUID) for a CiscoConnection in a CiscoCall is generated in the peerUUID on the other side in the CiscoCall and vice versa. This relation is assured for a basic two party call and is retained through the following features: • Redirect • Call Forward • Transfer • Hold/Resume If the Cisco call is shared between multiple devices, the CiscoConnection.getPeerUUID(null) on the calling side will return the UUID of any of the available terminals while the CiscoConnection on the called side is in CiscoConnection.ALERTING state. Once the call is answered CiscoConnection.getPeerUUID(null) on the calling side will return the uuid of the active TerminalConnection. Interface Changes CiscoConnection, on page 386. Message Sequences End to End Session ID for Calls, on page 981 Backward Compatibility This feature is backward compatible. FIPS Compliance This feature allows Unified Communications Manager to operate in Federal Information Processing Standard (FIPS) mode. FIPS specifies a minimum security level for cryptographic functions, limitations on how data is stored, and which algorithms are allowed to be used to encrypt sensitive information. These strictly defined requirements are important to government agencies, hospitals, and other customers who're interested in a higher level of security. To enable FIPS Compliance, Unified Communications Manager applications must request this mode when they download certificates with JTAPI and open a provider. When operating in FIPS, Unified Communications Manager experiences minimal performance loss. You can only witness this loss during the certificate downloads and opening of a Cisco Unified Communications Manager JTAPI provider. FIPS does not affect anything when the application is running. Starting from Release 8.6(1), JTAPI can be configured as FIPS-compliant. Important Notes In FIPS, there are two distinct “cryptographic entities”: The JTAPI application and the Unified CM server (or cluster). The FIPS compliance of one does not, in any way, affect the other. Setting JTAPI to run in FIPS compliance encrypts the client-side certificates with a FIPS-compliant algorithm, and connect using only approved SSL/TLS algorithms. It will not make the Unified CM server or cluster secure or FIPS-compliant. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 95 Features Supported by Cisco Unified JTAPI FIPS Compliance