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