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