Cisco Systems OL-14619-01 manual Option Considerations

Page 68

Chapter 6 Integrating Cisco Unity with the Phone System

Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP)

Integrating Cisco Unity with Multiple Cisco Unified Communications Manager Clusters

To integrate Cisco Unity with more than one Cisco Unified CM cluster, you can just re-run the

Cisco Unity Telephony Integration Manager, or UTIM. Note the options and considerations detailed in Table 6-2.

Table 6-2 Options and Considerations for Integrating with Multiple Cisco Unified

Communications Manager Clusters

Option

Considerations

 

 

 

Create a new Cisco

•

This is the recommended method.

Unified CM integration for

•

Each Cisco Unified CM integration handles the MWIs for the

each new Cisco Unified CM

 

cluster. Dedicated MWI ports for each Cisco Unified CM cluster is

cluster

 

 

necessary only if the Cisco Unified CM integration has multiple

 

 

 

 

clusters in UTIM.

 

• Cisco Unity sends each MWI request directly to the Cisco

 

 

Unified CM cluster on which the subscribers is homed.

 

• Multiple Cisco Unified CM integrations can be used with multiple

 

 

UTIM clusters on a Cisco Unity server.

 

 

 

Add a cluster in UTIM to an

•

You must assign at least one MWI port dedicated to each Cisco

existing Cisco Unified CM

 

Unified CM cluster that you add.

integration for each new

•

The first cluster in UTIM will handle all calls and direct them to the

Cisco Unified CM cluster

 

Cisco Unified CM cluster on which the subscriber is homed.

 

 

 

• You can create an unlimited number of clusters in UTIM to a Cisco

 

 

Unified CM integration.

 

• Multiple UTIM clusters can be used with multiple Cisco

 

 

Unified CM integrations on the Cisco Unity server.

 

 

 

Within a cluster, it is important to identify the backup (secondary) Cisco Unified CM servers so that Cisco Unity can connect to it if the primary Cisco Unified CM server becomes unavailable.

Cisco Unified Communications Manager Authentication and Encryption for Cisco Unity Voice Messaging Ports (SCCP Integrations Only)

A potential point of vulnerability for a Cisco Unity system is the connection between Cisco Unity and Cisco Unified Communications Manager. Possible threats include:

•Man-in-the-middle attacks, in which an attacker intercepts and changes the data flowing between Cisco Unified CM and Cisco Unity voice messaging ports.

•Network traffic sniffing, in which an attacker captures phone conversations and signaling information that flow between Cisco Unified CM, the Cisco Unity voice messaging ports, and IP phones that are managed by Cisco Unified CM).

•Changing the call signaling between the Cisco Unity voice messaging ports and Cisco Unified CM.

•Changing the media stream between Cisco Unity voice messaging ports and endpoints, for example, phones or gateways.

 

Design Guide for Cisco Unity Release 5.x

6-12

OL-14619-01

Page 67 Page 69
Image 68
Page 67 Page 69
Contents Design Guide for Cisco Unity Americas HeadquartersDesign Guide for Cisco Unity Release N T E N T S Workstations Authentication Centralized Voice Messaging Configuration Viii Audience Document ConventionsSupport Policy for Optional Third-Party Software Cisco Product Security Overview Xii Product Area Design or Feature Documentation Design Guide OverviewDesign Guide for Cisco Unity Bridge at Page Design Guide Overview Design Guide for Cisco Unity Release Cisco Unity Concepts How Cisco Unity WorksUnified Messaging Voice MessagingHardware Components of a Cisco Unity System One or More Cisco Unity Servers Cisco Unity Supported Platforms List atNetwork Connection Optional for Some Configurations Where Cisco Unity Stores Data Software Components of a Cisco Unity SystemVoice Messages Are Stored in Domino or Exchange DominoExchange Enabling Cisco Unity Servers to Communicate with One Another Networking Guide for Cisco Unity at Some Configuration Settings Are Stored in the Registry Name Resolution Availability of Network ResourcesDomain Controller Access and Availability Availability of Message Store ServersUsing Firewalls with Cisco Unity Sizing and Scaling Cisco Unity ServersStorage Capacity for Voice Messages Number of Voice PortsAudio Codecs How Codecs Affect the File Size of Voice MessagesTTS, TTY, Pocket PCs, and Hand-Held Computers Interoperability Among Multiple Voice-Messaging SystemsAudio Codec Quality RatingDeployment Models Unified Messaging with Customer-Provided Infrastructure Voice Messaging with Customer-Provided Infrastructure Multi-Site WAN with Distributed MessagingPhysical Placement and Network Infrastructure Considerations for Customer-Provided Infrastructure Active Directory ConsiderationsDesign Guide for Cisco Unity Release Exchange Considerations All Versions Exchange Considerations That Apply Only Exchange Considerations for Cisco-Provided, Dedicated Infrastructure OL-14619-01 Overview of Cisco Unity with Domino and Notes Maximum Number of Cisco Unity Subscribers Domino Address Book TerminologyChanges That csAdmin Makes to the Domino Address Book Element NameChanges That csClient Makes to the Mail File Server Placement Windows Domains and Domino DomainsAuthentication Active Directory Accounts and PermissionsDomino Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Client Access Licenses Cisco Unity and the Domino Address BookMessage Routing Backing Up and Restoring DataServers Requirements and Recommendations Unified Messaging ConfigurationsUnified Messaging, No Domino Cluster Unified Messaging, Domino Cluster Voice Messaging ConfigurationCriteria for a Supported Configuration Deploying Cisco Unity for Lotus Domino Administrative Access and Control Network ServicesDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow an Integration Works Digital Integration with Digital Pimg Units Lines and Cables to Make Physical ConnectionsIntegration with Cisco Unified Communications Manager Dtmf Integration with Analog Pimg Units Timg Integration LAN/WANDtmf Integration with Voice Cards Serial Integration with Voice CardsSettings in the Phone System and in Cisco Unity Connections for a Serial Integration by Using Voice CardsCall Control General Integration Issues Feature Sccp SIPIntegrating Cisco Unity with the Phone System Option Considerations Cisco Unified Communications Manager Security Features DescriptionDescription When Data Is Encrypted Setting EffectSettings for Individual Voice Messaging Ports Disabling and Re-Enabling SecurityPacketization Sccp Integrations Only Sccp SIP Cisco 11 Cisco Unified Communications Manager Fallback with Pstn Cisco Unity to a branch office will fail Integrating by Using SIP SIP Compliance Supported SIP IntegrationsCisco Unity Failover with SIP Trunks Description of Pimg Integrations Dtmf Integration with Analog Pimg Units Description of Timg Integrations Setup and Configuration Firmware Updates Serial IntegrationsIncreasing Port Capacity Cisco Unity FailoverCisco Unity Failback Multiple Integration Support/Branch Office ConsolidationIntegrating with Multiple Phone Systems Using Sccp Phone Systems with Other Integrations Requirements for Integrations with Multiple Phone SystemsOptional Integration Features Alternate ExtensionsReasons to Use Alternate Extensions How Alternate Extensions WorkAlternate MWIs MWIs for Extensions on a Non-Integrated Phone SystemCentralized Voice Messaging OL-14619-01 OL-14619-01 Cisco Unity Failover and Standby Redundancy FailoverStandby Redundancy Cisco Unity Failover and Standby Redundancy Cisco Unity Failover and Standby Redundancy Diagram of a Standby Redundancy Configuration Pstn WANOL-14619-01 Voice-Recognition Access to Cisco Unity OL-14619-01 Migrating to Cisco Unity from Another Voice-Messaging System Migrating to Cisco Unity from Another Voice-Messaging System D E IN-2 IN-3 IN-4
Top Page Image Contents