Cisco Systems OL-14619-01 manual Physical Placement and Network Infrastructure

Page 36

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

Physical Placement and Network Infrastructure

When all Cisco Unity servers will be in the same Active Directory forest and the customer wants subscribers to be able to send voice messages across servers, use Cisco Unity Digital Networking to connect them. The messaging functionality across Cisco Unity servers is the same as the messaging functionality on a single Cisco Unity server.

When Cisco Unity servers will be in two or more Active Directory forests, you can use VPIM networking to connect them. The messaging functionality across Cisco Unity servers is not identical to the messaging functionality on a single Cisco Unity server, but most functionality is preserved. (VPIM networking requires that the Cisco Unity Voice Connector for Microsoft Exchange be installed on an Exchange 2003 or Exchange 2000 server in each forest.) For more information, see the applicable Networking Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

When the customer wants Cisco Unity to communicate with another voice messaging system, the method you use to network them and the functionality that is available depend on the voice-messaging system. For example, to network Cisco Unity with Cisco Unity Express or with Cisco Unity Connection, you use VPIM networking, and to network Cisco Unity with Octel voice-messaging systems, you use the Cisco Unity Bridge. For more information, see:

•The applicable Networking Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

•Networking Options Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Physical Placement and Network Infrastructure

Revised May 6, 2008

To ensure that Cisco Unity functions properly, we require that a Cisco Unity server be in the same data center as the following servers:

•The Exchange server that Cisco Unity communicates with, commonly known as the partner Exchange server. For more information on the partner Exchange server, see the “Exchange Considerations (All Versions)” section on page 4-7.

•Every Exchange server on which mailboxes for that Cisco Unity server are homed. If Cisco Unity is separated by a WAN from an Exchange server on which subscriber mailboxes are homed, a second Cisco Unity server must be co-located with the remote Exchange server.

•At least one domain controller. If Cisco Unity subscribers are homed in more than one domain, a DC for each domain must be in the same data center as the Cisco Unity server.

•At least one global catalog server.

•At least one DNS server.

These requirements apply regardless of whether the non-Cisco Unity servers are customer provided, or are Cisco provided and dedicated to Cisco Unity.

Connect the Cisco Unity server and the servers that Cisco Unity relies on with a high-speed switched gigabit network with no congestion. Total MAPI response time must be less that 10 milliseconds.

The Cisco Unity server should be installed into the same Windows site as the Exchange servers it services.

Note the following:

•Cisco Unity can coexist with firewalls. However, note that Cisco Unity should never be deployed outside of a firewall. Doing so can expose the Cisco Unity server to unwanted intrusion from the Internet, even if the server is hardened.

Design Guide for Cisco Unity Release 5.x

4-4

OL-14619-01

 

 

Page 35 Page 37
Image 36
Page 35 Page 37
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 Where Cisco Unity Stores Data Software Components of a Cisco Unity SystemVoice 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 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 MessagesTTS, TTY, Pocket PCs, and Hand-Held Computers Interoperability Among Multiple Voice-Messaging SystemsAudio Codec 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 PermissionsDomino Permissions Cisco Unity Subscribers and Domino UsersDomino Clusters Client Access Licenses Cisco Unity and the Domino Address BookMessage Routing Backing Up and Restoring DataUnified 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 Administrative Access and Control Network ServicesDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow 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 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 Supported SIP Integrations Cisco Unity Failover with SIP TrunksSIP 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 SystemsOptional Integration Features Alternate ExtensionsReasons to Use Alternate 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
Top Page Image Contents