Cisco Systems OL-14619-01 manual Domino Permissions, Cisco Unity Subscribers and Domino Users

Page 49

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

Overview of Cisco Unity with Domino and Notes

Domino Permissions

Before Cisco Unity is installed, the Cisco Unity installer or a qualified Domino administrator needs to:

•Create a group for Cisco Unity servers named UnityServers, and grant the group Editor permissions for Admin4.nsf and Editor with Delete Documents permissions for Names.nsf.

•Confirm that the UnityServers group has the permissions required to create databases and templates. This allows Cisco Unity to create mail files for the default accounts.

With these permissions, Cisco Unity acts as a Notes user to:

•Import data from the Domino address book to create Cisco Unity subscribers, contacts, and distribution lists.

•Change the Domino address book by using the Cisco Unity Administrator.

•Submit voice messages through Domino.

•Retrieve and play messages left for subscribers.

•Get information about the read/unread status of voice messages, e-mail, and fax messages in a subscriber mailbox, and send notification when there are new messages.

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.

Design Guide for Cisco Unity Release 5.x

 

OL-14619-01

5-7

 

 

 

Page 48 Page 50
Image 49
Page 48 Page 50
Contents Americas Headquarters Design Guide for Cisco UnityDesign Guide for Cisco Unity Release N T E N T S Workstations Authentication Centralized Voice Messaging Configuration Viii Document Conventions AudienceSupport Policy for Optional Third-Party Software Cisco Product Security Overview Xii Design Guide Overview Product Area Design or Feature DocumentationDesign Guide for Cisco Unity Bridge at Page Design Guide Overview Design Guide for Cisco Unity Release How Cisco Unity Works Cisco Unity ConceptsVoice Messaging Unified MessagingHardware Components of a Cisco Unity System Cisco Unity Supported Platforms List at One or More Cisco Unity ServersNetwork Connection Optional for Some Configurations Software Components of a Cisco Unity System Where Cisco Unity Stores DataVoice 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 Availability of Network Resources Name ResolutionAvailability of Message Store Servers Domain Controller Access and AvailabilitySizing and Scaling Cisco Unity Servers Using Firewalls with Cisco UnityNumber of Voice Ports Storage Capacity for Voice MessagesHow Codecs Affect the File Size of Voice Messages Audio CodecsInteroperability Among Multiple Voice-Messaging Systems TTS, TTY, Pocket PCs, and Hand-Held ComputersAudio Codec Quality RatingDeployment Models Unified Messaging with Customer-Provided Infrastructure Multi-Site WAN with Distributed Messaging Voice Messaging with Customer-Provided InfrastructurePhysical Placement and Network Infrastructure Active Directory Considerations Considerations for Customer-Provided InfrastructureDesign 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 Domino Address Book Terminology Maximum Number of Cisco Unity SubscribersElement Name Changes That csAdmin Makes to the Domino Address BookChanges That csClient Makes to the Mail File Windows Domains and Domino Domains Server PlacementActive Directory Accounts and Permissions AuthenticationCisco Unity Subscribers and Domino Users Domino PermissionsDomino Clusters Cisco Unity and the Domino Address Book Client Access LicensesMessage Routing 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 Network Services Administrative Access and ControlDeployment Tasks for Unified Messaging Configurations Establishing Support PoliciesOperational Tasks Design Guide for Cisco Unity Release Overview Integrating Cisco Unity with the Phone SystemHow 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 LAN/WAN Timg IntegrationSerial Integration with Voice Cards Dtmf Integration with Voice CardsConnections for a Serial Integration by Using Voice Cards Settings in the Phone System and in Cisco UnityCall Control General Integration Issues Sccp SIP FeatureIntegrating Cisco Unity with the Phone System Option Considerations Description Cisco Unified Communications Manager Security FeaturesDescription Setting Effect When Data Is EncryptedDisabling and Re-Enabling Security Settings for Individual Voice Messaging PortsPacketization 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 Firmware Updates Serial Integrations Setup and ConfigurationCisco Unity Failover Increasing Port CapacityMultiple Integration Support/Branch Office Consolidation Cisco Unity FailbackIntegrating with Multiple Phone Systems Requirements for Integrations with Multiple Phone Systems Using Sccp Phone Systems with Other IntegrationsAlternate Extensions Optional Integration FeaturesReasons to Use Alternate Extensions How Alternate Extensions WorkMWIs for Extensions on a Non-Integrated Phone System Alternate MWIsCentralized Voice Messaging OL-14619-01 OL-14619-01 Failover Cisco Unity Failover and Standby RedundancyStandby Redundancy Cisco Unity Failover and Standby Redundancy Cisco Unity Failover and Standby Redundancy Pstn WAN Diagram of a Standby Redundancy ConfigurationOL-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