Cisco Systems OL-14619-01 manual Cisco Unity and the Domino Address Book, Message Routing

Page 50

Chapter 5 Designing a Cisco Unity System with Domino as the Message Store

Cisco Unity and the Domino Address Book

Message Routing

Cisco Unity voice messages are routed to Domino mailboxes by Domino. When a caller leaves a voice message (whether an outside caller or a subscriber), Cisco Unity submits the messages to Mail.box on the mail drop server. The mail drop server determines the routing path to the mail file of the recipient. When Cisco Unity has given the message to the mail drop server, the Domino services are responsible for delivery.

Notes Client on the Cisco Unity Server

For Cisco Unity to interact with a Domino server, a Notes Client must be installed on the Cisco Unity server. No other Domino software is installed on the Cisco Unity server. In order to determine the correct version of the Notes client to use, see the “Domino Requirements—Message Store” section of System Requirements for Cisco Unity Release 5.0 at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Client Access Licenses

DUC for Cisco is automatically shipped by Cisco with all Cisco Unity for Domino systems.

The customer is responsible for purchasing and maintaining any other Lotus licenses that may be required.

Backing Up and Restoring Data

Backing up mailboxes is important in any Unified Messaging deployment. The customer should use a backup program qualified by IBM Lotus for use with Domino.

Migrating from Cisco Unity for Exchange

Cisco Unity for Exchange systems, configured either for Voice Messaging or Unified Messaging, can be converted to Cisco Unity 5.0 for Domino, but only by reinstalling all software, and losing Cisco Unity settings and voice messages.

Cisco Unity and the Domino Address Book

Cisco Unity for Domino uses a Domino address book as its directory service. However, the majority of information on Cisco Unity subscribers and other Cisco Unity objects appears only in a SQL Server/MSDE database. For the small amount of data that appears both in the Domino address book and in the Cisco Unity database (for example, extension), Cisco Unity periodically checks the Domino address book for changes and replicates those changes in the Cisco Unity database. Some of the changes that are made in the Cisco Unity Administrator are replicated to the Domino address book. After a Cisco Unity system is installed and running, changes to the address book and to settings in the Cisco Unity Administrator are relatively few in number, so this replication will not hurt performance.

Design Guide for Cisco Unity Release 5.x

5-8

OL-14619-01

 

 

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