Cisco Systems OL-14619-01 manual Operational Tasks

Page 55

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

Deploying Cisco Unity for Lotus Domino

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

Install DUC for Cisco components on the applicable Domino servers.

Define the level of access to the local Cisco Unity server necessary for an administrator. Subscribers who are not administrators do not need direct access to the Cisco Unity server operating system or file system.

Define a policy for Cisco Unity classes of service for each Cisco Unity server.

Define the Cisco Unity templates to be used for subscribers.

Define the Cisco Unity distribution lists for each installation. (Other than the default distribution lists created during installation, you must either identify existing distribution lists in the Domino address book or create new distribution lists, and then import them into Cisco Unity.)

Define any audio-text applications that need to be created on each Cisco Unity server.

Define dialing restrictions necessary to prevent subscribers from accessing unauthorized outside numbers.

Verify that the number of subscribers serviced by each Cisco Unity server is known and documented (there is a limit of 7,500 subscribers per Cisco Unity server).

Verify that each Cisco Unity server is properly sized for the number of subscribers it will service. For additional sizing information, see the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.

Create and document a suitable disaster recovery plan.

Verify that the switch integration is understood.

Determine the number of ports needed for message notification, and for recording and playing messages over the phone.

Verify that all hardware and supporting components are set up correctly.

List the acceptance tests to be run after the server is installed and before going live.

Verify that there is a fallback procedure in the event that problems are encountered.

Define any measurements necessary to benchmark the initial performance of the system.

Install the DUC for Cisco client on workstations for Cisco Unity subscribers. This is necessary before a Domino user can be imported into Cisco Unity as a subscriber.

Operational Tasks

The following are best practices for an operational Cisco Unity system:

Create and implement a regular maintenance schedule to gather logs and to monitor the use of server resources such as disk space, memory, and the CPU.

Verify that regular backups are occurring.

Make arrangements for any regular downtime necessary for offline maintenance activities.

Make arrangements for any special administrative tasks, for example maintaining and creating audio-text applications and running clean up utilities such as Directory Walker.

Before reconfiguring the system, for example when migrating from Voice Messaging to Unified Messaging or when upgrading hardware, mock up the existing Cisco Unity system in a lab environment, and test and validate the work.

 

 

Design Guide for Cisco Unity Release 5.x

 

 

 

 

 

 

OL-14619-01

 

 

5-13

 

 

 

 

 

Image 55
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 Domino Where Cisco Unity Stores DataSoftware Components of a Cisco Unity System Voice Messages Are Stored in Domino or ExchangeExchange 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 CodecsQuality Rating TTS, TTY, Pocket PCs, and Hand-Held ComputersInteroperability Among Multiple Voice-Messaging Systems Audio CodecDeployment 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 Backing Up and Restoring Data Client Access LicensesCisco Unity and the Domino Address Book Message RoutingUnified 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 Establishing Support Policies Administrative Access and ControlNetwork Services Deployment Tasks for Unified Messaging ConfigurationsOperational 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 IntegrationsHow Alternate Extensions Work Optional Integration FeaturesAlternate Extensions Reasons to Use Alternate ExtensionsMWIs 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