Cisco Systems OL-14619-01 manual Unified Messaging with Customer-Provided Infrastructure

Page 34

Chapter 4 Designing a Cisco Unity System with Exchange as the Message Store

Deployment Models

Unified Messaging with Customer-Provided Infrastructure

Revised May 6, 2008

For the Cisco Unity Unified Messaging configurations, Cisco Unity installs into an existing infrastructure, is a part of the messaging environment, services subscribers who are homed on existing Exchange e-mail servers, and uses existing DC/GCs. This reduces administrative overhead when compared with maintaining a Cisco Unity Voice Messaging solution or maintaining a legacy voice messaging system. With Unified Messaging, only one messaging infrastructure is required to support both e-mail and voice messaging. The customer is responsible for maintaining the DC/GCs, Exchange servers, and DNS.

Each Cisco Unity server can be connected to a circuit-switched phone system, to Cisco Unified Communications Manager, or to both. If the phone system has ports available, you can connect more than one Cisco Unity server to each phone system.

When you are setting up two or more Cisco Unity servers in the same Active Directory forest, the Cisco Unity servers can be networked by using Cisco Unity Digital Networking.

Mixed Unified Messaging and Voice Messaging with Customer-Provided Infrastructure

When mixing Unified Messaging and Voice Messaging deployment models, the Unified Messaging portion of the deployment is the same as a Unified Messaging deployment without the Voice Messaging subscribers.

The Voice Messaging subscribers require separate accounts and mailboxes:

Each Voice Messaging subscriber requires a separate Active Directory user account in the existing forest.

Each Voice Messaging subscriber requires a separate Exchange mailbox that holds only Cisco Unity voice messages. The mailbox can be stored on existing Exchange servers or can be stored on separate, dedicated Exchange servers that home only Cisco Unity voice messages. If the mailboxes are stored on existing Exchange servers, the customer is responsible for support for the servers. If the mailboxes are stored on Exchange servers that are dedicated to Cisco Unity voice messages, Cisco will support the Exchange servers.

If the Voice Messaging subscribers are homed on one or more dedicated Exchange servers on which the Voice Mail Run-time Edition of Microsoft Exchange was installed, those subscribers do not need Microsoft Client Access Licenses (CALs). Unified Messaging subscribers all need CALs.

For more information on the Unified Messaging portion of a mixed system, see the “Unified Messaging with Customer-Provided Infrastructure” section on page 4-2.

For more information on the Voice Messaging portion of a mixed system, see the “Voice Messaging with Customer-Provided Infrastructure” section on page 4-3.

Voice Messaging with Cisco-Provided, Dedicated Infrastructure

Revised May 6, 2008

In this deployment model:

Each Voice Messaging subscriber requires a separate Active Directory user account in a dedicated forest.

Design Guide for Cisco Unity Release 5.x

4-2

OL-14619-01

 

 

Image 34
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 Voice Messages Are Stored in Domino or Exchange Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System 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 MessagesAudio Codec TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems 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 PermissionsCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Message Routing Client Access LicensesCisco Unity and the Domino Address Book Backing Up and Restoring DataUnified Messaging, No Domino Cluster Unified Messaging ConfigurationsServers Requirements and Recommendations Criteria for a Supported Configuration Voice Messaging ConfigurationUnified Messaging, Domino Cluster Deploying Cisco Unity for Lotus Domino Deployment Tasks for Unified Messaging Configurations Administrative Access and ControlNetwork Services Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow an Integration Works Integration with Cisco Unified Communications Manager Lines and Cables to Make Physical ConnectionsDigital Integration with Digital Pimg Units 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 Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP Compliance 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 SystemsReasons to Use Alternate Extensions Optional Integration FeaturesAlternate 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