Cisco Systems OL-14619-01 manual Standby Redundancy

Page 94

Chapter 7 Cisco Unity Failover and Standby Redundancy

Standby Redundancy

Configuring Failover When Cisco Unity Servers Are Separated by a Firewall

Revised May 6, 2008

When Exchange is the message store, you can separate Cisco Unity primary and secondary servers by a firewall. When IBM Lotus Domino is the message store, the primary and secondary servers cannot be separated by a firewall.

If the system includes a Cisco Unity voice recognition server, the primary and secondary Cisco Unity servers must be on the same side of the firewall as the Cisco Unity voice recognition server.

For additional requirements, see the “Failover Requirements for Separating Cisco Unity Servers by a Firewall” in the System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Installing Exchange 2003 on the Cisco Unity Secondary Server in a Voice Messaging Configuration with Failover

When Cisco Unity failover is installed in a Voice Messaging configuration, Exchange Server 2003 can be installed on the secondary server instead of on a separate, third server. Requirements for this configuration are listed in the “Requirements When the Message Store Is Installed on the Secondary Server” section of 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.

Requirements for Spanning a Cisco Unity Failover Pair Across Redundant Data Centers

Revised May 6, 2008

Some customers maintain redundant data centers that are so well connected that they essentially form a single LAN. For these customers, failover may be a more suitable configuration than standby redundancy. For detailed requirements for this configuration, see the section “Failover Requirements for Separating Cisco Unity Servers by a WAN” in the System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Standby Redundancy

Note the following about a Cisco Unity system configured for standby redundancy:

The standby redundancy configuration requires a minimum available bandwidth of 100 Mb/second between the data centers in which the Cisco Unity primary and secondary servers are installed. This is because of two bandwidth spikes, one caused by SQL Server, the other by Cisco Unity:

Once daily (by default at 2:00 a.m.), SQL Server replicates data from the active server to the inactive server.

Cisco Unity periodically replicates WAV files of voice names, greetings, call handlers, and interview handlers from the active server to the inactive server.

If something happens to the data center in which the Cisco Unity server is installed, the customer must have:

A way to reroute call traffic to the data center in which the secondary server is installed.

Design Guide for Cisco Unity Release 5.x

7-2

OL-14619-01

 

 

Image 94
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 Voice Messages Are Stored in Domino or Exchange Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System 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 MessagesAudio Codec TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems 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 PermissionsCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Message Routing Client Access LicensesCisco Unity and the Domino Address Book 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 Deployment Tasks for Unified Messaging Configurations Administrative Access and ControlNetwork Services Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Integrating Cisco Unity with the Phone System OverviewHow 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 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 Cisco Unity Failover with SIP Trunks Supported SIP IntegrationsSIP 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 SystemsReasons to Use Alternate Extensions Optional Integration FeaturesAlternate 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