- Integration Overview
- Planning the Voice Messaging Ports
- Setting Up a Cisco Unified Communications Manager SCCP Integration
- Configuring Voice Messaging Ports Configuration for a Unity Connection Cluster
- Testing the Integration
- Changing the Number of Voice Messaging Ports
- Cisco Unified Communications Manager Authentication and Encryption
- Adding Cisco Unified Communications Manager Express to a Cisco Unified Communications Manager Integration
- Index
Cisco Unified Communications Manager Authentication and Encryption
Cisco Unified Communications Manager Authentication and Encryption
Introduction
A potential point of vulnerability for a Cisco Unity Connection system is the connection between Unity Connection and Cisco Unified Communications Manager. Possible threats include:
Man-in-the-middle attacks (a process in which an attacker observes and modifies the information flow between Cisco Unified CM and the Unity Connection voice messaging ports)
Network traffic sniffing (a process in which an attacker uses software to capture phone conversations and signaling information that flow between Cisco Unified CM, the Cisco Unity Connection voice messaging ports, and IP phones that are managed by Cisco Unified CM)
Modification of call signaling between the Unity Connection voice messaging ports and Cisco Unified CM
Modification of the media stream between the Unity Connection voice messaging ports and the endpoint (for example, a phone or gateway)
Identity theft of the Unity Connection voice messaging port (a process in which a non-Unity Connection device presents itself to Cisco Unified CM as a Unity Connection voice messaging port)
Identity theft of the Cisco Unified CM server (a process in which a non-Cisco Unified CM server presents itself to Unity Connection voice messaging ports as a Cisco Unified CM server)
Cisco Unified CM Security Features
Cisco Unified CM can secure the connection with Unity Connection against these threats. The Cisco Unified CM security features are used by Unity Connection as described in Table 7-1.