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

Page 35

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

Deployment Models

Each Voice Messaging subscriber requires a separate Exchange mailbox that holds only Cisco Unity voice messages on a separate, dedicated Exchange server that homes only Cisco Unity voice messages.

The advantages of this model include the following:

The customer does not need to extend the Active Directory schema in the existing forest.

Some companies have one department that manages the phone and voice-messaging system and a separate department that manages Exchange. Dedicated Exchange servers for Cisco Unity voice messages may simplify implementation and maintenance.

Some customers like to keep voice messages and e-mail messages separate.

If Active Directory accounts are created in an existing forest and mailboxes are stored on existing Exchange servers, the customer is responsible for support for the servers. If accounts are created in a dedicated forest and mailboxes are stored on Exchange servers that are dedicated to Cisco Unity voice messages, Cisco will support the entire Cisco Unity system, including dedicated DC/GCs (if any) and dedicated Exchange servers.

The disadvantages of this model include:

A more complicated and time-consuming migration to a Unified Messaging configuration.

More overhead for maintaining the Active Directory and Exchange infrastructure.

Possible additional hardware expense.

Voice Messaging with Customer-Provided Infrastructure

Revised May 6, 2008

In this deployment model:

Each Voice Messaging subscriber requires a separate Active Directory user account in the existing forest. The customer can create a separate domain for these accounts, but that is not required.

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.

This model has the following advantages:

It simplifies the migration from a Voice Messaging Configuration to a Unified Messaging configuration.

Some companies have one department that manages the phone and voice-messaging system and a separate department that manages Exchange. If the two departments do not communicate with one another, dedicated Exchange servers for Cisco Unity voice messages may simplify implementation and maintenance.

Multi-Site WAN with Distributed Messaging

When deploying Cisco Unity in a multi-site WAN with distributed messaging, the customer uses two or more of the deployment models discussed earlier in this section, either at the same physical site or in geographically diverse data centers connected by a WAN. In this deployment, network bandwidth should meet the minimum Microsoft Exchange server inter-site requirements.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

4-3

 

 

 

Image 35
Contents Americas Headquarters Design Guide for Cisco UnityDesign Guide for Cisco Unity Release N T E N T S Workstations Authentication Centralized Voice Messaging Configuration Viii Document Conventions AudienceSupport Policy for Optional Third-Party Software Cisco Product Security Overview Xii Design Guide Overview Product Area Design or Feature DocumentationDesign Guide for Cisco Unity Bridge at Page Design Guide Overview Design Guide for Cisco Unity Release How Cisco Unity Works Cisco Unity ConceptsVoice Messaging Unified MessagingHardware Components of a Cisco Unity System Cisco Unity Supported Platforms List at One or More Cisco Unity ServersNetwork Connection Optional for Some Configurations Domino Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System Voice Messages Are Stored in Domino or ExchangeExchange Enabling Cisco Unity Servers to Communicate with One Another Networking Guide for Cisco Unity at Some Configuration Settings Are Stored in the Registry Availability of Network Resources Name ResolutionAvailability of Message Store Servers Domain Controller Access and AvailabilitySizing and Scaling Cisco Unity Servers Using Firewalls with Cisco UnityNumber of Voice Ports Storage Capacity for Voice MessagesHow Codecs Affect the File Size of Voice Messages Audio CodecsQuality Rating TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems Audio CodecDeployment Models Unified Messaging with Customer-Provided Infrastructure Multi-Site WAN with Distributed Messaging Voice Messaging with Customer-Provided InfrastructurePhysical Placement and Network Infrastructure Active Directory Considerations Considerations for Customer-Provided InfrastructureDesign 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 Domino Address Book Terminology Maximum Number of Cisco Unity SubscribersElement Name Changes That csAdmin Makes to the Domino Address BookChanges That csClient Makes to the Mail File Windows Domains and Domino Domains Server PlacementActive Directory Accounts and Permissions AuthenticationDomino Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Backing Up and Restoring Data Client Access LicensesCisco Unity and the Domino Address Book Message RoutingServers 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 Establishing Support Policies Administrative Access and ControlNetwork Services Deployment Tasks for Unified Messaging ConfigurationsOperational Tasks Design Guide for Cisco Unity Release Overview Integrating Cisco Unity with the Phone SystemHow 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 LAN/WAN Timg IntegrationSerial Integration with Voice Cards Dtmf Integration with Voice CardsConnections for a Serial Integration by Using Voice Cards Settings in the Phone System and in Cisco UnityCall Control General Integration Issues Sccp SIP FeatureIntegrating Cisco Unity with the Phone System Option Considerations Description Cisco Unified Communications Manager Security FeaturesDescription Setting Effect When Data Is EncryptedDisabling and Re-Enabling Security Settings for Individual Voice Messaging PortsPacketization 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 Firmware Updates Serial Integrations Setup and ConfigurationCisco Unity Failover Increasing Port CapacityMultiple Integration Support/Branch Office Consolidation Cisco Unity FailbackIntegrating with Multiple Phone Systems Requirements for Integrations with Multiple Phone Systems Using Sccp Phone Systems with Other IntegrationsHow Alternate Extensions Work Optional Integration FeaturesAlternate Extensions Reasons to Use Alternate ExtensionsMWIs for Extensions on a Non-Integrated Phone System Alternate MWIsCentralized Voice Messaging OL-14619-01 OL-14619-01 Failover Cisco Unity Failover and Standby RedundancyStandby Redundancy Cisco Unity Failover and Standby Redundancy Cisco Unity Failover and Standby Redundancy Pstn WAN Diagram of a Standby Redundancy ConfigurationOL-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