Cisco Systems OL-14619-01 manual Exchange Considerations All Versions

Page 39

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

Considerations for Customer-Provided Infrastructure

Exchange Considerations (All Versions)

Note the following Exchange considerations when a Cisco Unity implementation will use customer-provided Exchange infrastructure:

•When Cisco Unity is installed, the installer chooses a partner Exchange server, which is the home of several default Cisco Unity mailboxes, including:

–The Cisco Unity system mailbox (alias: Unity_<ServerName>), which is the mailbox that originates voice messages from outside callers. (Voice messages from Cisco Unity subscribers originate from the mailbox of the caller.) Each Cisco Unity server must have its own system mailbox.

–The mailbox from which broadcast messages are sent.

–If Cisco Unity is interoperating with other voice messaging systems, the mailboxes that send voice messages to and receiver voice messages from the other voice messaging systems.

The partner Exchange server can be running Exchange 2007, Exchange 2003, or Exchange 2000, and it can be either a clustered or non-clustered Exchange server.

Because of the importance of the partner Exchange server in a Cisco Unity installation, the server should be selected primarily on the basis of availability and secondarily on the basis of performance.

•Exchange performance is critical to Cisco Unity performance. To ensure that Exchange performance will not adversely affect Cisco Unity, we recommend that customers assess the performance of their Exchange infrastructure before installing Cisco Unity. For example, the Microsoft TechNet article Exchange Server 2003: Ruling Out Disk-Bound Problems (http://technet.microsoft.com/en-us/library/aa997558.aspx) can provide useful guidance.

•Exchange servers must meet Microsoft requirements, including the maximum number of users per server, the proper amount of memory, the proper processors and processor speed, hard disks that can meet disk-access response times, and placement of data files and transaction log files.

Cisco Unity cannot support Exchange servers that have performance bottlenecks such as slow hard drives or insufficient memory. For example, if slow hard drives or the lack of a dedicated mirror for transaction logs cause delays in recording log transactions, MAPI access (which is used by Microsoft Outlook, Exchange, and Cisco Unity to access Exchange) will be temporarily suspended until the transaction buffers can be cleared to a certain level. This can substantially delay phone access to Cisco Unity.

•The Cisco Unity Voice Connector for Microsoft Exchange, which is required for communicating with another voice-messaging system by using AMIS, the Cisco Unity Bridge, or VPIM, must be installed on the partner Exchange server. The Voice Connector can also, optionally, be installed on one or more other Exchange 2000 or Exchange 2003 servers to optimize message routing via Exchange’s native, cost-based routing. (The Voice Connector cannot be installed on an Exchange 2007 server.)

•For information on the impact of audio codecs on Exchange, see the “Audio Codecs” section on page 3-5.

•In a Voice Messaging configuration, to prevent the message store from filling the hard disk, some customers configure storage limits in Exchange, and use Cisco Unity Message Store Manager to delete old messages. For example, messages older than 30 days might be moved to the deleted-messages folder, and messages older than 60 days might be purged. For more information on Message Store Manager, see the Message Store Manager Help at http://ciscounitytools.com/HelpFiles/MSM/MSMConsoleHelp_ENU.htm.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

4-7

 

 

 

Page 38 Page 40
Image 39
Page 38 Page 40
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 Permissions Cisco Unity Subscribers and Domino UsersDomino Clusters Backing Up and Restoring Data Client Access LicensesCisco Unity and the Domino Address Book Message RoutingUnified Messaging Configurations Unified Messaging, No Domino ClusterServers Requirements and Recommendations Voice Messaging Configuration Criteria for a Supported ConfigurationUnified Messaging, Domino Cluster 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 Lines and Cables to Make Physical Connections Integration with Cisco Unified Communications ManagerDigital Integration with Digital Pimg Units 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 Supported SIP Integrations Cisco Unity Failover with SIP TrunksSIP Compliance 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
Top Page Image Contents