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