Cisco Systems OL-14619-01 User Manual
Design Guide for Cisco Unity
Release 5.x
Revised May 6, 2008
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-14619-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
IMPLIED, INCLUDING, WITHOUT
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick
Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified
Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ
Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Pac ke t, PIX, Post-Routing, Pre-Routing,
ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO
are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0501R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Design Guide for Cisco Unity Release 5.x
© 2008 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface ix
Audience ix
Document Conventions ix
Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and Software x
Support Policy for Optional Third-Party Software x
Obtaining Documentation, Obtaining Support, and Security Guidelines xi
Cisco Product Security Overview xi
CHAPTER
CHAPTER
1 Design Guide Overview 1-1
2 Cisco Unity Concepts 2-1
How Cisco Unity Works 2-1
Characteristics of Unified Messaging and Voice Messaging Systems 2-2
Unified Messaging 2-2
Voice Messaging 2-2
Hardware Components of a Cisco Unity System 2-3
Cisco Unified Communications Manager or Another Supported Phone System 2-3
One or More Cisco Unity Servers 2-4
Voice Cards or PIMG Units (Required for Integrations with Circuit-Switched Phone Systems) 2-4
Expansion Chassis (Required Only for Some Integrations with Circuit-Switched Phone Systems) 2-4
One or More Message-Store Servers (Optional for Some Configurations) 2-5
One or More Dedicated Domain Controllers/Global Catalog Servers (Exchange Only, Large Voice
Messaging Configurations Only)
Cisco Unity Bridge Server (Required Only for Interoperating with Avaya Voice Messaging
Systems)
2-5
Network Connection (Optional for Some Configurations) 2-5
2-5
OL-14619-01
Software Components of a Cisco Unity System 2-6
Where Cisco Unity Stores Data 2-6
Voice Messages Are Stored in Domino or Exchange 2-6
All Subscriber Information Is Stored in a SQL Server 2000 Database 2-7
Some Subscriber Information Also Appears in the Domino Address Book or in Active Directory 2-8
Data That Appears in Both the SQL Server 2000 Database and in the Address Book/Directory Is
Automatically Synchronized
2-9
Messages from Outside Callers Are Temporarily Stored on the Cisco Unity Server 2-10
Design Guide for Cisco Unity Release 5.x
iii
Contents
Some Subscriber Information and Configuration Settings Are Stored on the Cisco Unity Server 2-10
Some Configuration Settings Are Stored in the Registry 2-10
CHAPTER
CHAPTER
3 Network Infrastructure Requirements 3-1
Availability of Network Resources 3-1
Name Resolution 3-1
Domain Controller Access and Availability 3-2
Availability of Message Store Servers 3-2
Using Firewalls with Cisco Unity 3-3
Sizing and Scaling Cisco Unity Servers 3-3
Maximum Number of Users on Dedicated Domino or Exchange Servers 3-4
Storage Capacity for Voice Messages 3-4
Number of Voice Ports 3-4
Audio Codecs 3-5
How Codecs Affect the File Size of Voice Messages 3-5
TTS, TTY, Pocket PCs, and Hand-Held Computers 3-6
Interoperability Among Multiple Voice-Messaging Systems 3-6
4 Designing a Cisco Unity System with Exchange as the Message Store 4-1
Deployment Models 4-1
Unified Messaging with Customer-Provided Infrastructure 4-2
Mixed Unified Messaging and Voice Messaging with Customer-Provided Infrastructure 4-2
Voice Messaging with Cisco-Provided, Dedicated Infrastructure 4-2
Voice Messaging with Customer-Provided Infrastructure 4-3
Multi-Site WAN with Distributed Messaging 4-3
CHAPTER
iv
Physical Placement and Network Infrastructure 4-4
Considerations for Customer-Provided Infrastructure 4-5
Active Directory Considerations 4-5
Exchange Considerations (All Versions) 4-7
Exchange Considerations That Apply Only Exchange 2007 4-8
Considerations for Cisco-Provided, Dedicated Infrastructure 4-9
5 Designing a Cisco Unity System with Domino as the Message Store 5-1
Overview of Cisco Unity with Domino and Notes 5-1
Maximum Number of Cisco Unity Subscribers 5-2
Domino Address Book Terminology 5-2
IBM Lotus Domino Unified Communications (DUC) for Cisco on Domino Servers and on Client
Workstations
5-2
Address Book Server, Message Store Server, and Mail Drop Server 5-4
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Windows Domains and Domino Domains 5-5
Server Placement 5-5
Active Directory Accounts and Permissions 5-6
Authentication 5-6
Domino Permissions 5-7
Cisco Unity Subscribers and Domino Users 5-7
Domino Clusters 5-7
Message Routing 5-8
Notes Client on the Cisco Unity Server 5-8
Client Access Licenses 5-8
Backing Up and Restoring Data 5-8
Migrating from Cisco Unity for Exchange 5-8
Cisco Unity and the Domino Address Book 5-8
Unified Messaging Configurations 5-9
Unified Messaging, No Domino Cluster 5-9
Unified Messaging, Domino Cluster 5-10
Contents
CHAPTER
Voice Messaging Configuration 5-10
Criteria for a Supported Configuration 5-10
Deploying Cisco Unity for Lotus Domino 5-11
Administrative Access and Control 5-12
Establishing Support Policies 5-12
Network Services 5-12
Deployment Tasks for Unified Messaging Configurations 5-12
Operational Tasks 5-13
Feature Parity Between Cisco Unity for Domino and Cisco Unity for Exchange 5-14
6 Integrating Cisco Unity with the Phone System 6-1
Overview 6-1
How an Integration Works 6-2
Lines and Cables to Make Physical Connections 6-3
Settings in the Phone System and in Cisco Unity 6-7
Call Information Exchanged by the Phone System and Cisco Unity 6-7
Call Control 6-8
Sample Path for a Call from the Phone System to a Subscriber 6-8
OL-14619-01
General Integration Issues 6-9
Integrating with Cisco Unified Communications Manager (by Using SCCP or SIP) 6-10
Integrating Cisco Unity with Multiple Versions of Cisco Unified Communications Manager 6-11
Integrating Cisco Unity with Multiple Cisco Unified Communications Manager Clusters 6-12
Design Guide for Cisco Unity Release 5.x
v
Contents
Cisco Unified Communications Manager Authentication and Encryption for Cisco Unity Voice
Messaging Ports (SCCP Integrations Only)
6-12
Packetization (SCCP Integrations Only) 6-17
Integrating with Cisco Unified Communications Manager Express (by Using SCCP or SIP) 6-17
Multiple Cisco Unified Communications Manager Express Version Support 6-18
Multiple Cisco Unified Communications Manager Express Routers Integrating with a Single
Cisco Unity Server
6-19
Integrating Cisco Unity with Cisco Survivable Remote Site Telephony (Cisco SRST) 6-19
Integrating by Using SIP 6-22
Supported SIP Integrations 6-23
Cisco Unity Failover with SIP Trunks 6-23
SIP Compliance 6-23
Integrating with Circuit-Switched Phone Systems by Using PIMG or TIMG Units 6-24
Description of PIMG Integrations 6-24
Description of TIMG Integrations 6-26
Setup and Configuration 6-27
Firmware Updates 6-27
Serial Integrations 6-27
Increasing Port Capacity 6-28
Cisco Unity Failover 6-28
Cisco Unity Failback 6-29
Multiple Integration Support/Branch Office Consolidation 6-29
CHAPTER
Integrating with Multiple Phone Systems 6-30
Requirements for Integrations with Multiple Phone Systems 6-31
Using SCCP Phone Systems with Other Integrations 6-31
Notes for PIMG Integrations 6-31
Optional Integration Features 6-32
Alternate Extensions 6-32
Alternate MWIs 6-33
Centralized Voice Messaging 6-34
7 Cisco Unity Failover and Standby Redundancy 7-1
Comparison of Cisco Unity Failover and Standby Redundancy 7-1
Failover 7-1
Configuring Failover When Cisco Unity Servers Are Separated by a Firewall 7-2
Installing Exchange 2003 on the Cisco Unity Secondary Server in a Voice Messaging Configuration
with Failover
7-2
Requirements for Spanning a Cisco Unity Failover Pair Across Redundant Data Centers 7-2
Standby Redundancy 7-2
vi
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Installing Exchange 2003 on the Cisco Unity Primary Server in a Standby Redundancy
Configuration
7-3
Diagram of a Standby Redundancy Configuration 7-5
Contents
CHAPTER
CHAPTER
I
NDEX
8 Voice-Recognition Access to Cisco Unity 8-1
9 Migrating to Cisco Unity from Another Voice-Messaging System 9-1
OL-14619-01
Design Guide for Cisco Unity Release 5.x
vii
Contents
viii
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Preface
See the following sections:
• Audience, page ix
• Document Conventions, page ix
• Additional Cisco Unity Documentation, System Requirements, and Supported Hardware and
Software, page x
• Support Policy for Optional Third-Party Software, page x
• Obtaining Documentation, Obtaining Support, and Security Guidelines, page xi
Audience
The Design Guide for Cisco Unity Release 5.x is intended for anyone responsible for the design or
configuration of a Cisco
Document Conventions
Unity system.
OL-14619-01
The Design Guide for Cisco Unity Release 5.x uses the following conventions:
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
Caution Means reader be careful. In this situation, you might do something that could result in equipment damage
or loss of data.
Design Guide for Cisco Unity Release 5.x
ix
Preface
Additional Cisco Unity Documentation, System Requirements,
and Supported Hardware and Software
For descriptions and the URLs of Cisco Unity documentation on Cisco.com, see the Documentation
Guide for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_documentation_roadmaps_list.ht
ml.
In particular, note:
• For system requirements, and lists of supported hardware and software, the System Requirements for
Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
• For a list of servers that meet Cisco Unity specifications, the Cisco Unity Supported Platforms List,
at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.
• For client workstations, a list of the software that is compatible with the version of Cisco Unity that
you are installing, and a list of messaging clients that are compatible with the version of Cisco
that you are installing, the Compatibility Matrix: Cisco
Workstations at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_tables_list.ht
ml.
Unity. The document is shipped with Cisco Unity and is available at
Unity Release 5.0 at
Unity
Unity and the Software on Subscriber
Support Policy for Optional Third-Party Software
The Cisco support policy states that customers can deploy third-party software for backup, monitoring,
and security on the Cisco
integration partners) will have tested the interoperability of such products with Cisco
products are deployed. Such testing is essential in mitigating the risk that problems between Cisco
and the third-party products loaded on the Cisco
environment.
If a customer calls the Cisco Technical Assistance Center (TAC) with a problem, a Cisco TAC engineer
may require that optional third-party software be turned off or even removed from the Cisco
during the course of troubleshooting. If it is determined that the interoperability between the third-party
software and Cisco
the third-party software be disabled or removed from the Cisco
issue is addressed so that the customer can continue to have a functional Cisco
Before installing any qualified optional Microsoft service pack on the Cisco Unity server, confirm that
the manufacturer of any optional third-party software or hardware that you plan to install on the
Cisco
Unity server—or that is already installed—also supports the service pack for use with its product.
Unity server. However, Cisco expects that customers (or their systems
Unity server will be discovered within the production
Unity was the root cause of the problem, the Cisco TAC engineer will require that
Unity server until the interoperability
Unity before the
Unity
Unity server
Unity system.
Design Guide for Cisco Unity Release 5.x
x
OL-14619-01
Preface
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco
What’s
New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws
governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors
and users are responsible for compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local
laws, return this product immediately.
documents, see the monthly
A summary of U.S. laws governing Cisco cryptographic products can be found at
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html. If you require further assistance, contact us by
sending e-mail to export@cisco.com.
OL-14619-01
Design Guide for Cisco Unity Release 5.x
xi
Preface
xii
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Design Guide Overview
The following table lists the feature areas that affect the design of a Cisco Unity system and, for each
area, the location where you will find more information (either in this guide or in other Cisco
documentation). Note that for some features, documentation that covers only system design is not
available; therefore, the location listed is for feature documentation.
Product Area Design or Feature Documentation
Cisco Unity concepts Chapter 2, “Cisco Unity Concepts”
Network infrastructure
requirements
Cisco Unity with Microsoft
Exchange as the message store
Cisco Unity with IBM Lotus
Domino as the message store
Integrating Cisco Unity with
the phone system
Cisco Unity failover and
standby redundancy
Chapter 3, “Network Infrastructure Requirements”
Chapter 4, “Designing a Cisco Unity System with Exchange as the Message Store”
Chapter 5, “Designing a Cisco Unity System with Domino as the Message Store”
• Chapter 6, “Integrating Cisco Unity with the Phone System”
• If Cisco Unity will be integrated with Cisco Unified Communications Manager (CM)
(formerly known as Cisco Unified CallManager), see the applicable Cisco Unified
SRND at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_de
sign_guides_list.html.
Chapter 7, “Cisco Unity Failover and Standby Redundancy”
CHA PTER
1
Unity
CM
OL-14619-01
Design Guide for Cisco Unity Release 5.x
1-1
Chapter 1 Design Guide Overview
Product Area Design or Feature Documentation
Interoperating with or
migrating from other
voice-messaging systems
• For information on interoperating with Avaya voice-messaging systems, see the
following documents:
–
The Design Guide for Cisco Unity Bridge at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_implementati
on_design_guides_list.html.
–
The applicable Networking Guide for Cisco Unity Bridge at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide
s_list.html.
• For information on interoperating with other voice-messaging systems, see the
applicable Networking Guide for Cisco
Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_li
st.html.
• For information on migrating from another voice-messaging system to Cisco Unity, see
Chapter 9, “Migrating to Cisco Unity from Another Voice-Messaging System.”
Security For information on security for Cisco Unity, see the applicable version of the Security Guide
for Cisco
Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.h
tml.
Speech recognition Chapter 8, “Voice-Recognition Access to Cisco Unity”
Client access to voice
messages
• For end-user documentation on how Cisco Unity subscribers access Cisco Unity voice
messages and change their own Cisco
Unity settings, see the Cisco Unity End-User
Guides section of the Cisco website at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_user_guide_list.ht
ml.
• For information on setting up subscriber workstations, see the “Setting Up Subscriber
Workstations” chapter in the applicable version of the System Administration Guide for
Cisco
Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_l
ist.html.
• For information on subscriber orientation, see the “Subscriber Orientation” chapter in
the applicable version of the System Administration Guide for Cisco
Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_l
ist.html.
• For information on authentication for Cisco Personal Communications Assistant (PCA),
see the “Authentication for Cisco
Guide for Cisco
Unity at
Unity Applications” chapter of the applicable Security
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_l
ist.html.
Using Groupwise For information on using Novell GroupWise to access Cisco Unity voice messages, see the
Sending and receiving faxes
for Cisco
Unity subscribers
website for the third-party application GW-Unify,
For information on:
• The IP Fax Configuration wizard, see
http://www.gwipt.com.
http://ciscounitytools.com/App_IPFaxConfigurationWizard.htm.
• Configuring Cisco Unity to work with external fax servers that support Exchange and/or
Domino, see
Design Guide for Cisco Unity Release 5.x
1-2
http://ciscounitytools.com/App_ThirdPartyFaxConfig.htm.
OL-14619-01
Chapter 1 Design Guide Overview
OL-14619-01
Design Guide for Cisco Unity Release 5.x
1-3
Chapter 1 Design Guide Overview
1-4
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Cisco Unity Concepts
• How Cisco Unity Works, page 2-1
• Characteristics of Unified Messaging and Voice Messaging Systems, page 2-2
• Hardware Components of a Cisco Unity System, page 2-3
• Software Components of a Cisco Unity System, page 2-6
• Where Cisco Unity Stores Data, page 2-6
How Cisco Unity Works
Cisco Unity is a unified messaging system that can also be a voice messaging system, and it requires a
dedicated messaging infrastructure. When Cisco
Cisco
Unity answers the phone and takes voice messages for them. The subscribers can retrieve their
messages over the phone, or by using IBM Lotus Notes, Microsoft Outlook, the Cisco
Cisco Unified Personal Communicator, or an IMAP client.
CHA PTER
Unity subscribers are busy or away from their phones,
2
Unity Inbox,
When a call comes in for a subscriber, the following occurs:
1. A caller dials the subscriber extension. If the subscriber phone is busy or the subscriber does not
answer, the phone system routes the call and information about the call, including the subscriber
extension, to Cisco
2. Cisco Unity answers the call, looks up the subscriber extension in the Cisco Unity database,
retrieves and plays the subscriber greeting (“Hi, this is Pat, and I am not at my desk right now...”),
and lets the caller leave a message.
3. When the caller ends the call, the message is temporarily saved on the hard disk on the Cisco Unity
server.
4. Cisco Unity gives the message to Domino or Exchange, which routes the message to the subscriber
home server and stores it in the subscriber mailbox. If the call is from:
–
Another subscriber, the message is identified as coming from that person.
–
An outside caller who has not logged on to Cisco Unity as a subscriber, the message is identified
as coming from the Unity Messaging System mailbox.
5. Cisco Unity informs the subscriber in one or more of the following ways that a message has arrived,
regardless of the source of the call. (This is unlike some voice messaging systems, which activate
message waiting indicators only when a message is left over the phone.)
–
If the subscriber has a phone connected to the phone system, Cisco Unity activates the
subscriber message waiting indicator (MWI).
Unity.
OL-14619-01
Design Guide for Cisco Unity Release 5.x
2-1
Chapter 2 Cisco Unity Concepts
Characteristics of Unified Messaging and Voice Messaging Systems
Note This is true unless the MWI had already been activated because of a prior message arrival,
in which case it simply remains activated.
–
If the subscriber has configured personal notification options in the Cisco Unity Assistant,
Cisco
Unity can also call one or more phones or pagers, send an e-mail to a text pager, or send
an SMS message to a mobile phone to notify the subscriber that a new voice message has
arrived.
Characteristics of Unified Messaging and Voice Messaging
Systems
Cisco Unity can be configured either for Cisco Unity Unified Messaging or for Cisco Unity Vo i c e
Messaging. This section enumerates the characteristics of each configuration.
Unified Messaging
• Cisco Unity voice messages are stored in the same IBM Lotus Domino or Microsoft Exchange
message store in which e-mails and faxes (if applicable) are stored, so subscribers see all e-mails,
voice messages, and faxes in the same Inbox.
• A supported version of IBM Lotus Domino or Microsoft Exchange must be installed on a separate
server. (For information on supported versions, see System Requirements for Cisco
Release
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
• The Cisco Unity server is connected to the network, so it has access to the message store, the
directory (a Domino address book or Active Directory), and network utilities such as virus checking
and backup.
• Subscribers check messages:
–
–
• Cisco Unity administration can be performed over the network.
• Subscribers have access to the Cisco Unity Assistant through the Cisco PCA.
• Voice mail and e-mail attributes on subscriber accounts can be administered from a single location
by using the Cisco
Unity
5.0 at
With Domino, by using the phone or an e-mail client.
With Exchange, by using the phone, the Cisco Unity Inbox, or an e-mail client. (The
Cisco
Unity Inbox is accessed through the Cisco Personal Communications Assistant, or
Cisco
PCA.)
Unity Administrator.
• Cisco Unity can play back electronic messages over the phone by using Text to Speech, and can
Voice Messaging
Revised May 6, 2008
• Voice messages are stored in a supported version of Microsoft Exchange or IBM Lotus Domino.
Design Guide for Cisco Unity Release 5.x
2-2
support identifying, redirecting, and printing third-party faxes.
OL-14619-01
Chapter 2 Cisco Unity Concepts
Hardware Components of a Cisco Unity System
The message store contains only Cisco Unity voice messages, not e-mails or faxes.
Exchange can be installed either on the Cisco Unity server or on a separate server, depending on the
number of subscribers that need to be supported by Cisco
Unity. Domino must be installed on a
separate server.
• Subscribers check messages:
–
With Domino or Exchange, by using the phone or Cisco Personal Communicator.
–
With Exchange, by using the Cisco Unity Inbox (accessed through the Cisco PCA) or an IMAP
e-mail client.
• E-mail attributes, if any, and voice mail attributes on subscriber accounts must be administered
separately.
• Cisco Unity can play back electronic messages over the phone by using Text to Speech, and can
support identifying, redirecting, and printing third-party faxes.
Hardware Components of a Cisco Unity System
See the following sections:
• Cisco Unified Communications Manager or Another Supported Phone System, page 2-3
• One or More Cisco Unity Servers, page 2-4
• Voice Cards or PIMG Units (Required for Integrations with Circuit-Switched Phone Systems),
page 2-4
• Expansion Chassis (Required Only for Some Integrations with Circuit-Switched Phone Systems),
page 2-4
• One or More Message-Store Servers (Optional for Some Configurations), page 2-5
• One or More Dedicated Domain Controllers/Global Catalog Servers (Exchange Only, Large Voice
Messaging Configurations Only), page 2-5
• Cisco Unity Bridge Server (Required Only for Interoperating with Avaya Voice Messaging
Systems), page 2-5
• Network Connection (Optional for Some Configurations), page 2-5
Cisco Unified Communications Manager or Another Supported Phone System
Cisco Unity can be integrated with Cisco Unified Communications Manager (Cisco Unified CM) or
another supported phone system. For a list of supported phone systems, see the applicable version of
Supported Hardware and Software, and Support Policies for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
For integrations with circuit-switched phone systems, the customer may require special cables, line
splitters, and so on. For more information, see the integration guide for the phone system that the
customer uses. Cisco
Unity integration guides are available at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_g
uides_list.html.
Unity at
OL-14619-01
Design Guide for Cisco Unity Release 5.x
2-3
Hardware Components of a Cisco Unity System
Cisco Unity can also be integrated with multiple telephone systems. For more information, see the
Multiple Telephone System Integrations Guide for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_g
uides_list.html.
One or More Cisco Unity Servers
For a detailed list of servers that are qualified for use with Cisco Unity, see the Cisco Unity Supported
Platforms List at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.
Each qualified Cisco Unity server can service a specified number of Cisco Unity subscribers depending
on the type of server and, for Voice Messaging configurations, depending on whether Exchange is
installed on the Cisco
subscribers can be serviced by each type of server.
For Unified Messaging configurations, at least one Cisco Unity server is required for each:
• Domino domain
• Exchange organization
Unity server. The Cisco Unity Supported Platforms List indicates how many
Chapter 2 Cisco Unity Concepts
Unity 5.0 at
If the customer purchases Cisco Unity failover, two Cisco Unity servers are required:
• The primary server, which takes calls the majority of the time; and
• The secondary server, which takes calls when the customer wants to perform maintenance on the
primary server or when the primary server stops functioning for any reason.
If the customer purchases Voice Recognition licenses, one voice-recognition server is required for each
Cisco
Unity server. For a list of servers that are qualified as voice-recognition servers, see the
Cisco
Unity Supported Platforms List at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.
Note Voice recognition is not supported with phone system integrations that use voice cards.
Voice Cards or PIMG Units (Required for Integrations with Circuit-Switched Phone Systems)
If the customer integrates Cisco Unity with a circuit-switched phone system, either voice cards or PIMG
units are required. For a list of supported voice cards, see the Supported Hardware and Software, and
Support Policies for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Unity Release 5.x at
Expansion Chassis (Required Only for Some Integrations with Circuit-Switched Phone Systems)
If the customer is integrating Cisco Unity with a circuit-switched phone system and needs more voice
2-4
cards than will fit in the Cisco
Cisco
Unity Supported Platforms List at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html for more
Design Guide for Cisco Unity Release 5.x
Unity server, an expansion chassis is required for the voice cards (see the
OL-14619-01
Chapter 2 Cisco Unity Concepts
Hardware Components of a Cisco Unity System
information). All voice cards must be installed in the expansion chassis; they cannot be split between the
server and the expansion chassis, because all of the cards must be connected to one another by using a
single H.100 cable.
One or More Message-Store Servers (Optional for Some Configurations)
For Cisco Unity systems configured for Unified Messaging, the message store software (IBM Lotus
Domino or Microsoft Exchange) must be installed on a server other than the Cisco
For Cisco Unity systems configured for Voice Messaging, Exchange can be installed on the Cisco Unity
server or on a separate server. Domino must be installed on a separate server.
The number of subscribers homed on the Cisco Unity server cannot exceed the maximum listed for that
type of server on the Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.
Unity Supported Platforms List at
Unity server.
One or More Dedicated Domain Controllers/Global Catalog Servers (Exchange Only, Large Voice Messaging Configurations Only)
For large Voice Messaging configurations, one or more dedicated domain controllers/global catalog
(DC/GC) servers may be required. For more information, see
Requirements.”
Chapter 3, “Network Infrastructure
Cisco Unity Bridge Server (Required Only for Interoperating with Avaya Voice Messaging Systems)
If the customer wants Cisco Unity to interoperate with an Avaya voice messaging system, a dedicated
Cisco
Unity Bridge server is required. For more information, see the following documents:
• For information on how Cisco Unity can send voice messages to Avaya and receive voice messages
from Avaya, see the applicable version of the Networking Guide for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
• For requirements for connecting Cisco Unity and Avaya, see the System Requirements, and
Supported Hardware and Software for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Unity Bridge at
Unity Bridge at
Network Connection (Optional for Some Configurations)
For Cisco Unity systems that are configured for Unified Messaging, a network connection is required.
For Cisco Unity systems that are configured for Voice Messaging, a network connection is required only
if the customer wants to do one or more of the following:
• Use Domino for the message store.
OL-14619-01
• Integrate Cisco Unity with an IP phone system (for example, Cisco Unified Communications
Manager).
• Administer Cisco Unity over the network.
Design Guide for Cisco Unity Release 5.x
2-5
Software Components of a Cisco Unity System
• Give subscribers access to Cisco Unity by using the Cisco Unity Assistant, the Cisco Unity Inbox,
an IMAP e-mail client, or Cisco Personal Communicator.
• Install Exchange on a separate server.
Note For a system with a large number of Cisco Unity subscribers, installing Exchange on a separate
server is required.
• Give the Cisco Unity server access to network utilities such as virus checking and backup.
Software Components of a Cisco Unity System
For information on the software installed on the Cisco Unity server, the supported versions of Domino
and Exchange, and the supported versions of client software, see the System Requirements for
Cisco
Unity Release 5.0 at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Chapter 2 Cisco Unity Concepts
Where Cisco Unity Stores Data
Cisco Unity stores data in a variety of locations, as described in the following sections:
• Voice Messages Are Stored in Domino or Exchange, page 2-6
• All Subscriber Information Is Stored in a SQL Server 2000 Database, page 2-7
• Some Subscriber Information Also Appears in the Domino Address Book or in Active Directory,
page 2-8
• Data That Appears in Both the SQL Server 2000 Database and in the Address Book/Directory Is
Automatically Synchronized, page 2-9
• Messages from Outside Callers Are Temporarily Stored on the Cisco Unity Server, page 2-10
• Some Subscriber Information and Configuration Settings Are Stored on the Cisco Unity Server,
page 2-10
• Some Configuration Settings Are Stored in the Registry, page 2-10
Voice Messages Are Stored in Domino or Exchange
Cisco Unity stores voice messages either in Domino mailfile databases or in Exchange message stores.
Domino
Cisco Unity stores voice messages in a user mail file database on the Domino server. Domino is installed
on one or more servers (never on the Cisco
mailboxes on other servers. A Cisco
Domino person document includes Cisco
Every Domino server that homes Cisco Unity subscribers must have IBM Lotus Domino Unified
Communications (DUC) for Cisco installed. At the time this document was written, DUC was available
only for Windows 2000 Server, Windows Server 2003, and AIX. For information on operating systems
Unity subscriber is someone who has a Domino mailbox and whose
Unity server); therefore, all subscribers have their Domino
Unity-specific information.
2-6
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Chapter 2 Cisco Unity Concepts
currently supported by DUC for Cisco, see the “Domino Requirements—Message Store” section of
System Requirements for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
Cisco Unity can service subscribers on multiple Domino servers. You specify one Domino server (the
partner Domino server) through which Cisco
Cisco Unity can also service subscribers on Domino clusters. If subscribers are homed on one or more
Domino servers in a cluster, every Domino server in the cluster on which there will be Cisco
subscribers must have DUC installed.
Exchange
Cisco Unity can store voice messages in supported versions of Exchange. For information on versions
of Exchange currently supported for use with Cisco
Store” section of System Requirements for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
For small Cisco Unity Voice Messaging configurations, Exchange can be installed on the Cisco Unity
server, and all Cisco
(Exchange can also optionally be installed on a separate server instead of, or in addition to, being
installed on the Cisco
and whose Active Directory account includes Cisco
For medium and large Cisco Unity Voice Messaging configurations and for all Unified Messaging
configurations, Exchange is installed on one or more separate servers instead of on the Cisco
server. For these configurations, subscribers can have their Exchange mailboxes on other Exchange
servers.
Where Cisco Unity Stores Data
Unity at
Unity communicates with the other Domino servers.
Unity
Unity, see the “Exchange Requirements—Message
Unity at
Unity subscribers can have their Exchange mailboxes on the Cisco Unity server.
Unity server.) A Cisco Unity subscriber is someone who has an Exchange mailbox
Unity-specific information.
Unity
Cisco Unity can service subscribers on multiple Exchange servers. You specify one Exchange server (the
partner Exchange server) through which Cisco
The partner Exchange server can either be the Cisco
Cisco
Unity server) or a separate server.
Unity communicates with the other Exchange servers.
Unity server (when Exchange is installed on the
For Exchange 2003, Cisco Unity can also service subscribers on both active/active and active/passive
clusters. Do not install Cisco
Unity on a server in an Exchange cluster.
All Subscriber Information Is Stored in a SQL Server 2000 Database
Cisco Unity stores all information about Cisco Unity subscribers, as well as selected Cisco Unity
configuration data, in a SQL Server 2000 or Microsoft Data Engine 2000 (MSDE 2000) database on the
Cisco
Unity server. (The number of voice ports on the Cisco Unity server and, therefore, the maximum
number of subscribers the server can support, determines whether data is stored in SQL Server 2000 or
in MSDE, which is fully compatible with SQL Server 2000.)
When two or more Cisco Unity servers are in the same Domino domain and monitoring the same address
book, or are in the same Active Directory forest, the SQL Server 2000 database on each Cisco
server also includes a small amount of information about all of the subscribers on the other Cisco
servers.
Storing subscriber data in a SQL Server 2000 database has the following benefits:
• Performance: Because the SQL Server 2000 database is on the Cisco Unity server itself and
because the data is heavily indexed, accessing data—including looking up subscriber extensions—is
fast. The current maximum number of Cisco
Directory Global Address List is 250,000.
Unity subscribers in a Domino address book or Active
Unity
Unity
OL-14619-01
Design Guide for Cisco Unity Release 5.x
2-7
Chapter 2 Cisco Unity Concepts
Where Cisco Unity Stores Data
• Reliability: Because subscriber data is stored on the Cisco Unity server, Cisco Unity can answer
calls, let outside callers look up subscriber extensions, and take messages even when the Domino or
Exchange network is down. (When the Domino or Exchange network is unavailable, new messages
are stored on the Cisco
• Scalability: SQL Server 2000 was designed to support the largest enterprise data processing
systems, so there is more than enough room for storing the Cisco
storage limitations that SQL Server does not, it is also more than adequate for the Cisco
configurations for which it is sold.
• Network Impact: Only a small subset of subscriber information needs to be stored in the directory,
and that information does not change frequently. Therefore, directory replication caused by changes
to Cisco
Unity data is minimal after subscriber accounts have been created.
Unity server, and subscribers have access to those messages.)
Unity data. Although MSDE has
Unity
Some Subscriber Information Also Appears in the Domino Address Book or in Active Directory
A small amount of data that appears in the SQL Server 2000 database also appears in the Domino address
book or in Active Directory. This information, mostly subscriber data (including the recorded voice
name), is added to the directory to enable Cisco
enable communication between Cisco
directory monitor to keep the data in the directory synchronized with the data in the SQL Server 2000
database.
Unity and other voice messaging systems. Cisco Unity uses a
Unity servers to communicate with one another and to
Replicating data to the Domino address book or to Active Directory requires some changes to the
directory. If the customer is using:
• Domino, IBM Lotus Domino Unified Communications (DUC) for Cisco must be installed on the
Domino servers that will home Cisco
addition, DUC for Cisco must be installed on the client workstation for each Cisco
which adds elements to the mail file for the client.
• Exchange, the Active Directory schema must be extended with a few Cisco Unity–specific
attributes. For information about the Active Directory schema extensions, see the applicable
Cisco
Unity Data and the Directory white paper at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.
Unity subscribers. This adds elements to the address book. In
Enabling Cisco Unity Servers to Communicate with One Another
When two or more Cisco Unity servers are added to the same Domino address book or Active Directory
forest, each Cisco
Cisco
Unity servers to communicate with one another, which lets you administer subscriber accounts on
all Cisco
regardless of the Cisco
If you configure multiple Cisco Unity servers to communicate with one another, two types of
Cisco
• A primary location object for each Cisco Unity server. This unique identifier contains the addressing
• Selected subscriber data. The stored properties include the Cisco Unity server with which each
Unity servers from a single location and lets callers leave messages for any subscriber,
Unity data are stored in the directory:
information that Cisco
contains one primary location object for each Cisco
Directory forest.
subscriber is associated, the subscriber extension, and a recording of the subscriber name.
Unity server serves a distinct group of subscribers. You can optionally configure the
Unity server with which the subscriber is associated.
Unity needs to route messages to other Cisco Unity servers. The directory
Unity server in the Domino domain or Active
Unity subscriber,
2-8
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Chapter 2 Cisco Unity Concepts
Where Cisco Unity Stores Data
The directory replicates the information to all Domino servers in the domain (for Domino) or domain
controllers and global catalog servers in the forest (for Exchange), which ensures that Cisco
the required access to information.
For detailed information on adding two or more Cisco Unity servers to the same Domino domain or
Active Directory forest, see the Networking Guide for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Unity at
Unity has
Enabling Communication (Interoperability) Between Cisco Unity and Other Voice Messaging Systems
Cisco Unity supports several methods for allowing communication between Cisco Unity and other voice
messaging systems:
• VPIM (Voice Profile for Internet Mail) is a digital protocol for transferring voice messages between
different voice messaging system. To send and receive voice messages by using VPIM, the customer
creates a delivery location object for each remote voice messaging system. The third-party voice
messaging server must adhere to the VPIM v2 protocol.
As with the primary location objects, which allow one Cisco Unity server to send messages to
subscribers who are associated with another Cisco
the information necessary for Cisco
are using another voice messaging system.
Unity subscribers to exchange voice messages with people who
Unity server, delivery location objects contain
• The Audio Messaging Interchange Specification analog (AMIS-a) protocol provides an analog
mechanism for transferring voice messages between different voice messaging systems. To send and
receive voice messages by using AMIS, the customer creates a delivery location object for each
remote voice messaging system.
• The Cisco Unity Bridge acts as a networking gateway between Cisco Unity servers and Octel
servers. The Bridge communicates with Octel servers by using the OctelNet analog protocol; it
communicates with Cisco
on the VPIM protocol, with proprietary extensions.
Because the servers use different protocols, the Bridge uses nodes to translate messages as
appropriate for each server. For the Octel node, the Cisco
contains the Octel server name, unique serial number, and phone number. For the Cisco
the Bridge maintains another table that contains the Cisco
number, and domain name. By using these two tables, the Cisco
example, receive a message from an Octel node, look up the routing information from the
Cisco
Unity node table, reformat the information for the destination Cisco Unity node, and then
send the message to the Cisco
For more information on how Cisco Unity works with other voice messaging systems, see the
Networking Guide for Cisco
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Unity servers by using the Digital Networking protocol, which is based
Unity Bridge maintains a table that
Unity node,
Unity server name, assigned serial
Unity Bridge server can, for
Unity node.
Unity at
Data That Appears in Both the SQL Server 2000 Database and in the Address Book/Directory Is Automatically Synchronized
OL-14619-01
Some Cisco Unity information is stored in both the SQL Server 2000 database and in the address
book/directory. This data can be changed both from within Cisco
information can be changed by using the Cisco
example, subscriber information can be changed by using Active Directory Users and Computers).
Unity Administrator), and from outside Cisco Unity (for
Unity (for example, subscriber
Design Guide for Cisco Unity Release 5.x
2-9
Chapter 2 Cisco Unity Concepts
Where Cisco Unity Stores Data
Because this information can be stored and changed in multiple locations, it must be regularly
synchronized. Cisco
that keep the directory synchronized with the SQL Server 2000 database. Every few minutes, the
directory monitor checks for new, changed, and deleted objects, and replicates the information.
When two or more Cisco Unity servers are added to the same Active Directory forest, a global catalog
monitor keeps the SQL Server 2000 database synchronized with the global catalog. This is how each
Cisco
Unity server gathers information on subscribers who are associated with other Cisco Unity
servers.
Because the amount of data stored in the directory is so small, the impact of replication between the SQL
Server 2000 database and the directory is minimal (except when the first Cisco
created by importing them in bulk from Exchange or from a text file).
Unity includes separate directory monitors for Domino and for Active Directory
Unity subscribers are
Messages from Outside Callers Are Temporarily Stored on the Cisco Unity Server
All messages from outside callers are temporarily stored on the Cisco Unity server before they are
forwarded to Domino or Exchange for storage in the subscriber mailbox. This allows Cisco
continue functioning when the network connection between the Cisco
Exchange servers is down, or when one or more Domino or Exchange servers are down.
Unity server and the Domino or
Unity to
While Domino, Exchange, and/or the network is offline, Cisco Unity can still answer calls, allow outside
callers to look up subscriber extensions, and record voice messages. During this time, subscribers who
check their voice messages hear the Unity Messaging Repository (UMR) conversation, which explains
that their Domino or Exchange server is not available, but lets them access voice messages left after the
problem started. When the Domino server, Exchange server, and/or the network is back on line, the voice
messages that were stored in the UMR are routed to the subscriber mailboxes. (In some cases when a
network connection or a Domino or Exchange server is down, subscriber-to-subscriber messages are also
treated as outside caller messages and stored on the Cisco
appropriate mailbox.)
Unity server until they can be delivered to the
Some Subscriber Information and Configuration Settings Are Stored on the
Cisco
Unity Server
Selected recordings and configuration settings are stored in files on the Cisco Unity server, including
subscriber greetings (“Hi, this is Pat and I am out of the office today...”), recorded voice names, and some
phone system integration settings.
Some Configuration Settings Are Stored in the Registry
Selected server-specific configuration settings are stored in the Windows registry, including some phone
system integration and logging settings.
2-10
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Network Infrastructure Requirements
See the following sections:
• Availability of Network Resources, page 3-1
• Using Firewalls with Cisco Unity, page 3-3
• Sizing and Scaling Cisco Unity Servers, page 3-3
• Audio Codecs, page 3-5
Availability of Network Resources
The following network resources must be available at all times and in close physical proximity to
Cisco
Unity (over a local area network, not a wide area network), or Cisco Unity functionality will be
impaired:
• All name resolution hosts used by standard Windows networks, including DNS hosts. See the “Name
Resolution” section on page 3-1.
CHA PTER
3
• Domain controllers that provide authentication for the Cisco Unity service accounts. Windows
• Message store servers. Each message store server on which Cisco Unity subscribers are homed must
• Active Directory or the Domino directory. See the applicable chapter in this guide:
Name Resolution
Cisco Unity must be able to find the servers it interacts with by resolving the names of those servers to
IP addresses, unless the Cisco
can send messages from outside callers to the message store server on which the mailbox of the recipient
is homed only if Cisco
• A subscriber uses the Cisco Unity telephone user interface (TUI) to listen to messages or send
global catalog servers are also necessary if Cisco
Controller Access and Availability” section on page 3-2.
be accessible to Cisco
–
Designing a Cisco Unity System with Exchange as the Message Store
–
Designing a Cisco Unity System with Domino as the Message Store
messages to other subscribers. Name resolution is used by Cisco
the Unity application to execute commands that leave the Cisco
across the network to the mailbox stores where subscriber mailboxes are located.
Unity. See the “Availability of Message Store Servers” section on page 3-2.
Unity server is not connected with the network. For example, Cisco Unity
Unity can find that message store server. Name resolution is also used when:
Unity services Exchange. See the “Domain
Unity whenever a process requires
Unity server and access information
OL-14619-01
Design Guide for Cisco Unity Release 5.x
3-1
Availability of Network Resources
• Administrators access the Cisco Unity Administrator from other servers, which is primarily done
when using the administrative web interfaces. Typically, if a server name is used instead of an IP
address, the server name must be resolved to an IP address before access can occur over the network.
• Subscribers access the Cisco Unity Assistant or the Cisco Unity Inbox. Typically, if a server name
is used instead of an IP address, the server name must be resolved to an IP address before access can
occur over the network.
The Cisco Unity server must use Dynamic DNS (DDNS) or another version of DNS that supports
dynamic updates as described on the Microsoft website. Simply creating a host file on the Cisco
server is not sufficient.
When Domino is the message store, note the following:
• If Notes clients are using Notes Name Resolution, Cisco Unity must also use Notes Name
Resolution through the Notes client that is installed on the Cisco
the Windows domain controller in the domain to which the Cisco
• You can install the Windows DNS service on the Cisco Unity server in either a Unified Messaging
or a Voice Messaging configuration. With Domino, the Cisco
Windows domain controller to service Domino Notes clients via DUC. This is a Cisco
requirement, not a DUC requirement. The Cisco
Domino.
Chapter 3 Network Infrastructure Requirements
Unity
Unity server. DDNS is required on
Unity server belongs.
Unity server is configured as a
Unity
Unity server supports its own dedicated domain for
When Exchange is the message store, note the following:
• The DDNS server must be accessible by Cisco Unity and the supporting Exchange servers.
• In a Voice Messaging configuration with failover, install the Windows DNS service on the
Cisco
Unity secondary failover server or on a dedicated DC/GC server.
• In a Voice Messaging configuration without failover, when the Cisco Unity server is a Windows
domain controller and all other servers in the domain are Exchange servers that are used only to
support Cisco
configuration, the Cisco
• In a Unified Messaging configuration when Exchange is the message store, do not install the
Windows DNS service on the Cisco
Unity, install the Windows DNS service on the Cisco Unity server. In this
Unity server supports its own dedicated domain for Exchange.
Unity server.
Domain Controller Access and Availability
For all configurations and all message stores, Cisco Unity must have access to a Windows domain
controller to authenticate service accounts and, when Exchange is the message store, to authenticate
subscribers.
When Domino is the message store, subscribers can be authenticated for GUI-based access to
Cisco
Unity by using either Windows authentication or Domino authentication; Domino authentication
does not require access to a Windows domain controller.
Availability of Message Store Servers
When Cisco Unity is installed, the installer specifies one Domino or Exchange server that Cisco Unity
connects with; this is known as the partner Domino server or the partner Exchange server. The partner
server is the home of the Cisco
mailbox is the mailbox that originates voice messages from outside callers. The partner server is also the
home for default mailboxes and distribution groups (Cisco
Design Guide for Cisco Unity Release 5.x
3-2
Unity system mailbox (alias: Unity_<ServerName>. The Unity system
Unity distribution lists) that are created
OL-14619-01
Chapter 3 Network Infrastructure Requirements
during installation. If Cisco Unity subscribers are homed on servers other than the partner Exchange
server or the Domino mail drop server, all voice messages from outside callers pass through the partner
server or the mail drop server on their way to the home servers for Cisco
When the partner Exchange server, the mail drop Domino server, or a message store server on which
Cisco
Unity subscribers are homed is unavailable, Cisco Unity functionality is affected in the following
ways:
• Messages from outside callers are stored on the Cisco Unity server in the Unity Message Repository
(UMR), and can be retrieved during the outage. However, voice messages that were previously
received by subscribers are not available until the home server is back online.
• When the home server of a calling subscriber is down, any messages from that subscriber are stored
on the Cisco
• Message waiting indicators and message notification will not work.
Tip Make sure that the importance of message store availability is clearly understood prior to installing one
or more Cisco Unity servers, particularly those that service message stores on separate servers.
Using Firewalls with Cisco Unity
Unity subscribers.
Unity server in the UMR, and can be retrieved by the recipient during the outage.
Using Firewalls with Cisco Unity
Revised May 6, 2008
Cisco Unity can coexist with firewalls. However, note that Cisco Unity should never be deployed outside
of a firewall. Doing so can expose the Cisco
if the server is hardened.
For detailed firewall requirements, see the following sections in the System Requirements for
Cisco
Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html:
• “Network Requirements”
• “Failover Requirements for Separating Cisco Unity Servers by a Firewall”
• “Standby Redundancy Requirements for Separating Cisco Unity Servers by a Firewall”
Unity server to unwanted intrusion from the Internet, even
Sizing and Scaling Cisco Unity Servers
When sizing a Cisco Unity server, follow these guidelines:
• Maximum Number of Users on Dedicated Domino or Exchange Servers, page 3-4
• Storage Capacity for Voice Messages, page 3-4
• Number of Voice Ports, page 3-4
For a list of servers that meet Cisco Unity specifications, see the Cisco Unity Supported Platforms List
at
http://cisco.com/en/US/products/sw/voicesw/ps2237/products_data_sheets_list.html.
OL-14619-01
Design Guide for Cisco Unity Release 5.x
3-3
Chapter 3 Network Infrastructure Requirements
Sizing and Scaling Cisco Unity Servers
Maximum Number of Users on Dedicated Domino or Exchange Servers
You should not allow the Domino or Exchange servers to service the maximum number of Domino or
Exchange users that IBM Lotus or Microsoft allow. In addition, servers qualified by Cisco as Exchange
message store servers for use with Cisco
customer should not allow the number of users on these servers to reach the maximum.
You should also be careful not to exceed the disk capacity for the information store. For example, in
order to enable recovery if the information store is corrupted, Microsoft recommends that the total size
of an Exchange information store never exceed 50 percent of the capacity of the drive on which the
information store is installed. For more information, see the Microsoft website.
Unity have a maximum number of Exchange users, and the
Storage Capacity for Voice Messages
For Cisco Unity systems that are configured for Voice Messaging, base the server requirements on the
total number of voice storage minutes required for each subscriber. A supported Cisco
generally provides storage for 20 to 30 minutes of voice messages per subscriber for the maximum
number of subscribers supported on that server.
Unity server
For Cisco Unity systems that are configured for Unified Messaging, it is not possible to base server
requirements on the total number of voice storage minutes required for each subscriber, because the
message store also includes e-mail messages and possibly faxes. However, you can calculate the storage
requirement for the desired number of voice storage minutes and add that to the current mailbox limits.
If the customer is replacing an existing voice messaging system with Cisco Unity, it may be possible to
obtain information from the existing system on the average number of minutes of voice messages that
subscribers currently have. You can then multiply the average number of minutes by the recording size
per minute—according to the codec that Cisco
average amount of disk space required for voice messages per subscriber.
Start with a one-to-one correlation of legacy voice messaging system to Cisco Unity. If the legacy
system handles a larger capacity than the largest Cisco
subscriber population onto more than one Cisco
is not necessary to segment subscribers onto backend message stores by extension number ranges or
prefixes but it may be easier to manage.
For more information, see the “How Codecs Affect the File Size of Voice Messages” section on page 3-5.
Number of Voice Ports
To determine the number and configuration of voice ports required, you can start with the existing voice
messaging system, if applicable. This may give you some idea how many ports are required for taking
voice messages, for turning message waiting indicators on and off, and for message notification.
In a Unified Messaging configuration, Cisco Unity uses telephone record and playback (TRAP), to allow
subscribers who use Notes or Outlook for voice messaging to play and record voice messages over the
phone rather than by using speakers and a microphone. This feature is especially desirable when
subscribers work in cubicles, where there is a lack of privacy. However, when a subscriber plays or
records a message by using TRAP, a port on the Cisco
subscriber uses speakers and a microphone to play and record messages.) If the customer wants
subscribers to use TRAP, calculations for the total number of voice ports required will need to take this
into account.
Unity will use to record messages—to arrive at the
Unity server, consider splitting the legacy
Unity server by extension number ranges or prefixes. It
Unity server is used. (No port is used when a
3-4
For Cisco Unity failover, the primary and secondary servers must have the same number of ports.
Design Guide for Cisco Unity Release 5.x
OL-14619-01
Loading...