Cisco Systems OL-14619-01 manual Some Configuration Settings Are Stored in the Registry

Page 26

Chapter 2 Cisco Unity Concepts

Where Cisco Unity Stores Data

Because this information can be stored and changed in multiple locations, it must be regularly synchronized. Cisco Unity includes separate directory monitors for Domino and for Active Directory that keep the directory synchronized with the SQL Server 2000 database. Every few minutes, the directory monitor checks for new, changed, and deleted objects, and replicates the information.

When two or more Cisco Unity servers are added to the same Active Directory forest, a global catalog monitor keeps the SQL Server 2000 database synchronized with the global catalog. This is how each Cisco Unity server gathers information on subscribers who are associated with other Cisco Unity servers.

Because the amount of data stored in the directory is so small, the impact of replication between the SQL Server 2000 database and the directory is minimal (except when the first Cisco Unity subscribers are created by importing them in bulk from Exchange or from a text file).

Messages from Outside Callers Are Temporarily Stored on the Cisco Unity Server

All messages from outside callers are temporarily stored on the Cisco Unity server before they are forwarded to Domino or Exchange for storage in the subscriber mailbox. This allows Cisco Unity to continue functioning when the network connection between the Cisco Unity server and the Domino or Exchange servers is down, or when one or more Domino or Exchange servers are down.

While Domino, Exchange, and/or the network is offline, Cisco Unity can still answer calls, allow outside callers to look up subscriber extensions, and record voice messages. During this time, subscribers who check their voice messages hear the Unity Messaging Repository (UMR) conversation, which explains that their Domino or Exchange server is not available, but lets them access voice messages left after the problem started. When the Domino server, Exchange server, and/or the network is back on line, the voice messages that were stored in the UMR are routed to the subscriber mailboxes. (In some cases when a network connection or a Domino or Exchange server is down, subscriber-to-subscriber messages are also treated as outside caller messages and stored on the Cisco Unity server until they can be delivered to the appropriate mailbox.)

Some Subscriber Information and Configuration Settings Are Stored on the Cisco Unity Server

Selected recordings and configuration settings are stored in files on the Cisco Unity server, including subscriber greetings (“Hi, this is Pat and I am out of the office today...”), recorded voice names, and some phone system integration settings.

Some Configuration Settings Are Stored in the Registry

Selected server-specific configuration settings are stored in the Windows registry, including some phone system integration and logging settings.

 

Design Guide for Cisco Unity Release 5.x

2-10

OL-14619-01

Page 25 Page 27
Image 26
Page 25 Page 27
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 PermissionsDomino Clusters Domino PermissionsCisco Unity Subscribers and Domino Users Message Routing Client Access LicensesCisco Unity and the Domino Address Book 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 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 Digital Integration with Digital Pimg Units Lines and Cables to Make Physical ConnectionsIntegration with Cisco Unified Communications Manager 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 SIP Compliance Supported SIP IntegrationsCisco Unity Failover with SIP Trunks 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
Top Page Image Contents