Cisco With Microsoft Exchange User Manual

Networking Guide for Cisco Unity (With Microsoft Exchange)

Release 5.x September, 2007

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-13844-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

CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco

Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath 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. (0709R)

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.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Preface ix

Purpose ix

Audience ix

Document Conventions ix

Cisco Unity Documentation x

Obtaining Documentation, Obtaining Support, and Security Guidelines x

Cisco Product Security Overview xi

CHAPTER

1 Networking in Cisco Unity 1-1

Overview: Networking in Cisco Unity 1-1

Networking Options 1-1

Message Addressing Options 1-2

Locations and External Subscribers 1-3

Voice Connector 1-4

Active Directory Schema Extensions 1-4

Comparison of AMIS, Bridge, and VPIM Networking 1-5

Road Map to the Networking Documentation: Where to Go from Here 1-13

2 Digital Networking 2-1

Overview: Digital Networking 2-1

Requirements for Setting Up Digital Networking 2-1 Licenses and License Pooling 2-2 In This Chapter 2-2

Setting Up Digital Networking 2-3

Prerequisites 2-3 Task List: Setting Up Digital Networking 2-3

OL-13844-01

Procedures for Setting Up Cisco Unity to Use Digital Networking 2-4

Enabling License Pooling (Optional) 2-4 Customizing the Primary Location 2-6 Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes 2-6 Setting Up Identified Subscriber Messaging Between Networked Cisco Unity Subscribers

(Optional)

2-8

Modifying the All Subscribers Public Distribution List 2-10

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

iii

Contents

Setting Up System Broadcast Messaging for Sending to All Subscribers in the Directory (Optional)

2-10

Changing the Default Search Scope for the Cisco PCA (Optional) 2-11 Enabling Live Reply Between Cisco Unity Servers in the Same Dialing Domain (Optional) 2-11 Testing the Digital Networking Setup 2-12

Digital Networking Concepts and Definitions 2-14

Locations and Digital Networking 2-15 Dialing Domains 2-15 Addressing Options for Non-Networked Phone Systems 2-18 Cisco Unity Administrator Scope 2-20 Granting Administrative Rights to Other Cisco Unity Servers 2-22 Distribution Lists 2-22 System Broadcast Messages 2-23

Notable Behavior 2-24

Mapping Subscribers to Cisco Unity Servers 2-25

CHAPTER

3 Cross-Server Logon, Transfers, and Live Reply 3-1

Overview of Cross-Server Logon, Transfer, and Live Reply 3-1

Phone System Considerations for Cross-Server Features 3-2 Planning for Increased Port Usage 3-3 A Brief Look at Cisco Unity Data Architecture 3-3

Cross-Server Logon 3-5

Prerequisites: Enabling Cross-Server Logon 3-6 Task List: Enabling Cross-Server Logon 3-6 Procedures: Enabling Cross-Server Logon 3-6

Cross-Server Transfer from the Automated Attendant and Directory Handlers 3-8

Prerequisites: Enabling Cross-Server Transfer 3-8 Task List: Enabling Cross-Server Transfer 3-9 Procedures: Enabling Cross-Server Transfer 3-9

Cross-Server Live Reply 3-12

Prerequisites: Enabling Cross-Server Live Reply 3-13 Task List: Enabling Cross-Server Live Reply 3-13 Procedures: Enabling Cross-Server Live Reply 3-14

Troubleshooting 3-15

CHAPTER

Dialing Domain Options Page Reference 3-16

4 Internet Subscribers 4-1

Overview: Internet Subscribers 4-1

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Prerequisites for Setting Up Internet Subscriber Accounts 4-1

Creating Internet Subscriber Accounts 4-2

Before Creating Internet Subscriber Accounts 4-2 Before Creating Trusted Internet Subscriber Accounts 4-4 Using the Cisco Unity Bulk Import Wizard to Create Multiple Internet Subscriber Accounts 4-6 Correcting Import Errors 4-8 Using the Cisco Unity Administrator to Create Internet Subscriber Accounts 4-9 Enabling Cross-Server Transfer for Internet Subscribers 4-10 After Creating Internet Subscriber Accounts 4-10

Internet Subscriber Concepts and Definitions 4-11

Subscriber Experience with Internet Subscribers 4-12 Deleting Internet Subscribers 4-12

Contents

CHAPTER

5 AMIS Networking 5-1

Overview: AMIS 5-1

Setting Up Cisco Unity to Use AMIS 5-1

Prerequisites 5-2 Considerations for Deploying AMIS with Cisco Unified Communications Manager and Cisco

Gateways

5-3

Task List: Setting Up Cisco Unity to Use AMIS 5-3

Procedures for Setting Up Cisco Unity to Use AMIS 5-4

Setting Up the Voice Connector for AMIS Networking 5-4 Creating the UAmis Account 5-8 Designating Voice Ports for Outbound AMIS Calls 5-11 Setting AMIS Delivery Options 5-11 Customizing the AMIS Restriction Table 5-11 Setting Up the AMIS Schedule 5-12 Customizing the Primary Location 5-12 Creating AMIS Delivery Locations 5-13 Creating AMIS Subscribers 5-16 Extending Identified Subscriber Messaging to Include AMIS Subscribers 5-22 Enabling Cross-Server Transfer for AMIS Subscribers 5-24

OL-13844-01

AMIS Concepts and Definitions 5-25

Introduction to AMIS 5-25 Port Usage and Schedules 5-26 UAmis Account 5-27 Voice Connector and AMIS Networking 5-28 Locations and AMIS Networking 5-29 Message Addressing Options 5-29

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Contents

Blind Addressing and AMIS Networking 5-30 AMIS Subscribers 5-31 Identified Subscriber Messaging 5-32 Live Reply to AMIS Subscribers 5-33 Deleting AMIS Subscribers 5-34 Extension Addresses 5-34 Determining How AMIS Subscribers Appear in the Outlook Address Book 5-34 Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity

Assistant

5-36

Migrating Subscribers from Another Voice Messaging System to Cisco Unity 5-37 Considerations for Networked Cisco Unity Servers 5-38

Maintenance 5-40

Monitoring AMIS Message Traffic 5-40 Moving the UAmis Mailbox 5-41

Troubleshooting 5-41

CHAPTER

Notable Behavior 5-41

Inbound Messages Are Delivered Only to Primary Extensions 5-42 Inbound Search Scope 5-42 Running the Voice Connector Setup Program in Another Language 5-42

6 Bridge Networking 6-1

7 VPIM Networking 7-1

Overview: VPIM Networking 7-1

Setting Up Cisco Unity to Use VPIM Networking 7-2

Prerequisites 7-2 Task List: Setting Up Cisco Unity to Use VPIM Networking 7-3

Procedures for Setting Up Cisco Unity to Use VPIM Networking 7-4

Making Design Decisions and Gathering Needed Information 7-4 Determining the Domain Name 7-5 Resolving Names with IP Addresses 7-5 Verifying Connectivity with the Remote Voice Messaging System 7-6 Extending the Active Directory Schema 7-8 Verifying the Recipient Policies or Creating a New One 7-9 Setting Up the Voice Connector for VPIM Networking 7-10 Creating the UVPIM Account by Using ConfigMgr.exe (Optional) 7-16 Customizing the Primary Location 7-18 Creating VPIM Delivery Locations 7-18 Creating VPIM Subscribers 7-22

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Customizing VPIM Subscriber Directory Update Settings 7-28 Extending Identified Subscriber Messaging to Include VPIM Subscribers 7-34 Gathering Information About Cisco Unity to Configure Another Voice Messaging System for

VPIM

7-36

VPIM Concepts and Definitions 7-36

Introduction to VPIM 7-37 VPIM Networking and Locations 7-40 VPIM Networking and the Voice Connector 7-40 Message Addressing Options 7-42 VPIM Networking and Blind Addressing 7-43 VPIM Subscribers 7-44 Automatic VPIM Subscriber Directory Updates 7-46 Identified Subscriber Messaging 7-52 Live Reply to VPIM Subscribers 7-53 Deleting VPIM Subscribers 7-54 Extension Addresses 7-54 Determining How VPIM Subscribers Appear in the Outlook Address Book 7-54 Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity

Assistant

7-55

Migrating Subscribers from Another Voice Messaging System to Cisco Unity 7-56 Considerations for Digitally Networked Cisco Unity Servers 7-57 Phone Prefixes 7-58 Audio Format Considerations 7-58

Contents

CHAPTER

OL-13844-01

Maintenance 7-59

Changing the IP Address of a Microsoft Exchange Server 7-60 Moving the UVPIM Mailbox 7-61

Notable Behavior 7-61

Call Transfer Settings and VPIM Subscribers 7-61 Inbound Messages Are Delivered Only to Primary Extensions 7-62 Inbound Search Scope 7-62 Running the Voice Connector Setup Program in Another Language 7-63

8 Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems 8-1

Messaging Between Cisco Unity Servers in Different Directories 8-1

Correspondence Between Locations 8-2 VPIM Subscribers Correspond to Remote Cisco Unity Subscribers 8-2 Audio Format Conversion Settings 8-3

Messaging Between Cisco Unity and Cisco Unity Express Servers 8-6

Correspondence Between Locations 8-6

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

vii

Contents

VPIM Subscribers Correspond to Cisco Unity Express Subscribers 8-6

Additional Functionality 8-7

Networked System Broadcast Messages 8-7

CHAPTER

9 Primary Location Settings 9-1

Overview: Primary Location Settings 9-1

Primary Location Profile Settings 9-1

Assigning Dial IDs 9-2

Primary Location Addressing Option Settings 9-3

Subscriber Addressing Options 9-4 Location Addressing Options 9-8

10 Upgrading and Uninstalling Networking Options 10-1

Overview 10-1

Upgrading with Digital Networking 10-1

Upgrading with AMIS Networking 10-1

Upgrading with VPIM Networking 10-2

Removing AMIS Networking 10-2

Procedures for Removing AMIS Networking 10-2

Removing VPIM Networking 10-3

Procedures for Removing VPIM Networking 10-4

CHAPTER

LOSSARY

NDEX

Uninstalling the Cisco Unity Voice Connector 10-4

Determining the Voice Connector Version 10-6

11 Migrating from SMTP Networking to VPIM Networking 11-1

Overview 11-1

Prerequisites 11-1

Task List for Migrating from SMTP Networking to VPIM Networking 11-2

Running the Stored Procedure to Convert VPIM Delivery Locations and Subscribers 11-3 Manually Converting VPIM Delivery Locations and Subscribers 11-4

viii

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Purpose

Audience

Preface

This preface describes the purpose, audience, and conventions of the Networking Guide for Cisco Unity, and provides information on how to obtain related documentation.

The Networking Guide for Cisco Unity introduces you to the various networking options available in Cisco

Unity, and explains how to set them up.

The Networking Guide for Cisco Unity focuses on Cisco Unity. It does not provide information on Microsoft Exchange, Microsoft Windows, and IBM Lotus Domino, or on configuring other voice messaging systems.

The Networking Guide for Cisco Unity is intended for system administrators and others responsible for setting up and managing Cisco working knowledge of Windows and of the message store (Domino or Exchange) in which voice messages are stored. If you are setting up Cisco systems, you need a working knowledge of those voice messaging systems.

Unity. If you are administering the Cisco Unity server, you need a

Unity to communicate with other voice messaging

Document Conventions

This guide uses the following conventions:

Ta b l e 1 Networking Guide for Cisco Unity Conventions

Convention Descriptions

boldfaced text Boldfaced text is used for:

OL-13844-01

• Key and button names. (Example: Click OK.)

• Information that you enter. (Example: Enter Administrator in the

User Name box.)

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Preface

Table 1 Networking Guide for Cisco Unity Conventions (continued)

Convention Descriptions

< >

(angle brackets)

(hyphen)

(right angle bracket)

The Networking Guide for Cisco Unity also uses the following conventions:

Angle brackets are used around parameters for which you supply a value. (Example: In the Command Prompt window, enter ping <IP address>.)

Hyphens separate keys that must be pressed simultaneously. (Example: Press Ctrl-Alt-Delete.)

A right angle bracket is used to separate selections that you make:

• On menus. (Example: On the Windows Start menu, click Settings >

Control Panel > Phone and Modem Options.)

• In the navigation bar of the Cisco Unity Administrator. (Example:

Go to the System > Configuration > Settings page.)

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.

Cisco Unity Documentation

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.

Unity. The document is shipped with Cisco Unity and is available at

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

documents, see the monthly

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Preface

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.

A summary of U.S. laws governing Cisco cryptographic products may 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-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Preface

xii

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Networking in Cisco Unity

Overview: Networking in Cisco Unity

In Cisco Unity, “networking” is the general term for messaging between Cisco Unity servers, and between Cisco that encompasses the following ideas:

• Subscribers associated with one Cisco Unity server can use the phone to send voice messages to:

–

• Unidentified callers can find any subscriber in the phone directory and leave a voice message.

Depending on the phone system and network configuration, unidentified callers who reach the Cisco even to the phone of a subscriber who is not associated with the local server.

See the following sections:

Unity and other voice messaging systems. The term networking has a broad definition

Subscribers associated with another Cisco Unity server.

Individuals with access to a computer connected to the Internet.

Individuals who use a voice messaging system other than Cisco Unity.

Unity automated attendant or directory assistance can be transferred to any subscriber phone,

CHAP T ER

• Networking Options, page 1-1

• Message Addressing Options, page 1-2

• Locations and External Subscribers, page 1-3

Networking Options

The main goal of networking in Cisco Unity is to deliver messages from a Cisco Unity server to a target, and to deliver messages from the target to Cisco are defined according to a combination of the message transport mechanism and the target, as shown in

Table 1-1.

Ta b l e 1-1 Networkin g Option s

Networking Option Description

Digital Networking Allows messaging among multiple Cisco Unity servers connected to a single, global directory.

That is, the Exchange partner servers must be in the same Active Directory forest. Message routing is done by Exchange.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Unity. The networking options available in Cisco Unity

1-1

Chapter 1 Networking in Cisco Unity

Message Addressing Options

Table 1-1 Networking Options (continued)

Networking Option Description

Internet Subscribers Allows messaging with individuals over the Internet or any TCP/IP network by using SMTP. The

recipient receives the message as an e-mail with a WAV attachment. Internet subscribers can have local extensions, recorded voice names, and greetings, and be listed in the directory, but they do not have mailboxes in the local Exchange network. Messages are addressed to Internet subscribers as they are to regular subscribers, but the messages are sent to the e-mail address that you specify when creating the Internet subscriber account.

Trusted Internet Subscribers

AMIS Allows messaging with other voice messaging systems that support the Audio Messaging

Bridge Allows messaging between Cisco Unity and an Octel system on an Octel analog network by using

VPIM Allows messaging with other voice messaging systems that support the Voice Profile for Internet

Trusted Internet subscribers are Internet subscribers that are trusted with decrypted secure messages. Trusted Internet subscribers must be associated with a Trusted Internet Location. Secure messages to Trusted Internet subscribers are decrypted by the Cisco Microsoft Exchange before they are sent by the Exchange server. (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)

Interchange Specification analog (AMIS-a) protocol. In essence, the sending voice messaging system calls the receiving voice messaging system, there is an exchange of DTMF tones as defined by the protocol, the sending system plays the message, and the receiving system records it.

the Cisco Cisco Messaging between Cisco by using SMTP. Messaging between the Octel servers and the Bridge is done by using the Octel analog networking protocol. The Bridge must be installed on a separate and dedicated platform.

Mail (VPIM) protocol. VPIM allows different voice messaging systems to exchange voice, text, and fax messages over the Internet or any TCP/IP network. VPIM is based on SMTP and the Multi-Purpose Internet Mail Extension (MIME) protocol. VPIM Networking can be used for messaging between Cisco Cisco systems.

Unity Bridge. The Cisco Unity Bridge acts as a networking gateway between

Unity and the Octel system, and allows the systems to exchange voice and fax messages.

Unity and the Bridge is done over the Internet or any TCP/IP network

Unity servers that access different directories, between Cisco Unity and

Unity Express, and between Cisco Unity with Exchange and Cisco Unity with Domino

Unity Voice Connector for

Message Addressing Options

With AMIS, Bridge, and VPIM Networking, you can set up different addressing options, as follows:

• Blind Addressing—With blind addressing, Cisco Unity has the information it needs to send

messages to the remote voice messaging system, even though the recipient mailbox number, text name, and recorded name are not in the directory.

• “External” Subscribers—You create AMIS, Bridge, and/or VPIM subscribers on the local

Cisco

Unity server to correspond to subscribers on the remote voice messaging system. These external subscribers (also referred to as “proxy users” or “remote subscribers”) can have local extensions, recorded voice names, and greetings, and can be listed in the directory. However, they do not have mailboxes in the local Exchange network. Messages are addressed to an external subscriber as they are to a regular subscriber, but the messages are sent to the applicable mailbox on the remote voice messaging system. External subscribers have corresponding Active Directory contacts.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-2

OL-13844-01

Chapter 1 Networking in Cisco Unity

• A Combination—The various ways of sending and receiving messages, as detailed in Tabl e 1-1, are

not mutually exclusive. For example, if the Cisco Unity servers in your organization are set up to access a global directory (and thus can make use of the Digital Networking option), you can still add Internet subscriber accounts for contractors working at home. In addition, if you are migrating users from an existing voice messaging system to Cisco VPIM connectivity to the mix. networking options.

Figure 1-1 Networking in Cisco Unity

Exchange

Cisco

Unity

Locations and External Subscribers

Unity in stages, you can add AMIS, Bridge, or

Figure 1-1 depicts a configuration that uses a mix of the various

Exchange

Cisco

Unity

SMTP

Connector

Exchange

Active Directory Forest

PSTN

Internet

Locations and External Subscribers

Regardless of which networking option you choose, the setup process is similar.

For each networking option, you customize the settings for the primary location. Each Cisco Unity server has a default or primary location, which is created during installation and which cannot be deleted. The primary location contains information that identifies the Cisco systems, which may or may not be Cisco

section on page 9-1 for more information.

To set up AMIS, Bridge, or VPIM Networking, you create delivery locations. A delivery location contains the network information that Cisco which may or may not be Cisco

Unity servers. You create a delivery location for each voice messaging

server with which the local Cisco

Unity systems. See the “Overview: Primary Location Settings”

Unity needs to send messages to other messaging servers,

Unity server will communicate.

Other voice

messaging system

Internet

subscriber

Unity server to other messaging

AMIS

69379

OL-13844-01

Note Trusted Internet Locations are a special type of delivery location. They do not contain information about

other messaging servers, but rather serve as a delivery location for Trusted Internet subscribers that are trusted with decrypted secure messages. Based on the configuration settings of the Trusted Internet

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-3

Voice Connector

Location, messages are decrypted by the Voice Connector before they are sent by Exchange over the Internet or any TCP/IP network via SMTP. (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)

Optionally, you can also create “external” subscribers (that is, AMIS, Bridge, and/or VPIM subscribers). The messages for external subscribers are stored externally to the Cisco When creating an external subscriber, you specify a delivery location that the external subscriber is associated with so that Cisco

Voice Connector

The Cisco Unity Voice Connector for Exchange is a Cisco Unity networking component that enables messaging between Cisco

The Voice Connector for Exchange 2000 can be used when your network consists only of Exchange 2000 or Exchange 2003 servers, or a mixture of Exchange 2000, Exchange 2003, and Exchange 2007 servers.

Caution The Voice Connector for Exchange 2000 can be installed on an Exchange 2000 server or an Exchange

2003 server, but it cannot be installed on an Exchange 2007 server.

Chapter 1 Networking in Cisco Unity

Unity voice message store.

Unity has the information it needs to send messages to them.

Unity servers and other voice messaging systems.

The Voice Connector performs the following functions:

• AMIS Networking—The Voice Connector routes voice messages to the applicable

UAmis_<Servername> mailbox for outgoing analog delivery. Incoming AMIS voice messages received by the Cisco

• Bridge Networking—The Voice Connector performs the message conversion and address translation

that allows Cisco

• VPIM Networking—The Voice Connector performs the message conversion and address translation

that allows Cisco messaging systems by using the VPIM protocol. VPIM Networking also provides messaging between:

–

Cisco Unity servers that access separate directories

–

Cisco Unity with Domino systems and Cisco Unity with Exchange systems

–

Cisco Unity and Cisco Unity Express

Note that the Voice Connector is not needed with Digital Networking because the Cisco Unity servers access the same directory.

The Voice Connector ships with Cisco Unity and is available on the Cisco Unity Voice Connector for Exchange Software Download page, at

http://www.cisco.com/cgi-bin/tablebuild.pl/unity-voice-connector.

Unity AMIS bridgehead are routed to the Voice Connector for processing.

Unity to exchange messages with the Bridge server.

Unity to exchange messages with other Cisco Unity servers or other voice

Active Directory Schema Extensions

1-4

A small subset of Cisco Unity data is stored in Active Directory. Therefore, before installing Cisco

Unity, the Active Directory schema must be extended. In addition to the schema extensions required before installing Cisco the following:

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Unity, the Active Directory schema must be extended before setting up

OL-13844-01

Chapter 1 Networking in Cisco Unity

Comparison of AMIS, Bridge, and VPIM Networking

• Bridge Networking

• VPIM Networking

The schema extensions needed to support Digital Networking and AMIS Networking are part of the general set of schema extensions for Cisco

Unity.

For detailed information about the data that is stored in the directory, see the following white papers:

Cisco

Unity Data and Active Directory (Cisco Unity 5.x and Later with Microsoft Exchange) and Active

Directory Capacity Planning (Cisco

Unity Version 5.x and Later with Microsoft Exchange). Both white

papers are available at

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html).

Comparison of AMIS, Bridge, and VPIM Networking

AMIS, Bridge, and VPIM Networking can be used for networking Cisco Unity with other voice messaging systems. However, there are several differences among these networking options, as described in the following sections:

• Interoperability

• General Connectivity Costs

• Supported Voice Gateways

• International Availability

• Blind Addressing

• Addressing by Name or by Extension

• Spoken Name Confirmation

• Audio Formats Supported

• Delivery Receipt/Read Receipt

• Directory Information Sharing

• Distribution Lists

• Mailbox ID Translation

• Fax Messaging

• Message Transport Time Considerations

• Private Messages

• Secure Messages

• Simultaneous Analog Sessions for Message Delivery to or from Remote Voice Mail Systems

• Urgent Messages

• System Broadcast Messages

OL-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-5

Chapter 1 Networking in Cisco Unity

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-2 Interoperability

AMIS Bridge VPIM

For the most up-to-date list of supported voice messaging systems, see the applicable Supported

Hardware and Software, and Support Policies for Cisco

Unity, at

http://www.cisco.com/en/US/ products/sw/voicesw/ps2237/ prod_installation_guides_list.html.

Ta b l e 1-3 General Connectivity Costs1

For the most up-to-date list of supported voice messaging systems, see the applicable System Requirements, and

Supported Hardware and Software for Cisco

Unity Bridge, at

http://www.cisco.com/en/US/products/ sw/voicesw/ps2237/prod_installation_ guides_list.html.

For the most up-to-date list of supported voice messaging systems, see the applicable Supported Hardware and

Software, and Support Policies for Cisco

Unity, at

http://www.cisco.com/en/US/products/ sw/voicesw/ps2237/prod_installation_ guides_list.html.

AMIS Bridge VPIM

License for the Cisco Unity server that functions as an AMIS bridgehead.

Analog ports on the Cisco Unity server. Connectivity can be made in one of two ways: by using voice cards, or through supported voice gateways. (See

Table 1-4.)

Analog lines for message delivery.

Applicable long distance charges if the Cisco

Unity bridgehead server and the remote voice messaging system are physically located in different areas.

1. Note that the costs shown in this table are associated with Cisco Unity. There may be additional connectivity costs associated with enabling AMIS, Octel Analog Networking, or VPIM for the voice messaging system with which Cisco

License for the Bridge server. (Note that a license is no longer required on the Cisco

Unity bridgehead server.)

A separate server for the Bridge software. Each server supports up to 24 ports.

Voice cards for the Bridge server.

Analog lines for message delivery between Bridge and Octel nodes.

Applicable long distance charges if the Bridge server and the Octel system are physically located in different areas.

SMTP network bandwidth for message delivery between the Bridge and Cisco

Unity.

Unity exchanges messages.

License for the Cisco Unity server that functions as a VPIM bridgehead.

SMTP network bandwidth for message delivery.

Ta b l e 1-4 Supported Voice Gateways

AMIS Bridge VPIM

For the most up-to-date list of supported voice gateways, see the applicable Supported Hardware and

Software, and Support Policies for Cisco

Unity, at

http://www.cisco.com/en/US/ products/sw/voicesw/ps2237/prod_

For the most up-to-date list of supported voice gateways, see the applicable System

Requirements, and Supported Hardware and Software for Cisco

Unity Bridge, at

http://www.cisco.com/en/US/products/ sw/voicesw/ps2237/prod_installation_ guides_list.html.

N/A.

installation_guides_list.html.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-6

OL-13844-01

Chapter 1 Networking in Cisco Unity

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-5 International Availability

AMIS Bridge VPIM

All countries in which Cisco Unity is sold.

For a list of countries for which there is a voice-fax card approved for use, see the

All countries in which Cisco Unity is

sold. “Supported Voice-Fax Cards” section in the System Requirements, and Supported

Hardware and Software for Cisco

Unity

Bridge, at

http://www.cisco.com/en/US/products/ sw/voicesw/ps2237/prod_installation_ guides_list.html.

Some deployments may service users in countries that are not on the “Supported Voice-Fax Cards for the Cisco

Unity Bridge Server” list, but only when the Bridge server itself is located in one of the countries listed.

The Bridge server is supported only when using the English-language version of Windows. The locale must be set to English (United States), and the language settings must be set only to Western Europe and United States. (Choosing additional language settings is not supported.) The Bridge software is not localized in any language other than English.

Ta b l e 1-6 Blind Addressing

AMIS Bridge VPIM

Available through the Cisco Unity Telephone User Interface (TUI), Cisco

Unity ViewMail for Microsoft

Outlook, and the Cisco

Ta b l e 1-7 Addressing by Name or by Extension

Unity Inbox.

Available through the Cisco Unity TUI, ViewMail, and the Cisco

Unity Inbox.

Available through the Cisco Unity TUI, ViewMail, and the Cisco

AMIS Bridge VPIM

Available through the Cisco Unity TUI, ViewMail, and the Cisco

Unity Inbox when AMIS subscribers exist in the Cisco

Unity directory.

Available through the Cisco Unity TUI, ViewMail, and the Cisco

Unity Inbox when Bridge subscribers exist in the Cisco

Unity directory.

Available through the Cisco Unity TUI, ViewMail, and the Cisco when VPIM subscribers exist in the Cisco

Unity Inbox.

Unity Inbox

Unity directory.

OL-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-7

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-8 Spoken Name Confirmation

AMIS Bridge VPIM

Available when a recorded voice name exists for the AMIS subscriber.

Voice names for AMIS subscribers must be recorded individually in the Cisco

Unity Administrator.

Voice names for AMIS subscribers can be imported by using the Cisco

Unity Bulk Import utility.

Available when a recorded voice name exists for the Bridge subscriber.

Voice names for Bridge subscribers can be recorded individually in the Cisco

Unity Administrator. However, because the Bridge supports directory information sharing, the text and recorded voice names of Octel subscribers are retrieved on a usage basis, and Bridge subscribers can be automatically created in the Cisco

Unity directory with the retrieved text and voice names. Similarly, the text and voice names of Cisco

Unity subscribers are retrieved by the Octel servers on a usage basis, and directory entries are automatically created on the Octel servers with the retrieved text and voice names.

Cisco Unity includes support for the automatic creation of VPIM subscribers. Therefore, the text and recorded voice names of senders on remote VPIM systems can be derived from incoming VPIM messages, and VPIM subscribers can be automatically created in the Cisco text and voice names.

Available when a recorded voice name exists for the VPIM subscriber.

Voice names for VPIM subscribers can be recorded individually in the Cisco Administrator.

Voice names for VPIM subscribers can be imported by using the Cisco Import utility.

Chapter 1 Networking in Cisco Unity

Unity directory with the derived

Unity

Unity Bulk

Voice names for Bridge subscribers can be imported by using the Cisco

Unity

Bulk Import utility.

Ta b l e 1-9 Audio Formats Supported1

AMIS Bridge VPIM

The AMIS protocol is not dependent on audio format.

Any codec supported for use with Cisco

Unity can be used.

Octel Analog Networking is not dependent on audio format.

The Cisco Unity servers must use either the G.711 or the G.729a codec in order to communicate with the Cisco

Unity

Bridge servers.

The VPIM Version 3 Specification includes support for the following audio formats: G.711, G.726, and GSM 6.10.

Any codec supported for use with Cisco

Outbound VPIM messages can be converted to G.726 or sent in the format in which they were recorded.

Incoming VPIM messages can be converted to G.711, G.729a, or GSM

6.10, or remain in the format in which they were sent.

1. For a list of audio formats supported by Cisco Unity, see the Audio Codecs and Cisco Unity white paper, at

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

Unity can be used.

1-8

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Chapter 1 Networking in Cisco Unity

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-10 Delivery Receipt/Read Receipt

AMIS Bridge VPIM

The AMIS protocol does not support this functionality. A request for a delivery or read receipt may be allowed on either Cisco

Unity or the remote AMIS voice mail system when addressing, but the request will not result in a receipt.

Requests for a delivery or read receipt generated by Cisco

Unity are returned from the Octel system as delivery receipts. The receipt is sent to the sender after the message is delivered to the Octel node, regardless of when the Octel system places the message in the subscriber

Requests for a delivery or read receipt generated by either Cisco remote VPIM system are honored, although both are treated as requests for delivery receipts.

mailbox or when the message is actually read.

Ta b l e 1-11 Directory Information Sharing

AMIS Bridge VPIM

The AMIS protocol does not provide any mechanism for sharing or synchronizing directory information.

If the remote AMIS system is configured to send the recorded voice name in messages, Cisco

Unity will

play it as part of the message.

Avaya Octel analog networking includes the NameNet feature, which provides a mechanism to propagate text and voice names among nodes on the Octel analog network, based on message activity or by administrator request.

The Cisco Unity Bridge participates in NameNet. The Bridge retrieves Octel subscriber names and voice names from other Octel nodes, and stores the data in a directory on the Bridge server. The Bridge also maintains a directory of Cisco

Unity subscribers, and sends

Cisco

Unity names and voice names to

the Octel nodes upon request.

The Bridge synchronizes Octel subscriber information with Cisco Cisco

Unity allows the automatic

Unity. By default,

creation, modification, and deletion of Bridge subscribers based on the information sent by the Bridge.

Cisco Unity synchronizes Cisco Unity subscriber information with the Bridge.

If the remote Octel system is configured to send the recorded voice name in messages, Cisco

Unity will play it as part

Although the VPIM specification does not define a mechanism for directory information sharing or synchronization, some VPIM-compliant voice mail systems may process vCards or header information in VPIM messages and update their directories based on message activity.

Cisco Unity can be configured to include the recorded voice name and/or vCard of the sender in messages to the remote VPIM systems.

The delivery location settings for a remote voice messaging system can be configured to allow automatic creation, modification, and deletion of VPIM subscribers for that location, based on vCard or header information received in incoming voice messages from that location.

If the remote VPIM system is configured to send the recorded voice name and/or vCard in messages, Cisco make them available as part of the message.

of the message.

Unity or the

Unity will

OL-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-9

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-12 Distribution Lists

AMIS Bridge VPIM

The AMIS protocol does not support delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco

Unity to the AMIS system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco

Unity can be addressed to a Cisco

Unity public or private distribution list that includes AMIS subscribers. Private distribution lists can include blind addresses.

Incoming AMIS messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco

Unity public distribution lists. (However, you may be able to set up a Cisco

Unity subscriber account whose sole purpose is to forward messages to a Cisco

Unity public

distribution list. See your Microsoft

Octel Analog Networking does not support delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco Unity to the Octel system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco Unity can be addressed to a Cisco

Unity public or private distribution list that includes Bridge subscribers. Private distribution lists can include blind addresses.

Incoming Bridge messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco

Unity public distribution lists. (However, you may be able to set up a Cisco

Unity subscriber account whose sole purpose is to forward messages to a Cisco

Unity public distribution list. See your Microsoft Exchange and Outlook documentation for more information.)

The VPIM specification does not include support for message delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco Unity to the VPIM system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco Unity can be addressed to a Cisco or private distribution list that includes VPIM subscribers. Private distribution lists can include blind addresses.

Incoming VPIM messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco distribution lists. (However, you may be able to set up a Cisco account whose sole purpose is to forward messages to a Cisco distribution list. See your Microsoft Exchange and Outlook documentation for

more information.) Exchange and Outlook documentation for more information.)

Chapter 1 Networking in Cisco Unity

Unity public

Unity subscriber

Unity public

1-10

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Chapter 1 Networking in Cisco Unity

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-13 Mailbox ID Translation

AMIS Bridge VPIM

Not available. Prefixes can be defined so that

Cisco

Unity subscribers can address messages to Octel subscribers by entering a network address consistent with phone network dial plans.

All Cisco Unity subscribers are mapped to a configurable mailbox and serial number value for use when communicating with Octel servers. This allows any Cisco

Unity subscriber to

Additional digits can be automatically added to the beginning of the mailbox numbers that are associated with the Cisco on messages that are sent from Cisco can be removed from the beginning of the remote sender and Cisco numbers for delivery to Cisco subscribers.

represent mailbox X at node serial number Y within the Octel network, independent of the Cisco

Unity

numbering plan.

Unity sender and remote recipient

Unity subscribers. The same digits

Unity mailbox

Unity

Ta b l e 1-14 Fax Messaging

AMIS Bridge VPIM

The AMIS protocol does not support this functionality.

Ta b l e 1-15 Message Transport Time Considerations

Supported. Supported; however, VPIM supports only

the TIFF-F message format.

AMIS Bridge VPIM

Analog delivery of the message from the sending system to the receiving system is the most significant contribution to transport time.

The minimum analog delivery time can be calculated by multiplying the actual recording length of the message by the number of recipients of the message. The AMIS protocol requires a separate analog transmission of the message for each recipient.

For example, a five-minute message with 10 recipients would require a minimum of 50 minutes for the

Analog delivery of the message from the sending system to the receiving system is the most significant contribution to transport time.

The minimum analog delivery time is the actual recording length of the message.

Octel Analog Networking allows a single analog transmission of a message addressed to multiple recipients, which the receiving node will deliver to all intended recipients.

For example, a five-minute message with 10 recipients would require a minimum of 5 minutes for the analog transmission.

Exchange routing time and SMTP delivery time to a remote VPIM system are the only considerations.

For example, a five-minute message with 10 recipients would likely take less than one minute to transmit.

analog transmission.

OL-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-11

Comparison of AMIS, Bridge, and VPIM Networking

Ta b l e 1-16 Private Messages

AMIS Bridge VPIM

The AMIS protocol does not support this functionality. Messages marked private when they are sent are not

Supported. Messages marked private when they are sent are marked private when the recipient retrieves them.

Supported. Messages marked private when they are sent are marked private

when the recipient retrieves them. marked private when the recipient retrieves them.

Ta b l e 1-17 Secure Messages

AMIS Bridge VPIM

Incoming messages cannot be encrypted before being delivered to the local recipient.

With default settings: Outgoing secure messages are undeliverable and will generate an NDR.

When configured: Outgoing secure messages are decrypted by the Voice Connector and the message is no longer secure.

With default settings: Incoming messages will not be encrypted before being delivered to the local recipient. Outgoing secure messages are undeliverable and will generate an NDR.

When configured: Incoming messages are encrypted before being delivered to the local recipient. Outgoing secure messages are decrypted by the Voice Connector and the message is no longer secure.

With default settings: Incoming messages

will not be encrypted before being

delivered to the local recipient. Outgoing

secure messages are undeliverable and

will generate an NDR.

When configured: Incoming messages are

encrypted before being delivered to the

local recipient. Outgoing secure

messages are decrypted by the Voice

Connector and can be re-encrypted if the

receiving server is Cisco

Exchange and if secure messaging is

configured. During transport outside the

Cisco

encrypted.

Chapter 1 Networking in Cisco Unity

Unity with

Unity system, messages are not

Ta b l e 1-18 Simultaneous Analog Sessions for Message Delivery to or from Remote Voice Mail Systems

AMIS Bridge VPIM

Supported.

Limited to the voice mail port availability on the AMIS bridgehead server.

Ports available to place outgoing AMIS calls can be configured in the Cisco

Unity Administrator (but not

per AMIS destination).

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Supported.

Limited to Bridge server analog port availability.

Maximum number of ports to deliver simultaneously to any single node, and the threshold to initiate and disconnect additional calls, can be configured per Bridge server.

N/A.

1-12

OL-13844-01

Chapter 1 Networking in Cisco Unity

Road Map to the Networking Documentation: Where to Go from Here

Ta b l e 1-19 Urgent Messages

AMIS Bridge VPIM

The AMIS protocol does not support this functionality. Messages marked urgent when they are sent are not marked urgent when the recipient retrieves them.

Ta b l e 1-20 System Broadcast Messages

AMIS Bridge VPIM

Not available. Regular voice messages can be sent to a

Supported. Messages marked urgent when they are sent are marked urgent when the recipient retrieves them.

bulletin mailbox on an Octel Aria system or to a System Distribution List (SDL) on an Octel Serenade system. Similarly, system broadcast messages can be sent to a bulletin mailbox or SDL. Both types of message will be transmitted in the same way by the Cisco treated identically when delivered to the bulletin mailbox or SDL.

Unity Bridge and

Supported. Messages marked urgent when they are sent are marked urgent when the recipient retrieves them.

System broadcast messages can be sent between Cisco servers that do not share the same directory, or between Cisco Exchange and Cisco servers, using VPIM. Other types of remote messaging systems will treat the system broadcast message in the same way they would treat a regular voice message.

Unity with Exchange

Unity with

Unity Express

Road Map to the Networking Documentation: Where to Go from Here

If your installation includes multiple Cisco Unity servers networked together and accessing a common directory, much of the information that you need is included in the with “Digital Networking” even if you will also be using other networking options.

If you plan to use AMIS to communicate with another voice messaging system, see the “AM IS

Networking” chapter.

If you plan to use VPIM to communicate with another voice messaging system, see the “VPIM

Networking” chapter.

If you plan to use the Bridge to communicate with Octel systems on an Octel analog network, see the

Networking Guide for Cisco

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

Regardless of which networking option you choose, you need to customize the settings for the primary location. See the

“Primary Location Settings” chapter.

Unity Bridge, at

“Digital Networking” chapter. Start

OL-13844-01

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

1-13

Road Map to the Networking Documentation: Where to Go from Here

Chapter 1 Networking in Cisco Unity

1-14

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

Digital Networking

Overview: Digital Networking

Each Cisco Unity server has a maximum number of subscribers that it can serve. When the voice messaging needs of your organizations require more than one Cisco networked together such that they access a single, global directory, while at the same time, each Cisco

Unity installation in the network continues to serve only those subscribers that were created on the server. Digital Networking is the Cisco one Cisco Cisco and send voice messages to subscribers who are associated with other Cisco message, press 2”). After listening to messages, subscribers can reply to messages that were sent from subscribers on other Cisco

When the networked Cisco Unity servers are integrated with the same phone system, the servers can be grouped into a dialing domain and configured such that:

• Calls are transferred from the automated attendant or directory assistance to subscribers who are not

• Identified subscriber messaging (ISM) works for networked subscribers: subscribers who call and

Unity server to exchange messages with subscribers who are associated with other

Unity servers. With Digital Networking, subscribers can use the phone to log on to Cisco Unity

Unity servers.

associated with the local server.

leave messages for subscribers on other Cisco subscribers.

CHAP T ER

Unity server, the servers can be

Unity feature that allows subscribers who are associated with

Unity servers in the dialing domain are identified as

Unity servers (“To send a

Subscribers use the same Cisco Unity tools for messaging with subscribers on other networked Cisco

Unity servers that they use for messaging with subscribers on the same server. If your organization also has the FaxMail and Text to Speech e-mail features, subscribers can use the phone to forward fax and e-mail messages to any subscriber in the organization.

Although Cisco Unity stores information about subscribers (and other Cisco Unity objects such as call handlers) in a SQL Server database on the Cisco subscribers, distribution lists, and locations is also stored in Active Directory to enable Digital Networking. When subscriber and location data from other Cisco Directory, Cisco replication, each Cisco subscribers who are associated with the other Cisco

Unity detects the data and updates the SQL Server database. Because of directory

Unity server has the information that it needs to address voice messages to

Unity server, a small subset of information about

Unity servers.

Requirements for Setting Up Digital Networking

The key to Digital Networking is that all of the Cisco Unity servers access a common directory. To use Digital Networking, the Cisco

OL-13844-01

Unity servers must be in the same Active Directory forest.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

Unity servers replicates in Active

2-1

Overview: Digital Networking

Note that Cisco Unity servers that are licensed for Unified Messaging (UM) and Cisco Unity servers that are licensed for Voice Messaging (VM) can use Digital Networking to exchange messages. There are no licensing issues associated with VM and UM existing in the same Exchange organization or Active Directory forest, as long as the VM subscribers access voice and fax messages only over the phone interface or with the separately licensed Cisco

For specific information about requirements and support, see the Cisco Unity Networking Options Requirements document, available at

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

Licenses and License Pooling

Digital Networking is enabled on every Cisco Unity server. There are no additional licenses that you need to obtain to set up Digital Networking.

Though you do not need a license for Digital Networking, you may want to add a licensed feature called license pooling. License pooling allows Cisco pool licenses for subscribers and for the Cisco across all of the Cisco is in compliance with licensing restrictions. For example: two Cisco licenses for subscribers; with license pooling, one of the servers can use 501 or more licenses as long as the total used by both servers does not exceed 1,000.

For all licensed features other than subscriber licenses, licensing is on a per-machine basis. Licensing information is stored with the primary location for each Cisco stored in the directory, each Cisco usage in the pool.

For more information about license pooling and obtaining licenses for Cisco Unity features, see the applicable Licensing for Cisco

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

Unity servers does not exceed total licenses for the feature, the Cisco Unity server

Chapter 2 Digital Networking

Personal Communications Assistant (PCA).

Unity servers that are set up for Digital Networking to

Unity Inbox. With license pooling, if total utilization

Unity servers each have 500

Unity server. Because location data is

Unity server has the information that it needs to keep track of license

Unity white paper, at

In This Chapter

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

2-2

In this chapter, you will find procedures for setting up and upgrading Digital Networking, followed by detailed discussions of the concepts and terminology you need to understand. See the following sections:

• Setting Up Digital Networking, page 2-3—This section describes the prerequisites for setting up

Digital Networking, and provides a task list containing a high-level view of all of the tasks that you need to complete for the setup, and the order in which they should be completed.

• Procedures for Setting Up Cisco Unity to Use Digital Networking, page 2-4—This section contains

all of the procedures necessary to set up Cisco Unity for Digital Networking.

• Digital Networking Concepts and Definitions, page 2-14—This section explains Digital Networking

concepts in detail. If you are unfamiliar with Digital Networking, we recommend that you read this section prior to completing the setup procedures.

• Notable Behavior, page 2-24—This section contains information about notable behavior related to

Digital Networking.

Setting Up Digital Networking

Prerequisites

• Cisco Unity is already installed on the servers, according to the requirements and instructions in the

Cisco

Unity installation guide.

• Cisco Unity meets the requirements as described in the “Requirements for Setting Up Digital

Networking” section on page 2-1.

Setting Up Digital Networking

Task List: Setting Up Digital Networking

Use this task list to set up Digital Networking on each Cisco Unity server. The cross-references take you to detailed procedures. If a system is using failover, do the tasks only on the primary server unless a task requires changing the registry, which must be done on both the primary and secondary servers. (The instructions will note this.)

1. Optionally, obtain and enable a license file for license pooling. See the “Enabling License Pooling

(Optional)” section on page 2-4.

2. Customize the primary location. See the “Customizing the Primary Location” section on page 2-6.

3. Set the addressing, directory handler, and automated attendant search scopes. See the “Setting the

Addressing, Directory Handler, and Automated Attendant Search Scopes” section on page 2-6. The

Automated Attendant search option must be set to search the dialing domain in order for identified subscriber messaging to work.

4. Optionally, enable identified subscriber messaging (ISM). See the “Setting Up Identified Subscriber

Messaging Between Networked Cisco Unity Subscribers (Optional)” section on page 2-8.

5. Modify the All Subscribers public distribution list. See the “Modifying the All Subscribers Public

Distribution List” section on page 2-10.

6. Optionally, add alternate extensions to each subscriber account. For instructions, see the “Setting

Up Alternate Extensions” section in the “Setting Up Features That Are Controlled by Subscriber or Subscriber Template Settings” chapter of the System Administration Guide for Cisco

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

7. Optionally, set up system broadcast messaging in order to send system broadcasts to all subscribers

in the directory. See the

the Directory (Optional)” section on page 2-10.

“Setting Up System Broadcast Messaging for Sending to All Subscribers in

Unity, at

OL-13844-01

8. Optionally, change the default search scope in the Cisco Personal Communications Assistant to the

global directory. See the

on page 2-11.

“Changing the Default Search Scope for the Cisco PCA (Optional)” section

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

2-3

Chapter 2 Digital Networking

Procedures for Setting Up Cisco Unity to Use Digital Networking

9. Optionally, enable live reply between subscribers on different Cisco Unity servers. See the

“Enabling Live Reply Between Cisco Unity Servers in the Same Dialing Domain (Optional)” section on page 2-11.

10. Test the Digital Networking setup. See the “Testing the Digital Networking Setup” section on

page 2-12.

11. For Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager)

integrations only: Optionally, enable the cross-server features. See the

Transfers, and Live Reply” chapter for details.

“Cross-Server Logon,

Procedures for Setting Up Cisco Unity to Use Digital Networking

This section contains all of the procedures necessary to set up each Cisco Unity server for Digital Networking. Consult the on the order in which the procedures must be completed.

Enabling License Pooling (Optional)

“Task List: Setting Up Digital Networking” section on page 2-3 for information

For each Cisco Unity server, you can choose whether it will participate in the license pool. To place a Cisco

Unity server in the pool, obtain a license file with license pooling enabled, and then install the license file on the Cisco pooling feature enabled, the server does not participate in the pool, and compliance for licenses on that server is measured on a per-machine basis.

You obtain the license file by completing registration information on Cisco.com. Shortly after registration, Cisco e-mails the license file. The e-mail from Cisco contains instructions on how to save and store the files.

Note If the system is using failover, you install the license files only on the primary server.

The following information is required during registration:

• The MAC address (physical address) for the network interface card (NIC) in the Cisco Unity

computer.

• The product authorization key (PAK) that appears on the sticker located on the front of the sleeve

for Cisco

Do the following procedures in the order listed.

To Get the MAC Address of the Cisco Unity Computer

Step 1 On the Cisco Unity server, do one of the following:

• If the server contains a dual NIC that has been configured for fault tolerance, run the

NIC-configuration utility provided by the manufacturer, and write down the MAC address (excluding hyphens) that is shared by the two NICs. Then skip the rest of this procedure.

• If the server does not contain a dual NIC or if the server contains a dual NIC that is not configured

for fault tolerance, on the Windows Start menu, click Programs > Accessories > Command Prompt.

Unity DVD 1 or CD 1.

Unity server. If a license file on a Cisco Unity server does not have the license

2-4

Step 2 In the Command Prompt window, enter ipconfig /all, and press Enter.

Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)

OL-13844-01

+ 218 hidden pages

Cisco With Microsoft Exchange User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Networking Guide for Cisco Unity (With Microsoft Exchange)

CONTENTS

Preface

Networking in Cisco Unity

Overview: Networking in Cisco Unity

Networking Options

Message Addressing Options

Locations and External Subscribers

Voice Connector

Active Directory Schema Extensions

Comparison of AMIS, Bridge, and VPIM Networking

Road Map to the Networking Documentation: Where to Go from Here

Digital Networking

Overview: Digital Networking

Requirements for Setting Up Digital Networking

Licenses and License Pooling

In This Chapter

Setting Up Digital Networking

Prerequisites

Task List: Setting Up Digital Networking

Procedures for Setting Up Cisco Unity to Use Digital Networking

Enabling License Pooling (Optional)