Cisco Systems OL-14619-01 manual Considerations for Cisco-Provided, Dedicated Infrastructure

Page 41

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

Considerations for Cisco-Provided, Dedicated Infrastructure

Considerations for Cisco-Provided, Dedicated Infrastructure

Note the following considerations when a Cisco Unity implementation will use Cisco-provided, dedicated Exchange and Active Directory infrastructure:

•Ensure that the servers selected for Cisco Unity and for Exchange are able to handle the proposed number of users. For information on selecting servers, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

•If the customer is installing Cisco Unity and Exchange servers in multiple locations and if they will all be in the same Active Directory forest, ensure that Active Directory sites are configured.

•If two or more Cisco Unity servers are being installed in a forest but they are being installed in different forest roots, configure a one-way trust to enable client authentication. For more information, see the “Grant Unity Access” section in the Client Access in a Voice Messaging-Only Deployment (Cisco Unity Version 4.0) white paper at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

Note The version of GrantUnityAccess shipped with Cisco Unity 5.0 requires a two-way trust due to caveat CSCsi68156. An updated version of GrantUnityAccess that does not have this problem is available on the “4.x/5.x Tools” page on the Cisco Unity Tools website at http://ciscounitytools.com/4_x_tools.htm.

•Within a given data center, if the location will have two Exchange servers, we recommend that the customer make both servers DC/GCs and run DNS on both servers. If the location will have four or more Exchange servers, we recommend that the customer make half of the Exchange servers DC/GCs and run DNS on two of them.

•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.

•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.)

•The customer can configure Exchange clustering by using the Voice Mail Run-Time Edition of Microsoft Exchange Server 2003 Enterprise Edition that is shipped with Cisco Unity. However, the customer is responsible for supporting the Exchange cluster and any custom hardware or configuration.

•In a Voice Messaging configuration, to help prevent Exchange transaction logs from filling the hard disk, a wizard in Cisco Unity Setup prompts the installer to change the circular-logging setting for any message store in the forest for which circular logging is turned off. If the customer is using an Exchange-aware backup application to back up Exchange message stores and clear transaction logs, the installer can choose not to change the circular-logging setting.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

4-9

 

 

 

Page 40 Page 42
Image 41
Page 40 Page 42
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 Software Components of a Cisco Unity System Where Cisco Unity Stores DataVoice 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 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 CodecsInteroperability Among Multiple Voice-Messaging Systems TTS, TTY, Pocket PCs, and Hand-Held ComputersAudio Codec Quality RatingDeployment 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 Cisco Unity and the Domino Address Book Client Access LicensesMessage 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 Network Services Administrative Access and ControlDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational 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 IntegrationsAlternate Extensions Optional Integration FeaturesReasons to Use Alternate Extensions How Alternate Extensions WorkMWIs 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