Cisco Systems OL-14619-01 manual Enabling Cisco Unity Servers to Communicate with One Another

Page 24

Chapter 2 Cisco Unity Concepts

Where Cisco Unity Stores Data

Reliability: Because subscriber data is stored on the Cisco Unity server, Cisco Unity can answer calls, let outside callers look up subscriber extensions, and take messages even when the Domino or Exchange network is down. (When the Domino or Exchange network is unavailable, new messages are stored on the Cisco Unity server, and subscribers have access to those messages.)

Scalability: SQL Server 2000 was designed to support the largest enterprise data processing systems, so there is more than enough room for storing the Cisco Unity data. Although MSDE has storage limitations that SQL Server does not, it is also more than adequate for the Cisco Unity configurations for which it is sold.

Network Impact: Only a small subset of subscriber information needs to be stored in the directory, and that information does not change frequently. Therefore, directory replication caused by changes to Cisco Unity data is minimal after subscriber accounts have been created.

Some Subscriber Information Also Appears in the Domino Address Book or in Active Directory

A small amount of data that appears in the SQL Server 2000 database also appears in the Domino address book or in Active Directory. This information, mostly subscriber data (including the recorded voice name), is added to the directory to enable Cisco Unity servers to communicate with one another and to enable communication between Cisco Unity and other voice messaging systems. Cisco Unity uses a directory monitor to keep the data in the directory synchronized with the data in the SQL Server 2000 database.

Replicating data to the Domino address book or to Active Directory requires some changes to the directory. If the customer is using:

Domino, IBM Lotus Domino Unified Communications (DUC) for Cisco must be installed on the Domino servers that will home Cisco Unity subscribers. This adds elements to the address book. In addition, DUC for Cisco must be installed on the client workstation for each Cisco Unity subscriber, which adds elements to the mail file for the client.

Exchange, the Active Directory schema must be extended with a few Cisco Unity–specific attributes. For information about the Active Directory schema extensions, see the applicable Cisco Unity Data and the Directory white paper at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

Enabling Cisco Unity Servers to Communicate with One Another

When two or more Cisco Unity servers are added to the same Domino address book or Active Directory forest, each Cisco Unity server serves a distinct group of subscribers. You can optionally configure the Cisco Unity servers to communicate with one another, which lets you administer subscriber accounts on all Cisco Unity servers from a single location and lets callers leave messages for any subscriber, regardless of the Cisco Unity server with which the subscriber is associated.

If you configure multiple Cisco Unity servers to communicate with one another, two types of

Cisco Unity data are stored in the directory:

A primary location object for each Cisco Unity server. This unique identifier contains the addressing information that Cisco Unity needs to route messages to other Cisco Unity servers. The directory contains one primary location object for each Cisco Unity server in the Domino domain or Active Directory forest.

Selected subscriber data. The stored properties include the Cisco Unity server with which each subscriber is associated, the subscriber extension, and a recording of the subscriber name.

Design Guide for Cisco Unity Release 5.x

2-8

OL-14619-01

 

 

Image 24
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