Release Revised May 6
Americas Headquarters
Design Guide for Cisco Unity
Cisco Systems, Inc 170 West Tasman Drive San Jose, CA
Design Guide for Cisco Unity Release
2008 Cisco Systems, Inc. All rights reserved
C O N T E N T S
One or More Message-Store Servers Optional for Some Configurations
Network Connection Optional for Some Configurations
Preface
Voice Messaging with Customer-Provided Infrastructure
Audio Codecs
Workstations
Domino Address Book Terminology
General Integration Issues
Authentication
Deployment Tasks for Unified Messaging Configurations
Voice Messaging Configuration
Messaging Ports SCCP Integrations Only
Setup and Configuration
Optional Integration Features
Alternate MWIs
Voice-Recognition Access to Cisco Unity
Configuration
Diagram of a Standby Redundancy Configuration
Migrating to Cisco Unity from Another Voice-Messaging System
OL-14619-01
viii
Contents Design Guide for Cisco Unity Release
Document Conventions
Preface
Audience
Audience, page Document Conventions, page
Support Policy for Optional Third-Party Software
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Product Security Overview
Preface Design Guide for Cisco Unity Release
OL-14619-01
C H A P T E R
Design or Feature Documentation
Design Guide Overview
Product Area
Domino, see http//ciscounitytools.com/AppThirdPartyFaxConfig.htm
Chapter 8, “Voice-Recognition Access to Cisco Unity”
http//ciscounitytools.com/AppIPFaxConfigurationWizard.htm
ondesignguideslist.html
Chapter 1 Design Guide Overview Design Guide for Cisco Unity Release
OL-14619-01
Chapter 1 Design Guide Overview Design Guide for Cisco Unity Release
OL-14619-01
How Cisco Unity Works
Where Cisco Unity Stores Data, page
Cisco Unity Concepts
How Cisco Unity Works, page
Voice Messaging
Characteristics of Unified Messaging and Voice Messaging Systems
Unified Messaging
One or More Cisco Unity Servers, page
Network Connection Optional for Some Configurations, page
Hardware Components of a Cisco Unity System
One or More Cisco Unity Servers
Network Connection Optional for Some Configurations
One or More Message-Store Servers Optional for Some Configurations
Software Components of a Cisco Unity System
Where Cisco Unity Stores Data
Some Configuration Settings Are Stored in the Registry, page
Voice Messages Are Stored in Domino or Exchange
All Subscriber Information Is Stored in a SQL Server 2000 Database
Exchange
Enabling Cisco Unity Servers to Communicate with One Another
Networking Guide for Cisco Unity at
Some Configuration Settings Are Stored in the Registry
Network Infrastructure Requirements
Name Resolution
Using Firewalls with Cisco Unity, page
Availability of Network Resources
Domain Controller Access and Availability
Availability of Message Store Servers
Maximum Number of Users on Dedicated Domino or Exchange Servers, page
Using Firewalls with Cisco Unity
Sizing and Scaling Cisco Unity Servers
Storage Capacity for Voice Messages, page Number of Voice Ports, page
Maximum Number of Users on Dedicated Domino or Exchange Servers
Storage Capacity for Voice Messages
Number of Voice Ports
Audio Codecs
How Codecs Affect the File Size of Voice Messages
Audio Codec
TTS, TTY, Pocket PCs, and Hand-Held Computers
Interoperability Among Multiple Voice-Messaging Systems
Quality Rating
Deployment Models
Physical Placement and Network Infrastructure, page
Designing a Cisco Unity System with Exchange as the Message Store
Deployment Models, page
Unified Messaging with Customer-Provided Infrastructure
Voice Messaging with Cisco-Provided, Dedicated Infrastructure
Voice Messaging with Customer-Provided Infrastructure
Multi-Site WAN with Distributed Messaging
Physical Placement and Network Infrastructure
Active Directory Considerations, page
Considerations for Customer-Provided Infrastructure
Active Directory Considerations
Exchange Considerations All Versions, page
Active Directory Application Mode ADAM is not supported
Exchange Considerations All Versions
Exchange Considerations That Apply Only Exchange
Design Guide for Cisco Unity Release
Considerations for Cisco-Provided, Dedicated Infrastructure
Considerations for Cisco-Provided, Dedicated Infrastructure
OL-14619-01
Design Guide for Cisco Unity Release
4-10
Considerations for Cisco-Provided, Dedicated Infrastructure
OL-14619-01
Criteria for a Supported Configuration, page
Unified Messaging Configurations, page
Voice Messaging Configuration, page
Windows Domains and Domino Domains, page Server Placement, page
Domino Address Book Terminology
Client Access Licenses, page Backing Up and Restoring Data, page
Maximum Number of Cisco Unity Subscribers
Domino Clusters, page Message Routing, page
Name
Changes That csAdmin Makes to the Domino Address Book
Element
Element
Address Book Server, Message Store Server, and Mail Drop Server
Changes That csClient Makes to the Mail File
Name
Revised May 6
Server Placement
Windows Domains and Domino Domains
Authentication
Active Directory Accounts and Permissions
Domino Clusters
Domino Permissions
Cisco Unity Subscribers and Domino Users
Message Routing
Client Access Licenses
Cisco Unity and the Domino Address Book
Notes Client on the Cisco Unity Server
Servers
Unified Messaging Configurations
Unified Messaging, No Domino Cluster
Requirements and Recommendations
Unified Messaging, Domino Cluster
Voice Messaging Configuration
Criteria for a Supported Configuration
gnguideslist.html
Deployment Tasks for Unified Messaging Configurations, page
Administrative Access and Control, page
Establishing Support Policies, page Network Services, page
Deploying Cisco Unity for Lotus Domino
Deployment Tasks for Unified Messaging Configurations
Administrative Access and Control
Network Services
Establishing Support Policies
Operational Tasks
5-13
5-14
Cisco Unity 5.0 for Domino does not support Cisco Unity reports
Optional Integration Features, page Centralized Voice Messaging, page
General Integration Issues, page
Integrating by Using SIP, page
Integrating Cisco Unity with the Phone System
How an Integration Works
guideslist.html
Digital Integration with Digital PIMG Units
Lines and Cables to Make Physical Connections
Integration with Cisco Unified Communications Manager
DTMF Integration with Analog PIMG Units
Serial SMDI, MCI, or MD-110 Integration with Analog PIMG Units
TIMG Integration
Connections for an Integration by Using TIMG Units
DTMF Integration with Voice Cards
Serial Integration with Voice Cards
Figure 6-6 Connections for a DTMF Integration by Using Voice Cards
Settings in the Phone System and in Cisco Unity
Call Information Exchanged by the Phone System and Cisco Unity
Sample Path for a Call from the Phone System to a Subscriber
Call Control
General Integration Issues
6-10
Feature
SCCP
Differences Between SCCP and SIP Integration Methods
6-11
6-12
Option
Considerations
When Data Is Encrypted, page
Cisco Unified Communications Manager Security Features
Cisco Unified Communications Manager Security Features, page
Multiple Integrations Can Have Different Security Mode Settings, page
6-14
Description
Effect
When Data Is Encrypted
Setting
6-15
Disabling and Re-Enabling Security
Multiple Integrations Can Have Different Security Mode Settings
Settings for Individual Voice Messaging Ports
6-16
Packetization SCCP Integrations Only
6-17
Feature
Multiple Cisco Unified Communications Manager Express Version Support
6-18
SCCP
Multiple Cisco Unified Communications Manager Express Routers Integrating with a Single Cisco Unity Server
Call forward to busy greeting
6-20
Figure 6-11 Cisco Unified Communications Manager Fallback with PSTN
Call transfers
Impact of Non-Delivery of RDNIS on Voice Mail Calls Routed via AAR
6-21
Message waiting indication
Integrating by Using SIP
6-22
SIP Compliance
Supported SIP Integrations
Cisco Unity Failover with SIP Trunks
6-23
Digital Integration with Digital PIMG Units
Description of PIMG Integrations
6-24
DTMF Integration with Analog PIMG Units
6-25
The phone system sends call information, MWI requests, and voice connections through the analog lines, which connect the phone system to the PIMG units. The PIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initiation Protocol SIP. Figure 6-13 shows the connections for a DTMF integration by using analog PIMG units
Serial SMDI, MCI, or MD-110 Integration with Analog PIMG Units
Description of TIMG Integrations
6-26
Serial Integrations
Setup and Configuration
Firmware Updates
6-27
6-28
Increasing Port Capacity
Cisco Unity Failover
6-29
Cisco Unity Failback
Multiple Integration Support/Branch Office Consolidation
Call Control QOS Byte
Integrating with Multiple Phone Systems
6-30
RTP QOS Byte
Notes for PIMG Integrations
Using SCCP Phone Systems with Other Integrations
Requirements for Integrations with Multiple Phone Systems
6-31
Reasons to Use Alternate Extensions
Optional Integration Features
Alternate Extensions
How Alternate Extensions Work
MWIs for Extensions on a Non-Integrated Phone System
Setting Up Alternate MWIs for Extensions on the Same Phone System
Alternate MWIs
6-33
Centralized Voice Messaging
6-34
6-35
Message waiting indication MWI
Centralized Voice Messaging
6-36
Chapter 6 Integrating Cisco Unity with the Phone System
Design Guide for Cisco Unity Release
Comparison of Cisco Unity Failover and Standby Redundancy
Cisco Unity Failover and Standby Redundancy
Failover
Comparison of Cisco Unity Failover and Standby Redundancy, page
Standby Redundancy
Page
The names of both Cisco Unity servers must be 14 characters or shorter
Data Center
Diagram of a Standby Redundancy Configuration
Figure 7-1 Cisco Unity Standby Redundancy Example Diagram
primary
OL-14619-01
Chapter 7 Cisco Unity Failover and Standby Redundancy
Standby Redundancy Design Guide for Cisco Unity Release
Voice-Recognition Access to Cisco Unity
C H A P T E R
OL-14619-01
Chapter 8 Voice-Recognition Access to Cisco Unity
Design Guide for Cisco Unity Release
Migrating to Cisco Unity from Another Voice-Messaging System
C H A P T E R
The supporting infrastructure for example, message store servers, whether dedicated to
I N D E
IN-1
IN-2
Design Guide for Cisco Unity Release
IN-3
Index
OL-14619-01
OL-14619-01
IN-4
Index Design Guide for Cisco Unity Release
