Cisco Systems OL-14619-01 manual Considerations for Customer-Provided Infrastructure

Page 37

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

Considerations for Customer-Provided Infrastructure

For detailed firewall requirements, see the following sections in the System Requirements for

Cisco Unity at

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html:

“Network Requirements”

“Failover Requirements for Separating Cisco Unity Servers by a Firewall”

“Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall”

When Cisco Unity is remotely connected with an IP phone system, it is acceptable to calculate the per-port bandwidth and necessary overhead. The aggregate total of bandwidth for all ports plus any necessary overhead is the minimum bandwidth required.

Cisco Unity supports a maximum of 250 Exchange information stores.

If the Cisco Unity server has two NICs, the NICs cannot be used for load balancing. If dual NICs are configured, we recommend that they be configured in adaptive fault tolerant (AFT) or network fault tolerant (NFT) mode. For additional information about dual NICs, see the “Customizing the Cisco Unity Platform” chapter in the applicable Cisco Unity installation guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

In general, Cisco Unity failover servers can be on separate network segments or subnets. However, both servers must reside in the same Windows site, and each server must directly connect to the DCs, GCs, message store servers, and other network resources necessary to operate normally. For requirements for failover over a WAN, see the “Requirements for Cisco Unity Failover Over a WAN” section in the System Requirements for Cisco Unity Release 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

For information on network requirements for phone system integrations, see the “Integrating Cisco Unity with the Phone System” chapter.

Considerations for Customer-Provided Infrastructure

See the following sections:

Active Directory Considerations, page 4-5

Exchange Considerations (All Versions), page 4-7

Exchange Considerations That Apply Only Exchange 2007, page 4-8

Active Directory Considerations

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

The Active Directory schema must be extended for Cisco Unity to function properly. For information on capacity planning recommendations related to using Cisco Unity with Active Directory, see the Active Directory Capacity Planning (Cisco Unity Version 5.x and Later with Microsoft Exchange) white paper at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html. This white paper also includes sizing information for Active Directory objects that have been voice enabled by Cisco Unity. Finally, it discusses the Cisco Unity schema: what is required when the customer extends the schema, and when it is required.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

4-5

 

 

 

Image 37
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 AuthenticationCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing 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 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 Integration with Cisco Unified Communications Manager Lines and Cables to Make Physical ConnectionsDigital 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 Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP 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 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