Cisco Systems OL-14619-01 manual Administrative Access and Control, Establishing Support Policies

Page 54

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

Deploying Cisco Unity for Lotus Domino

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:

Managing the server resources (hardware, operating system, file system, and other supporting software).

Managing the Cisco Unity application, including web access; supporting components such as SQL Server/MSDE, IIS, and Internet Explorer; the Cisco Unity application log files; and utilities such as the Windows Event Viewer, Performance Monitor, and so on.

Administering Cisco Unity subscribers, distribution lists, call handlers, and so on.

Administering Cisco Unity switch connectivity to Cisco Unified Communications Manager or a circuit-switched phone system.

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:

Define and create the accounts to be used in running the Cisco Unity services.

Define and create the accounts to be used to administer Cisco Unity.

 

Design Guide for Cisco Unity Release 5.x

5-12

OL-14619-01

Image 54
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 Permissions Cisco Unity Subscribers and Domino UsersDomino Clusters Message Routing Client Access LicensesCisco Unity and the Domino Address Book 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 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 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 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