-
Design Guide for Cisco Unity Release 5.x
-
Index
-
Preface
-
Design Guide Overview
-
Cisco Unity Concepts
-
Network Infrastructure Requirements
-
Designing a Cisco Unity System with Exchange as the Message Store
-
Designing a Cisco Unity System with Domino as the Message Store
-
Integrating Cisco Unity with the Phone System
-
Cisco Unity Failover and Standby Redundancy
-
Voice-Recognition Access to Cisco Unity
-
Migrating to Cisco Unity from Another Voice-Messaging System
-
Design Differences Among Versions of Cisco Unity
-
Table Of Contents
Designing a Cisco Unity System with Domino as the Message Store
Overview of Cisco Unity with Domino and Notes
Maximum Number of Cisco Unity Subscribers
Domino Address Book Terminology
IBM Lotus Domino Unified Communications (DUC) for Cisco on Domino Servers and on Client Workstations
Changes That csAdmin Makes to the Domino Address Book
Changes That csClient Makes to the Mail File
Address Book Server, Message Store Server, and Mail Drop Server
Windows Domains and Domino Domains
Active Directory Accounts and Permissions
Cisco Unity Subscribers and Domino Users
Notes Client on the Cisco Unity Server
Migrating from Cisco Unity for Exchange
Cisco Unity and the Domino Address Book
Unified Messaging Configurations
Unified Messaging, No Domino Cluster
Unified Messaging, Domino Cluster
Criteria for a Supported Configuration
Deploying Cisco Unity for Lotus Domino
Administrative Access and Control
Deployment Tasks for Unified Messaging Configurations
Feature Parity Between Cisco Unity for Domino and Cisco Unity for Exchange
Designing a Cisco Unity System with Domino as the Message Store
This chapter focuses on using IBM Lotus Domino as the message store and a Domino address book as the directory for Cisco Unity.
See the following sections:
•
Overview of Cisco Unity with Domino and Notes
•
•
•
•
•
•
Overview of Cisco Unity with Domino and Notes
This section provides an overview of the characteristics of a Cisco Unity system with Domino as the message store. Unless noted, all information applies to both Unified Messaging and Voice Messaging configurations.
See the following sections:
•
•
•
•
•
•
•
•
•
•
Maximum Number of Cisco Unity Subscribers
Cisco Unity for Domino deployments are limited to one Cisco Unity server or one pair of failover servers with a maximum of 7,500 subscribers.
Domino Address Book Terminology
Names.nsf is the first address book (directory) file in a Domino domain, and is created when the first Domino server is installed. Each additional Domino server that is added to the Domino domain receives a replica of Names.nsf.
During Cisco Unity installation, the installer specifies a Domino address book on a Domino server. In general, this address book will be a replica of Names.nsf. The customer can create Cisco Unity subscriber accounts by importing user data from the specified address book. Cisco Unity monitors the address book for changes to Domino users who are also Cisco Unity subscribers and to Domino distribution lists.
A secondary address book is an address book that is typically created to house non-local mail users, who do not own a mailbox in the domain or enterprise. (In Domino, the Person documents for these users have "Other Internet Mail" set in the Mail System field.) The Active Directory equivalent is contacts. You can add one additional (secondary) subscriber address book by using the Cisco Unity Administrator. The secondary address book must reside in the same Domino domain as the primary address book, and cannot be a replica of an address book in another Domino domain.
By default, the address book that the installer specifies in the Message Store Configuration wizard during Cisco Unity Setup is monitored for changes to Cisco Unity data. In addition, you can add up to eight monitored address books by using the Cisco Unity Administrator. Monitored address books may be needed when there are multiple Cisco Unity servers that will be set up for Digital Networking. For more information, see the "Managing Monitored Address Books" section in the "Digital Networking" chapter of the Networking Guide for Cisco Unity Release 5.x at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
IBM Lotus Domino Unified Communications (DUC) for Cisco on Domino Servers and on Client Workstations
To use Domino as the message store and directory, the customer must install components of IBM Lotus Domino Unified Communications (DUC) for Cisco on Domino servers:
•
•
In addition, DUC for Cisco client software must be installed on the client workstation of each Notes user who will be a Cisco Unity subscriber. Installing the client software adds VCR-style recording and playback controls to the message form, and provides message notification, message waiting indicators, and a Lotus Mail template for recording and playing voice messages.
For information on the versions of the following software currently supported, 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:
•
•
•
•
Changes That csAdmin Makes to the Domino Address Book
Table 5-1 shows the elements added to the Domino address book when csAdmin is installed. If csAdmin is uninstalled, these items are removed from the address book.
Changes That csClient Makes to the Mail File
When csClient software is installed on a client workstation, the elements in Table 5-2 are added to the mail file. If csClient is uninstalled, these elements are removed from the mail file.
Address Book Server, Message Store Server, and Mail Drop Server
Cisco Unity interacts with Domino servers that perform a variety of functions. Depending on the number of Domino users, these functions may be all on one Domino server or spread out across many servers:
•
–
The primary address book is the home of the Cisco Unity system mailbox; this mailbox sends voice messages from outside callers. (Voice messages from Cisco Unity subscribers are identified as coming from those subscribers.) Each Cisco Unity server must have a system mailbox.
You choose the primary address book server during Cisco Unity installation.
–
–
•
•
Windows Domains and Domino Domains
A Cisco Unity server can be either a domain controller or a member server in a Windows Server 2003 or Windows 2000 Server domain. If the Cisco Unity server is a member server, it should reside in the same highly available and connected network as a domain controller for that domain.
The customer needs at least one Cisco Unity server for each Domino domain that will home Cisco Unity subscribers.
Server Placement
Revised May 6, 2008Note the following best practices for placement of Cisco Unity servers and the servers that Cisco Unity relies on:
•
•
•
When failover or standby redundancy is configured, the Cisco Unity servers cannot be separated from one another by a firewall. They also cannot be separated by a firewall from:
–
–
–
–
For additional firewall requirements, see the section "Network Requirements" in the System Requirements for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html:
•
•
Active Directory Accounts and Permissions
Cisco Unity requires that three Active Directory domain accounts be created during installation, as described in the Cisco Unity installation guide. One account is used to install Cisco Unity, another is the account that most Cisco Unity services log on as, and the third is used to access the Cisco Unity Administrator. (Some services, including the Text to Speech service and the service that controls Cisco Unity licensing, log on as the local system account.)
The permissions required by each of the accounts are set by the Cisco Unity Permissions Wizard. The account that Cisco Unity services log on as can be used by more than one Cisco Unity server in the same domain. For detailed information on the permissions required, see the Help file Permissions Granted by the Cisco Unity 5.0(1)+ Permissions Wizard at http://ciscounitytools.com/HelpFiles/PW501/PWHelpPermissionsSet_ENU.htm.
These accounts and permissions are required for Cisco Unity-specific functionality and are separate from the Domino permissions that are described in the "Domino Permissions" section.
Domino users who are Cisco Unity subscribers do not need Active Directory accounts, and Cisco Unity administrators and subscribers are not required to use Windows authentication.
Authentication
Cisco Unity subscribers whose class of service (COS) allows them access to the Cisco Unity Administrator can log on to the Cisco Unity Administrator by using Domino authentication, Integrated Windows authentication, or Anonymous authentication, depending on how the system is configured. Subscribers whose COS allows them access to the Cisco Unity Assistant must log on to the Cisco Unity Assistant by using Domino authentication.
For more information, see:
•
•
•
Domino Permissions
Before Cisco Unity is installed, the Cisco Unity installer or a qualified Domino administrator needs to:
•
•
With these permissions, Cisco Unity acts as a Notes user to:
•
•
•
•
•
In addition, when a Domino user is imported into Cisco Unity, Cisco Unity submits an AdminP request to grant the user access to the imported user mail file.
For more information on setting Domino-specific permissions, see the applicable Cisco Unity installation guide, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Cisco Unity Subscribers and Domino Users
A Cisco Unity subscriber is a Domino user who has been DUC for Cisco-enabled and imported into Cisco Unity. The person document of each subscriber has Cisco Unity attributes, and the mail file has DUC for Cisco attributes. The only way to create a Cisco Unity subscriber is to import an existing Domino user into Cisco Unity. Cisco Unity cannot create Domino users by using the Cisco Unity Administrator.
Domino Clusters
Cisco Unity supports homing Cisco Unity subscribers on Domino clusters. The Domino cluster must meet all IBM Lotus requirements, particularly those related to the maximum number of users and to supported hardware.
Depending on the number of users on a cluster, the customer may want to install one Cisco Unity server for each Domino cluster.
The customer is responsible for installing, configuring, and maintaining the Domino cluster.
For more information on Domino clusters, refer to the Lotus Domino documentation, available on the Lotus Domino website.
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.
Cisco Unity requires Editor with Delete Documents permission for the address book that Cisco Unity monitors. A Cisco Unity server can monitor the address books for one domain, including Names.nsf and any secondary address book that may be supporting proxy/remote users (users who do not have mail files in the Domino domain).
For more information on permission requirements, see the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Unified Messaging Configurations
In a Unified Messaging configuration, Cisco Unity does not own the directory or messaging data but instead uses existing directory (Domino address book) and message store information. The benefits of Unified Messaging include:
•
•
•
Unified Messaging, No Domino Cluster
When you are setting up two or more Cisco Unity servers, the servers can be networked by using Cisco Unity Digital Networking. If the phone system has ports available, you can hook up more than one Cisco Unity server to each phone system. For more information, see Table 5-3.
Table 5-3 Server Requirements and Recommendations for a Unified Messaging Configuration
Cisco Unity server
Each physical site that includes one or more Domino servers on which mailboxes for Cisco Unity subscribers are homed also includes at least one Cisco Unity server.
Each Domino domain requires a Cisco Unity server. If you need to import Cisco Unity subscribers in different Domino domains, you must install a Cisco Unity server in each Domino domain and use Digital Networking between the servers.
Domino address book server, message store server, and mail drop server
Domino servers must be in the same highly available and connected LAN as the Cisco Unity server.
Domain controller/global catalog server (DC/GC)
There must be at least one DC/GC per physical site that includes a Cisco Unity server. If necessary, the Cisco Unity server can be the DC/GC.
DNS server
There must be at least one DNS server per physical site that includes a Cisco Unity server. In sites with enough servers, we recommend two or more DNS servers.
Media gateways (for phone system integrations that include PIMG or TIMG units
The PIMG or TIMG units can be connected to the Cisco Unity server by a LAN or a WAN.
Cisco Unified Communications Manager servers
The Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager) and Cisco Unity servers can be connected by a LAN or a WAN.
Cisco Unified Communications Manager Express
The Cisco Unified Communications Manager (CM) Express (formerly known as Cisco Unified CallManager Express) and Cisco Unity servers must be connected by a LAN.
Cisco Unity voice-recognition server
The Cisco Unity voice-recognition server and the Cisco Unity server must be connected by a LAN.
For each Cisco Unity server that homes subscribers for whom you want to have voice-recognition functionality, you must have one voice-recognition server. A voice-recognition server cannot service more than one Cisco Unity server or, when failover is configured, one pair of failover servers.
Voice-recognition software cannot be installed on the Cisco Unity server.
Cisco Unity Bridge server
The Bridge server can be a member server in an existing domain or a workgroup server. It cannot be a DC/GC.
The Cisco Unity Bridge and Cisco Unity servers can be connected by a LAN or a WAN.
Bridge software cannot be installed on the Cisco Unity server.
For more information, see the Design Guide for Cisco Unity Bridge at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_implementation_design_guides_list.html.
Unified Messaging, Domino Cluster
A clustered environment is the same as the non-clustered environment detailed in Table 5-3 except that all Domino servers have to be in the same highly available and connected LAN as the Cisco Unity server.
Domino partitioning is also supported.
Voice Messaging Configuration
A clustered environment is the same as the environment detailed in Table 5-3 except that all Domino servers are dedicated to servicing Cisco Unity voice messages.
Criteria for a Supported Configuration
Requirements for supported configurations for Cisco Unity for Domino include the following:
•
•
•
•
•
•
•
•
Deploying Cisco Unity for Lotus Domino
Cisco Unity for Lotus Domino can be deployed in the following ways:
•
•
•
•
See the following sections for additional information:
•
•
•
Administrative Access and Control
To manage administrative access to the Cisco Unity server and its resources, the customer may want different levels of access for different operations, for example, backing up the server or gathering performance information for trending.
When installing Cisco Unity in a Unified Messaging configuration, it is best to allow administrative access to the server to be governed by the server administration policies of the customer. This should not detract from the administrative access required for normal Cisco Unity operations, which include:
•
•
•
•
Establishing Support Policies
To make administering Cisco Unity more manageable, establish a support policy that separates Cisco Unity-specific administration from administration for the rest of the server. This allows Cisco Unity administrators with limited class of service (COS) settings to access the Cisco Unity application only as designed through their COS.
Network Services
Cisco Unity is a Notes client that uses Notes name resolution to resolve FQDNs in the Domino/Notes environment. Cisco Unity must be able to access and resolve server names across the deployment, or performance will suffer and some Cisco Unity operations will fail. Ideally, the name resolution server will be on the same highly available network as the Cisco Unity server. Because Cisco Unity for Domino can only be deployed in existing Domino environments, name resolution servers should already be available.
Because Cisco Unity still needs to be installed in an Active Directory domain, Cisco Unity relies on Windows DNS. If you install Cisco Unity into an existing Active Directory domain, there should be an existing DNS server highly available. If the customer does not have an existing Active Directory domain, DNS must be installed on the Cisco Unity server.
Deployment Tasks for Unified Messaging Configurations
In a Unified Messaging configuration, pay careful attention to the placement of Cisco Unity servers, how they are managed, and the accounts that are used to manage them.
Consider the following deployment best practices:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Operational Tasks
The following are best practices for an operational Cisco Unity system:
•
•
•
•
•
Feature Parity Between Cisco Unity for Domino and Cisco Unity for Exchange
Cisco Unity 5.0 for Domino does not support:
•
•
•
•
The following capabilities of Cisco Unity for Exchange are not available in Cisco Unity for Domino:
•
•
•
•
•
•
•
The following Cisco Unity tools are not available with Cisco Unity for Domino:
•
•
•
•
•
•