Cisco With Microsoft Exchange User Manual

Download

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

Chapter 2 Digital Networking

Step 3 Write down the value of Physical Address, excluding the hyphens, or save it to a file that you can access

during online registration. (For example, if the physical address is 00-A1-B2-C3-D4-E5, record 00A1B2C3D4E5.)

If the server contains more than one NIC, one value will appear for each NIC. Write down the value for the NIC that you will use to connect the Cisco

Step 4 Close the Command Prompt window.

To Register and Obtain the License Files

Step 1 Browse to the registration website at http://www.cisco.com/go/license (URL is case sensitive).

You must be a registered user on Cisco.com to obtain license files.

Step 2 Enter the PAK or software serial number, and click Submit.

Step 3 Follow the on-screen prompts.

Step 4 Shortly after registration, you will receive an e-mail with the Cisco Unity license files.

If license files are lost, it can take up to one business day to get another copy.

Procedures for Setting Up Cisco Unity to Use Digital Networking

Unity server to the network.

If you do not receive the license files within 1 hour or to get another copy of a license file, call the Cisco Technical Assistance Center (TAC) and ask for the Licensing Team:

In the U.S.

Outside the U.S.

800 553-2447

For your local Cisco TAC phone number, see the Cisco Worldwide Contacts page at

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Or open a service request by using the TAC Service Request Tool at

http://tools.cisco.com/ServiceRequestTool/create/DefineProblem.do.

You will need to provide information to verify Cisco Unity ownership—for example, the purchase order number or the PAK (which appears on the sticker located on the front of the sleeve for Cisco DVD

1 or CD 1).

Unity

To View the License Pooling Information

Step 1 On a Cisco Unity server that has a license file with license pooling enabled, double-click the

Cisco

Unity Tools Depot icon on the desktop.

Step 2 In the left pane of the Tools Depot window, expand Administration Tools.

Step 3 Double-click License Info Viewer.

Step 4 Under Cisco Unity Licensing, expand License Pool.

Step 5 Under License Pool, click Subscriber Mailboxes, Maximum Unified Messaging Subscribers, or

Cisco

Unity Inbox Subscribers.

OL-13844-01

Step 6 In the right pane, the names of the networked servers that share the subscriber license appear.

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

2-5

Procedures for Setting Up Cisco Unity to Use Digital Networking

Customizing the Primary Location

To Customize the Primary Location

Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Profile page.

Step 2 Enter a meaningful name for the location.

Step 3 Enter a Dial ID. The Dial ID identifies this location to Cisco Unity.

Step 4 Record a voice name for the location.

Step 5 For the dialing domain, do one of the following:

• If this server is not integrated with the same phone system as other networked Cisco Unity servers,

click None.

• If this server is integrated with the same phone system as other networked Cisco Unity servers, enter

the dialing domain name, or select it from the available list. The list contains names of dialing domain names already configured on at least one other Cisco

Note that the dialing domain name is case sensitive and must be entered exactly the same on all of the servers. To ensure that all servers are correctly added to the same dialing domain, enter the dialing domain name on one Cisco Cisco

Unity servers. By doing so, you also confirm that replication is working correctly among the servers. The time that it takes for the primary location data from other Cisco reflected on the local server depends on your network configuration and replication schedule.

Chapter 2 Digital Networking

Unity server in the network.

Unity server and wait for the name to replicate to the other

Unity servers to be

Step 6 If you will be setting up for VPIM Networking, enter the SMTP Domain Name.

Step 7 Click Save.

For additional information about primary location settings, see the “Primary Locations Profile Page” section in the “Network Settings” chapter of the Interface Reference Guide for the Cisco Administrator, available at

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

Unity

Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes

Do the procedures in the following sections to set up the search scopes:

• Setting the Addressing Search Scope, page 2-6

• Setting the Directory Handler Search Scope, page 2-7

• Setting the Automated Attendant Search Scope, page 2-7

Setting the Addressing Search Scope

For detailed information about the addressing search options, see the “Primary Location Addressing

Option Settings” section on page 9-3.

2-6

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

OL-13844-01

Chapter 2 Digital Networking

To Set the Addressing Search Scope

Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Addressing Options page

and set the addressing options as follows:

• To allow subscribers that are created on the local Cisco Unity server to address messages to

subscribers on other Cisco

Unity servers that access the same directory, select Dialing Domain or

Global Directory, as applicable.

• If you are using blind addressing to a Cisco Unity server in a separate directory, or to another voice

messaging system, set the Blind Addressing Allowed Locations setting to something other than None, as applicable.

Step 2 If you want subscribers to be able to do a spell-by-name search that is limited to a specific location,

check the Include Locations in Searches check box.

Step 3 Click the Save icon.

Setting the Directory Handler Search Scope

Procedures for Setting Up Cisco Unity to Use Digital Networking

To Set the Directory Handler Search Scope

Step 1 In the Cisco Unity Administrator, go to the Call Management > Directory Handlers > Profile page. If

you are using only the default directory handler, skip to

Step 2 Click the Find icon to find and view the directory handler that you want to change.

Step 3 Go to the Search Options page, and click Dialing Domain.

Step 4 Click the Save icon.

Step 5 Repeat Step 2 through Step 4 for each directory handler that you want to change.

Setting the Automated Attendant Search Scope

By default, callers who reach the opening greeting for your organization can be transferred only to subscribers who are associated with the local Cisco attendant so that callers can be transferred to subscribers who are associated with other Cisco servers in the same dialing domain, change a registry setting as described in the following procedure.

The automated attendant search scope must be set to search the dialing domain in order for the following features to work:

• Identified subscriber messaging between Cisco Unity servers in the dialing domain

• Cross-server transfers from the automated attendant of one Cisco Unity server to another

Cisco

Unity server in the dialing domain

Step 3.

Unity server. If you want to set up the automated

Unity

OL-13844-01

Note If the system is configured for failover, the registry changes must be made on both the primary and

secondary Cisco Unity servers.

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

2-7

Chapter 2 Digital Networking

Procedures for Setting Up Cisco Unity to Use Digital Networking

To Set the Automated Attendant Search Scope

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Networking—Set Auto Attendant Search Scope.

Step 4 In the New Value list, click 1, and then click Set so that Cisco Unity searches for subscribers within the

dialing domain.

Step 5 When prompted, click OK.

You do not need to restart Cisco Unity to enable the change.

Step 6 Click Exit.

Setting Up Identified Subscriber Messaging Between Networked Cisco Unity Subscribers (Optional)

Enabling identified subscriber messaging (ISM) between networked Cisco Unity subscribers requires the following:

• The Cisco Unity servers must be connected to the same phone system or phone system network as

described in the

• The servers must be configured to be in the same dialing domain, as described in the “Customizing

“Dialing Domains” section on page 2-15.

the Primary Location” section on page 2-6.

• The automated attendant search scope on each server must be set to the dialing domain as described

in the

“Setting the Automated Attendant Search Scope” section on page 2-7.

• The applicable permissions must be set, as described in the “Setting Permissions on Active

Directory Containers Used for Importing Subscribers” section on page 2-8.

• Identified subscriber messaging on each server must be enabled in the Cisco Unity Administrator as

described in the

“Enabling Identified Subscriber Messaging on Each Cisco Unity Server” section on

page 2-9.

Setting Permissions on Active Directory Containers Used for Importing Subscribers

In Permissions wizard, on the Choose Active Directory Containers for Import page, you choose the Active Directory containers from which you want to import users, contacts, and groups to make them Cisco

Unity subscribers and public distribution lists. Note the following:

• You must choose a container for the domain that includes the Cisco Unity server.

• If you will be importing users from the same container for every Cisco Unity server, choose that

container. For example, if CiscoUnityServer1 and CiscoUnityServer2 will both be importing users from Container1 only, choose Container1.

• If, for all of the Cisco Unity servers combined, you will be importing users from two or more

containers, the Cisco granted SendAs permission on every container from which users will be imported on every Cisco

Unity server in the forest. For example, if CiscoUnityServer1 will import users from

Unity message store services account on each Cisco Unity server must be

2-8

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

OL-13844-01

Chapter 2 Digital Networking

Although you can use different message store services accounts on each Cisco Unity server and set the SendAs permissions by using Active Directory Users and Computers, the easiest way to set the needed permissions is when you run Permissions wizard on each Cisco

• Use the same message store services account on each Cisco Unity server.

• Specify all of the import containers that will be used by all of the Cisco Unity servers.

Note that all of the Cisco Unity servers can use the same installation, directory services, and message store services accounts.

To Set the Applicable Permissions

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane of the Tools Depot window, expand Administration Tools.

Step 3 Double-click Permissions Wizard.

Procedures for Setting Up Cisco Unity to Use Digital Networking

Container1 and Container2, and if CiscoUnityServer2 will import users from Container3 and Container4, the Cisco

Unity message store services account for each Cisco Unity server must have

SendAs permission for all four containers.

Unity server. Make note of the following:

Step 4 Do the following:

• Choose the same Active Directory account for the Cisco Unity message store services account:

–

Click Next without changing any options until you arrive at the Choose the Cisco Unity Message Store Services Account page.

–

Choose the same Active Directory account for the Cisco Unity message store services account on every Cisco

• Choose the applicable containers:

–

Click Next without changing any options until you arrive at the Choose Active Directory

Unity server.

Containers for Import page.

–

Choose all of the containers from which users will be imported for every Cisco Unity server in the forest.

Step 5 Click Next without changing any options until you complete the wizard.

Step 6 Repeat Step 1 through Step 5 on each Cisco Unity in the forest.

Enabling Identified Subscriber Messaging on Each Cisco Unity Server

Note If the system is using failover, you must make this change on both the primary and secondary servers,

because the setting is stored in the registry.

OL-13844-01

To Enable Identified Subscriber Messaging on Each Cisco Unity Server

Step 1 In the Cisco Unity Administrator, go to the System > Configuration Settings page.

Step 2 In the Identified Subscriber Messaging section, uncheck the Disable Identified Subscriber Messaging

check box.

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

2-9

Procedures for Setting Up Cisco Unity to Use Digital Networking

Identified subscriber messaging for subscribers on the same Cisco Unity server is enabled when the check box is unchecked. By default, the box is unchecked.

Step 3 Click the Save icon.

Modifying the All Subscribers Public Distribution List

By default, the predefined All Subscribers public distribution list on each Cisco Unity server has the same recorded voice name and extension. If you do not modify the recorded voice name and extension, subscribers will hear a confusing list of choices when they address messages to an All Subscribers distribution list, and errors will be logged to the Windows Event Viewer on the Cisco

To Modify the All Subscribers Public Distribution List

Step 1 In the Cisco Unity Administrator, go to the Public Distribution List > Profile page.

Step 2 Click the Find icon.

Chapter 2 Digital Networking

Unity server.

Step 3 In the Find By list, indicate how to find the distribution list, and then click Find.

Step 4 In the Name list, click All Subscribers -<Server Name> to display the profile settings for the list.

Step 5 Record a unique voice name for the list.

Step 6 Assign a unique extension to the list.

Step 7 Optionally, change the display name of the list to match the recorded voice name. By default, the

Cisco

Unity server name is appended to the display name, so the display name is unique in the directory.

Step 8 Click the Save icon.

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

System broadcast messages are recorded announcements that are sent to everyone in an organization (or to particular location(s) within an organization). When each server has been configured for Digital Networking, a system broadcast message can be sent to all subscribers on all Cisco share the same directory. Alternatively, a system broadcast message can be sent to all subscribers on one or more specific Cisco message to the delivery location Dial ID of the desired server.

System broadcast messages do not light message waiting indicators (MWIs) on subscriber phones, nor do they cause distinctive dial tones to notify subscribers of a new message when they pick up their desk phone receiver. System broadcast messages also do not trigger message notifications for alternative devices, such as a pager or another phone.

To allow one or more Cisco Unity subscriber(s) to send system broadcast messages to subscribers on multiple Cisco Broadcast Message Administrator. For information on setting up the Cisco Administrator, see the “Sending System Broadcast Messages” section in the “Cisco chapter of the System Administration Guide for Cisco

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

Unity servers, you first set up and offer the subscriber(s) access to the Cisco Unity

Unity servers that access the same subscriber directory, by addressing the

Unity Broadcast Message

Unity. The guide is available at

Unity servers that

Unity Conversation”

2-10

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

OL-13844-01

Chapter 2 Digital Networking

Procedures for Setting Up Cisco Unity to Use Digital Networking

Note that individual subscribers can be granted permissions to send system broadcast messages either on the local Cisco

In organizations where there are multiple Cisco Unity or Cisco Unity Express servers that access different directories, the VPIM Networking option must be used in order to include subscribers on those servers in the distribution of a system broadcast message. For information on setting up system broadcast messages to be distributed to VPIM locations, see the

on page 8-7.

Unity server only, or to subscribers on multiple servers.

“Networked System Broadcast Messages” section

Changing the Default Search Scope for the Cisco PCA (Optional)

By default, the search scope for the Cisco Personal Communications Assistant (PCA) address book is set to local directory. As a possible convenience to subscribers in your organization, you may want to change the default search scope to global directory instead. When the default search scope is set to the global directory, subscribers can search for subscribers at different locations without having to change the search scope themselves. In addition, subscribers will not need to keep track of which Cisco subscribers are listed in the local directory and which are listed in the global directory.

Regardless of the default search scope that you specify here, subscribers can still switch between the local and global directory as they use the Cisco Cisco

Unity Assistant.

Use the following procedure to set the global directory as the default search scope for the Cisco PCA Address Book. The change affects all subscribers that are associated with the Cisco

PCA Address Book in the Cisco Unity Inbox and

Unity

Unity server.

To Set the Default Search Scope to the Global Directory for the Cisco PCA Address Book

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Unity Inbox and Assistant—Set Default Address Book Search

Scope.

Step 4 In the New Value list, click 1, and then click Set so that the Address Book searches for subscribers within

the global directory by default.

Step 5 When prompted, click OK.

Step 6 Click Exit.

You do not need to restart Cisco Unity to enable the change.

Enabling Live Reply Between Cisco Unity Servers in the Same Dialing Domain (Optional)

Live reply allows subscribers who listen to their messages by phone to reply to a message from a subscriber by calling the subscriber. For live reply to work:

• Subscribers must belong to a class of service in which live reply is enabled. Live reply is enabled

on the Subscribers > Class of Service > Messages page in the Cisco checking the Subscribers Can Reply to Messages from Subscribers by Calling Them check box.

• Transfer numbers must be configured for each Cisco Unity subscriber.

Unity Administrator, by

OL-13844-01

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

2-11

Procedures for Setting Up Cisco Unity to Use Digital Networking

• Cisco Unity must identify the sender of the message as a subscriber. This happens either when the

sender logs in to his or her mailbox to send the message, or when identified subscriber messaging is enabled and the sender calls the recipient from a recognized subscriber phone number and is forwarded to Cisco

Unity. (To set up identified subscriber messaging, see the “Setting Up Identified

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

By default, live reply is restricted to subscribers on the same Cisco Unity server. Do the following procedure to enable live reply via release to phone system transfer between subscribers on different Cisco

Unity servers in the same dialing domain.

To Enable Live Reply Between Cisco Unity Servers in the Same Dialing Domain

Step 1 Verify that the addressing search scope has been set to the dialing domain as described in the “Setting

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

Step 2 In the Cisco Unity Administrator, go to the Network > Dialing Domain Options page. (If the link is

not active, that means that the Cisco

Step 3 In the Live Reply section, check the Subscribers Can Call Back a Cisco Unity Subscriber on a

Different Cisco

Unity Server check box.

Chapter 2 Digital Networking

Unity server has not been configured to be in a dialing domain.)

Step 4 Leave the Release Calls to the Phone System button selected (this is the default).

Caution Do not select the Cross-Server Live Reply: Pass Control to the Called Subscriber’s

Cisco

Unity Server option unless you have read the restrictions and requirements that are

explained in the “Cross-Server Logon, Transfers, and Live Reply” chapter.

Step 5 Click the Save icon.

Testing the Digital Networking Setup

Each Cisco Unity server stores the primary location data and a subset of the data about subscriber accounts and distribution lists in the directory. The time that it takes for data from other Cisco servers to be reflected on the local server depends on your Active Directory network configuration and replication schedule. You need to wait for the Cisco testing the Digital Networking setup.

To test the Digital Networking setup, create test subscriber accounts or use existing subscriber accounts on each Cisco used in the tests, be sure to:

• Record voice names.

• Record and enable internal greetings.

• Check the List in Phone Directory check box on the Subscriber Profile page.

Unity server. When setting up subscriber accounts in the Cisco Unity Administrator to be

Unity

Unity data to replicate to the other servers before

2-12

• Check the Before Playing Each Message, Play the Sender’s Name check box on the Subscriber

Conversation page.

Do the following tests to make sure Digital Networking is functioning properly:

• To Verify Messaging Between Subscribers on Different Cisco Unity Servers, page 2-13

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

OL-13844-01

Chapter 2 Digital Networking

• To Verify Call Transfers from the Automated Attendant to Subscribers on Other Cisco Unity

• To Verify Call Transfers from a Directory Handler to Subscribers on Other Cisco Unity Servers,

• To Verify Identified Subscriber Messaging Between Networked Subscribers, page 2-14

• To Verify Live Reply Between Subscribers on Different Cisco Unity Servers in the Dialing Domain,

To Verify Messaging Between Subscribers on Different Cisco Unity Servers

Verify that messaging between subscribers on different Cisco Unity servers works in both directions (for example, from server A to server B and from server B to server A).

Step 1 Log on to a Cisco Unity server as a subscriber.

Step 2 Press 2 to record and send messages to subscribers who are associated with other Cisco Unity server(s).

Step 3 Log on to the applicable Cisco Unity server as the recipient subscriber to verify that the message was

received.

Step 4 Repeat Step 1 through Step 3 in the opposite direction.

Procedures for Setting Up Cisco Unity to Use Digital Networking

Servers, page 2-13

page 2-13

page 2-14

To Verify Call Transfers from the Automated Attendant to Subscribers on Other Cisco Unity Servers

If the automated attendant search scope is set to search the dialing domain, verify that outside callers are transferred to subscribers who are associated with other Cisco

Step 1 From a non-subscriber phone, call the Cisco Unity server that has been configured to handle outside

callers, and enter the extension of a subscriber who is associated with another Cisco

Step 2 Verify that you reach the correct subscriber phone.

Unity servers.

Unity server.

To Verify Call Transfers from a Directory Handler to Subscribers on Other Cisco Unity Servers

If the directory handler search scope is set to search the dialing domain, verify that outside callers can find subscribers who are associated with other Cisco

Step 1 From a non-subscriber phone, call the Cisco Unity server that has been configured to handle outside

Unity servers in the phone directory.

callers, and transfer to a directory handler.

Step 2 Verify that you can find a subscriber who is associated with another Cisco Unity server in the phone

directory, and that the directory handler transfers the call to the correct subscriber phone.

OL-13844-01

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

2-13

Digital Networking Concepts and Definitions

To Verify Identified Subscriber Messaging Between Networked Subscribers

Do this test if the Cisco Unity servers have been configured for identified subscriber messaging between networked subscribers.

Step 1 Ve ri fy t ha t Ci sc o Unity plays an internal greeting for subscribers who leave messages, by doing the

following sub-steps:

a. From a subscriber phone, call a subscriber who is associated with another Cisco Unity server, and

allow the call to be forwarded to voice mail.

b. Verify that the internal greeting plays.

c. Leave a test message.

Step 2 Verify that subscribers are identified when the recipient listens to a message, by doing the following

sub-steps:

a. Log on to the applicable Cisco Unity server as the recipient subscriber and listen to the test message

that you recorded in

b. Verify that the subscriber conversation announces who the message is from by playing the recorded

voice name of the sending subscriber.

c. After listening to the message, verify that the subscriber conversation allows you to reply to the

message.

Chapter 2 Digital Networking

Step 1.

To Verify Live Reply Between Subscribers on Different Cisco Unity Servers in the Dialing Domain

Do this test if the Cisco Unity servers have been configured for live reply (via release to phone system transfer) between subscribers on different Cisco

Step 1 From a subscriber phone, call a subscriber who is associated with another Cisco Unity server, and allow

Unity servers in the same dialing domain.

the call to be forwarded to voice mail.

Step 2 Leave a message.

Step 3 Log on to the applicable Cisco Unity server as the recipient subscriber and listen to the test message that

you recorded in

Step 4 After listening to the message, verify that the subscriber conversation allows you to live reply to the

Step 2.

message by pressing 4-4 (or by pressing 8-8 if Optional Conversation 1 is used).

Step 5 Verify that the live reply call is correctly transferred to the phone of the subscriber who left the message.

Digital Networking Concepts and Definitions

The following sections explain Digital Networking concepts in detail:

• Locations and Digital Networking, page 2-15

• Dialing Domains, page 2-15

• Addressing Options for Non-Networked Phone Systems, page 2-18

• Cisco Unity Administrator Scope, page 2-20

2-14

• Granting Administrative Rights to Other Cisco Unity Servers, page 2-22

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

OL-13844-01

Chapter 2 Digital Networking

• Distribution Lists, page 2-22

• System Broadcast Messages, page 2-23

Locations and Digital Networking

Central to how Digital Networking works is a Cisco Unity object called a location. Each Cisco Unity server is associated with one location, referred to as the default or primary location, which is created during installation and which cannot be deleted. With the exception of public distribution lists, all subscribers and other Cisco server are associated with the primary location.

Each primary location contains the addressing information that Cisco Unity needs to route messages between Cisco

Unity servers. Because Cisco Unity stores location and subscriber addressing information in the directory, the addressing information replicates to other Cisco network.

The primary location also contains a Dial ID, which Cisco Unity uses as an identifier for the location. Carefully plan the numbers that you choose as Dial IDs for the primary location (and for any delivery locations that you create). Without careful planning, it is possible to inadvertently assign Dial IDs that will cause problems in locating message recipients at another location. See the

section on page 9-2 and the “Location Addressing Options” section on page 9-8 for more information.

Unity objects (such as call handlers) that are created on your Cisco Unity

Digital Networking Concepts and Definitions

Unity servers on the

“Assigning Dial IDs”

Dialing Domains

A dialing domain is a collection of Cisco Unity servers that access the same directory and that are integrated with the same phone system or phone system network. (This includes Cisco are configured for dual integrations.) A dialing domain is a grouping scheme that allows Cisco handle call transfers from one Cisco extensions in Cisco unique. (Typically, a subscriber extension and phone extension are the same number.) With a networked phone system, subscribers dial a phone extension without having to dial a trunk access code or prefix when calling someone who is at another location on the phone network. In the same way, when grouped in a dialing domain, subscribers who are associated with one Cisco extension when sending messages to subscribers who are associated with another Cisco

To be in a dialing domain, all of the Cisco Unity servers must access the same directory; a dialing domain cannot span directories. Dialing domains are not related to Exchange routing groups or Active Directory sites.

To group the Cisco Unity servers in a dialing domain, you enter information on the primary location page of each Cisco

The following sections describe the functionality that can be provided when the Cisco Unity servers are in the same dialing domain:

• Release to Switch Transfers from the Automated Attendant or a Directory Handler to Subscribers

• Identified Subscriber Messaging with Networked Cisco Unity Subscribers, page 2-16

• Addressing Search Scopes, page 2-17

Unity servers that

Unity to

Unity server to another. Within the dialing domain, subscriber

Unity must be unique just as the phone extensions in the phone system must be

Unity server enter a subscriber

Unity server.

Unity server, as described in the “Customizing the Primary Location” section on page 2-6.

on Other Cisco Unity Servers, page 2-16

OL-13844-01

• Addressing Options for Subscribers in a Dialing Domain, page 2-17

• Dialing Domains Shield Against Overlapping Numbering Plans, page 2-17

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

2-15

Chapter 2 Digital Networking

Digital Networking Concepts and Definitions

Release to Switch Transfers from the Automated Attendant or a Directory Handler to Subscribers on Other Cisco

Unity Servers

By default, when a caller enters the extension of a subscriber from the automated attendant (for example, from the opening greeting), or a caller spells the name of a subscriber from a directory handler, Cisco

Unity searches only the local server for a matching subscriber. For calls to be transferred from the automated attendant or a directory handler on one Cisco Cisco

Unity server, the servers must be configured to be in the same dialing domain.

To enable this functionality, you set search scopes so that Cisco Unity searches for a matching extension or name among subscribers on other Cisco scopes, one for the automated attendant and one for each directory handler. See the

Directory Handler Search Scope” section on page 2-7 and the “Setting the Automated Attendant Search Scope” section on page 2-7 for details on how to set the search scopes.

Subscriber call transfer settings are not stored in the directory. Because the directory is the means by which Cisco transfer settings of subscribers on other Cisco the automated attendant or a directory handler to subscribers who are not associated with the local server, the transfers are automatically handled by the phone system (release to switch) rather than by Cisco

Unity (supervised transfer), even if these subscribers are set up for supervised transfers. Note the following limitations:

Unity server to a subscriber on another

Unity servers in the dialing domain. There are separate search

“Setting the

Unity servers share subscriber data, Cisco Unity servers do not have access to the call

Unity servers. By default, when calls are transferred from

• The subscriber call screening, call holding, and announce features that are available with supervised

transfers are not available on calls that have been transferred via release to switch.

• The call transfer setting that sends calls directly to the greeting of the called subscriber is not

available. This means that Cisco Cisco

Unity subscribers or AMIS, Bridge, Internet, or VPIM subscribers) who do not have phones on the phone system that Cisco dials the subscriber extension and hangs up. What happens to the call after that depends on how the phone system is configured. If you do not configure the phone system to handle this situation, the call may be dropped.

Unity cannot take messages for subscribers (either regular

Unity is integrated with. On a release to switch transfer, Cisco Unity

Identified Subscriber Messaging with Networked Cisco Unity Subscribers

When a subscriber calls another subscriber, and the call is forwarded to the greeting of the called subscriber, the ability of Cisco referred to as identified subscriber messaging. Because Cisco subscriber:

• Cisco Unity plays the internal greeting of the called subscriber when the caller leaves a message.

• Cisco Unity plays the recorded voice name of the subscriber who left the message when the recipient

listens to the message.

• Cisco Unity allows the recipient to record a reply.

For identified subscriber messaging to work when a subscriber on one Cisco Unity server calls a subscriber on another networked Cisco Note that identified subscriber messaging between Cisco

“Setting Up Identified Subscriber Messaging Between Networked Cisco Unity Subscribers (Optional)” section on page 2-8 for details.

It is important to note the difference between the following two circumstances:

Unity to identify that it is a subscriber who is leaving a message is

Unity is able to identify the caller as a

Unity server, the servers must be in the same dialing domain.

Unity servers by default is not enabled. See the

2-16

• A subscriber logs on to Cisco Unity, and then records and sends a message (“To send a message,

press 2”)

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

OL-13844-01

Chapter 2 Digital Networking

• A subscriber places a phone call to another subscriber, and then leaves a message

When the subscriber has logged on to Cisco Unity, Cisco Unity can identify the message as being from the subscriber, regardless of which Cisco the phone system is not involved and the recipient phone does not ring. Instead, the message is sent via Digital Networking.

Addressing Search Scopes

In addition to the automated attendant and directory handler search scopes mentioned above, a dialing domain provides a means to set the scope for searches that Cisco

• When a subscriber addresses a message

• When members are being added to a public or private distribution list

By default, the addressing search scope used for the above searches is set to search only among subscribers on the local Cisco Cisco

Unity server to either the dialing domain or the global directory to enable messaging between subscribers on different Cisco

page 2-6 for information on how to expand the Addressing search scope.

Digital Networking Concepts and Definitions

Unity server the message recipient is homed on. In this case,

Unity performs in the following cases:

Unity server. You must expand the addressing search scope on each

Unity servers. See the “Setting the Addressing Search Scope” section on

Addressing Options for Subscribers in a Dialing Domain

After expanding the addressing search scope to either the dialing domain or the global directory, subscribers address messages to subscribers on other Cisco messages to subscribers on the same Cisco

Unity server: either by extension or by spelling the name.

Dialing Domains Shield Against Overlapping Numbering Plans

The two requirements for grouping Cisco Unity servers into a dialing domain are that the servers access the same global directory and are integrated with the same phone system. However, the minimum requirement for the basic messaging functionality provided by Digital Networking is that all of the Cisco

Unity servers access the same global directory, as Figure 2-1 illustrates.

Figure 2-1 Multiple Phone Systems But One Global Directory

Global directory

Dialing

domain A

Unity 1

Networked

phone system

Unity 3

Phone system

Unity servers the same way that they address

OL-13844-01

Unity 2

69418

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

2-17

Digital Networking Concepts and Definitions

Subscribers on the Cisco Unity servers in the dialing domain can use the phone to send messages to and reply to messages from the subscribers on Unity 3, and vice versa. However, identified subscriber messaging is not available between the subscribers on Unity 3 and the subscribers on the Cisco servers in dialing domain A.

Although subscriber extensions must be unique within a dialing domain, it is possible that subscribers who are associated with a Cisco are the same as extensions used by subscribers who are associated with the servers within the dialing domain. In other words, it is possible that extensions may overlap in the global directory when there are Cisco

Unity servers that are integrated with different phone systems.

Grouping the Cisco Unity servers into a dialing domain allows Cisco Unity to handle overlapping numbering plans. The dialing domain allows the subscribers within the dialing domain to use extensions to address messages without conflicting with the extensions of the subscribers on the other phone system. See the

Cisco Unity Searches for a Matching Number” section on page 9-4 for a detailed description of how

dialing domains shield against overlapping numbering plans.

“How Cisco Unity Searches for a Matching Name” section on page 9-4 and the “How

Unity server outside of the dialing domain could have extensions that

Addressing Options for Non-Networked Phone Systems

Chapter 2 Digital Networking

Unity

If your organization has a separate phone system for each location, subscribers at one location dial a complete phone number, not just an extension, when calling someone at another location. When subscribers log on to Cisco number they enter when addressing the message depends on whether the Cisco overlap across locations, as described in the following sections.

When Numbering Plans Do Not Overlap

When Cisco Unity numbering plans do not overlap across locations—that is, when subscriber extensions are unique across locations—subscribers enter an extension when addressing a message to a subscriber who is associated with another Cisco

As a convenience for subscribers, you may choose to add alternate extensions to each subscriber account. With alternate extensions, the number that a subscriber enters when addressing a message to someone at another location can be the same number that the subscriber dials when calling. When set up this way, subscribers do not need to remember two different numbers—one for calling a subscriber directly, and one for addressing a message.

For example, a subscriber, Kelly Bader, has subscriber extension 4060, as illustrated in Figure 2-2. Suppose that Chris, a subscriber at a remote location, dials 456-4060 to reach Kelly by phone. When Chris logs on to Cisco (4060) and not dial the prefix (456) when addressing the message, rather than using the same number he dials to call Kelly. However, you could assign to Kelly the alternate extension 4564060. If this alternate extension has been set up, Chris can enter either 4060 or 4564060 when addressing a message to Kelly.

Unity to send a message to Kelly, he has to remember just to dial the extension

Unity to send messages to subscribers on another Cisco Unity server, the

Unity numbering plans

Unity server.

2-18

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

OL-13844-01

Chapter 2 Digital Networking

Figure 2-2 No Overlapping Extensions

Digital Networking Concepts and Definitions

Ext 4060

alt ext 456 4060

Phone system 1

If the numbering plans for each location do not overlap, setting up alternate extensions is optional because they are simply a convenience for subscribers. However, if you do not set up alternate extensions, be sure to tell subscribers to use the extension instead of the full phone number when addressing messages to subscribers who are associated with another location.

Note that alternate extensions have other purposes beyond their use in Digital Networking, such as handling multiple line appearances on subscriber phones. Subscribers can have up to nine alternate extensions. For more information, see the “Specifying Subscriber Alternate Extension Settings” 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.

When Numbering Plans Overlap

Kelly

Global directory

Unity 1

Unity 2

Chris

Phone system 2

69671

Unity, available at

Assume that subscriber extensions on Unity 3 in Figure 2-3 overlap with extensions in dialing domain A. To allow subscribers who are associated with Unity 3 to use the phone to address messages to subscribers in dialing domain A, and vice versa, you have the following choices:

• Instruct subscribers to enter one number that consists of the primary location Dial ID of the

destination Cisco

• Set up alternate extensions for each subscriber account. For each subscriber, enter a number for the

Unity server and the extension of the recipient.

alternate extension that is the same as the full phone number for the subscriber. In this way, when subscribers log on to Cisco

Unity to send messages, the number they enter when addressing

messages is the same number that they use when calling.

• Enable the Include Locations in Searches setting. When this setting is enabled, subscribers can

address a message in two steps: they first select a location (by spelling the location name or entering a Dial ID) and then spell the recipient name.

When a subscriber addresses a message, Cisco Unity searches for a matching extension on the local Cisco

Unity server first. If a match is found, Cisco Unity ends the search and never looks for a matching extension at another location. Therefore, if a local subscriber and a subscriber on another Cisco server have the same extension, Cisco

Unity will find only the subscriber on the local Cisco Unity server.

Unity

However, when one of the options described above is set up, subscribers on the local server will be able to address messages to subscribers on other Cisco

Unity servers.

OL-13844-01

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

2-19

Digital Networking Concepts and Definitions

Figure 2-3 Numbering Plans Overlap

Global directory

Dialing

domain A

Chapter 2 Digital Networking

Dialing

domain B

Networked

phone system 1

Cisco Unity Administrator Scope

With the exception of public distribution lists, all subscribers and other Cisco Unity objects (such as call handlers) that are created on your Cisco server. Because of this association, if you want to access the subscriber accounts and other objects that are created on another server, you need to run the Cisco was created on. Note that you can view information about the primary locations of other servers and the delivery locations created on other servers, but you cannot modify or delete them.

The following sections provide information about accessing the Cisco Unity Administrator on other servers:

• Browsing to Another Cisco Unity Administrator from the Local Cisco Unity Administrator, page

2-20

• Searching for Subscriber Accounts That Were Created on Another Cisco Unity Server, page 2-21

• Using Global Subscriber Manager to Browse to Another Cisco Unity Administrator, page 2-21

Unity 1

Unity 2

Unity 3

Networked

phone system 2

Unity 4

69670

Unity server are associated with the primary location of your

Unity Administrator of the server that the object

Browsing to Another Cisco Unity Administrator from the Local Cisco Unity Administrator

The Cisco Unity Administrator on the local server provides links to the Cisco Unity Administrator of other servers. To access the data of any object that was created on another Cisco to know the name of the server on which the object was created.

To Browse to Another Cisco Unity Administrator on a Networked Cisco Unity Server

Step 1 Near the bottom of the navigation bar on the left side of the Cisco Unity Administrator interface, click

Unity Servers. The Server Chooser page appears.

Step 2 From the list, click the server that you want to access.

Step 3 If prompted, enter the appropriate credentials to gain access to the Cisco Unity Administrator that you

want to access.

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

2-20

Unity server, you need

OL-13844-01

Chapter 2 Digital Networking

Digital Networking Concepts and Definitions

Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco

Unity Administrator of the server that you selected.

Searching for Subscriber Accounts That Were Created on Another Cisco Unity Server

Within the local Cisco Unity Administrator, you can search for subscribers on other Cisco Unity servers, and when you select a subscriber account to edit settings, the applicable Cisco launched. Do the following procedure to use the Cisco server to search for subscriber accounts on other Cisco

To Search for Subscriber Accounts That Were Created on a Cisco Unity Server Other than Your Local Cisco Unity Server

Step 1 In the Cisco Unity Administrator, go to any Subscribers > Subscribers page.

Step 2 Click the Find icon.

Step 3 Indicate whether to search by alias, extension, first name, or last name.

Unity Administrator on your local Cisco Unity

Unity servers in the network.

Unity Administrator is

Step 4 Enter the appropriate alias, extension, or name. You also can enter * to display a list of all subscribers,

or enter one or more characters or values followed by * to narrow your search.

Step 5 Check the Search All Cisco Unity Servers check box.

Step 6 Click Find.

Step 7 On the list of matches, click the name of the subscriber to display the record.

Step 8 If prompted, enter the appropriate credentials to gain access to the Cisco Unity Administrator that you

want to access.

Another instance of the Cisco Unity Administrator appears in a separate browser window. This is the Cisco

Unity Administrator website of the Cisco Unity server on which the subscriber account was created. The subscriber profile page is displayed in the new browser window.

Using Global Subscriber Manager to Browse to Another Cisco Unity Administrator

You can also use the Global Subscriber Manager (GSM) from Tools Depot to launch the Cisco Unity Administrator on another server. The GSM shows your entire Cisco dialing domains and servers. The GSM allows you to quickly locate individual subscribers and launch the Cisco

Unity Administrator for the subscribers regardless of which server they are homed on. You can select any scope you want and see all of the subscribers at that level. Searching can be done by dialing domain, by server, or globally across the entire Cisco

Unity network.

Unity network broken down by

OL-13844-01

To Use the GSM

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, double-click Global Subscriber Manager.

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

2-21

Digital Networking Concepts and Definitions

Step 3 Double-click the subscriber account that you want to edit. The applicable Cisco Unity Administrator will

be displayed in a browser window. See the GSM Help file for more information.

Granting Administrative Rights to Other Cisco Unity Servers

To access the Cisco Unity Administrator on another server, the administrators on the local Cisco Unity server need the applicable class of service rights. The easiest way to set this up is to run the GrantUnityAccess utility. See the “Granting Administrative Rights to Other Cisco section in the “Managing Cisco

Guide for Cisco

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

Unity for instructions. (The System Administration Guide for Cisco Unity is available

Unity Administrator Accounts” chapter in the System Administration

Distribution Lists

Public distribution lists are not associated with a specific Cisco Unity server. If a list has a recorded voice name, an extension, or both, subscribers can address messages to it—if allowed by their class of service—regardless of which location created the list.

Chapter 2 Digital Networking

Unity Servers”

New Lists

When you create a new public distribution list, keep in mind the following:

• The extension for the list must be unique in the entire directory. Therefore, you need to know which

extensions are in use at other locations before assigning an extension to the new list.

• In the Cisco Unity Administrator, you can add members from multiple locations to a list, if allowed

by the Addressing Options settings for the default location on your Cisco

“Primary Location Addressing Option Settings” section on page 9-3 for more information.

• In the Cisco Unity Administrator, you can view all members of a list regardless of the location with

which the member is associated.

Predefined Public Distribution Lists

Cisco Unity includes the following predefined public distribution lists: All Subscribers, Unaddressed Messages, and System Event Messages (the System Event Messages list is no longer created during Cisco

Unity installation; however, you may still have a System Event Messages list if you upgraded from a version of Cisco Cisco

Unity server in your organization has a distinct version of each of these lists. When you view these lists in the Cisco

By default, the predefined All Subscribers public distribution list on each Cisco Unity server has the same recorded voice name (“all subscribers”) and extension. When setting up Digital Networking, you should modify the recorded voice name and extension of each All Subscribers list; if you do not, subscribers will hear a confusing list of choices when they address messages to an All Subscribers distribution list, and errors will be logged to the Windows Event Viewer on the Cisco because of the non-unique extensions.

Unity earlier than 4.0(4), as the list is not removed during the upgrade process). Each

Unity Administrator, the Cisco Unity server name is appended to the list name.

Unity server. See the

Unity server

2-22

Tip Distribution lists can be nested, that is, a distribution list can contain other lists. If desired, you can create

one master All Subscribers distribution list that contains the All Subscribers list of each Cisco server.

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

Unity

OL-13844-01

Chapter 2 Digital Networking

By default, each Unaddressed Messages and System Event Messages distribution list has the same recorded voice name, but they are not assigned an extension because subscribers typically do not address messages to these lists.

Private Lists

When creating private lists, subscribers can add members from other locations if allowed by the Addressing Options settings for your default location. The location addressing options allow you to control the search that Cisco a subscriber addresses a message. For more information, see the

Settings” section on page 9-3.

Consider notifying subscribers in the event that the following members are inadvertently removed from their lists:

• When you delete a delivery location, blind addressees are removed from all private lists.

• When an external subscriber (that is, an AMIS, Bridge, or VPIM subscriber) becomes a regular

subscriber, the external subscriber is removed from all private lists.

System Broadcast Messages

Digital Networking Concepts and Definitions

Unity performs when a subscriber adds members to a private list and when

“Primary Location Addressing Option

System broadcast messages are recorded announcements that are sent to everyone in an organization (or to particular location(s) within an organization). System broadcast messages are played immediately after subscribers log on to Cisco saved messages. Subscribers must listen to each system broadcast message in its entirety before Cisco

Unity allows them to hear new and saved messages or to change setup options. They cannot

fast-forward or skip a system broadcast message.

System broadcast messages can be networked to all subscribers on one or more Cisco Unity servers that access the same subscriber directory by using Digital Networking. In organizations where there are multiple Cisco messages can be sent to all subscribers in the organization (or to all subscribers who are associated with specific sets of digitally networked servers), provided that the networks are connected by using the VPIM Networking option.

Unity or Cisco Unity Express servers that access different directories, system broadcast

Unity by phone—even before they hear message counts for new and

Addressing System Broadcast Messages to Digitally Networked Servers

Depending on the desired set of recipients and the options selected in the Cisco Unity Broadcast Administrator, a subscriber who has been granted permission to send system broadcast messages to subscribers on multiple servers can address messages to all subscribers on the local server, to all subscribers on one or more digitally networked servers, or to all subscribers on all servers in the domain by using Digital Networking.

For example, consider a situation in which three Cisco Unity servers share the same directory. The servers are named ChicagoUnity (dial ID 344), NewYorkUnity (dial ID 444), and AtlantaUnity (dial ID

544). A subscriber on ChicagoUnity who has been granted permission to send system broadcast messages to subscribers on multiple servers can address a message from the Cisco

Unity Broadcast

OL-13844-01

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

2-23

Chapter 2 Digital Networking

Notable Behavior

Message Administrator by using the options in Table 2-1, which result in a system broadcast being transmitted to all subscribers on the local server or to all subscribers on multiple servers within the directory.

Ta b l e 2-1 Using the Cisco Unity Broadcast Administrator to Address Messages to Servers Within the Directory

Cisco Unity Broadcast Administrator Option Selected

Send to Subscribers on this Server N/A All subscribers on ChicagoUnity

Send to Subscribers at all Locations N/A All subscribers on all Cisco Unity servers in the

Send to One or More Locations, or to a Public Distribution List

Individual Cisco Unity servers within the directory can be added by location dial ID as shown in the example above. Public distribution lists are only used for sending system broadcast messages to VPIM locations. For more information on sending system broadcast messages by using VPIM, see the

“Addressing System Broadcast Messages to Multiple Servers” section on page 8-7.

Note that when a system broadcast message is sent to multiple locations, a copy of the message is sent to each server and then distributed to the subscribers who are homed on that server. As a result, the subscriber who is sending the system broadcast message must make updates to each message locally. In this example, after the ChicagoUnity subscriber has sent a message, if updates need to be made to any properties on the message at a later time, he or she would need to have permission to log on to the Cisco

Unity Broadcast Administrator on each server to make the updates.

Extension Entered System Broadcast Recipients

directory—ChicagoUnity, NewYorkUnity, and AtlantaUnity

444 All subscribers on NewYorkUnity (dial ID 444)

444, then 544 All subscribers on NewYorkUnity (dial ID 444) and

AtlantaUnity (dial ID 544)

How Networked System Broadcast Messages are Processed by Cisco Unity

When Cisco Unity is installed, a new Windows service called CsBMessageConnector is created, along with a special mailbox that has the display name USbms_<Servername>. The USbms mailbox is created in the default directory container for Cisco CsBMessageConnector service processes messages that are placed in the USBms mailbox. For systems that use failover, the CsBMessageConnector service runs on both the primary and secondary servers, and both services access the same USbms mailbox, but only the service on the currently active server will process messages.

When a system broadcast message is addressed to multiple Cisco Unity servers, a copy of the message is placed in the USbms mailbox for each server; the CsBMessageConnector service on each server processes the message and makes it available to all Cisco start and end dates configured for the message.

Unity, and is hidden from the address book. The

Unity subscribers on the server, based on the

Notable Behavior

This section provides information about notable expected behavior associated with Digital Networking.

2-24

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

OL-13844-01

Chapter 2 Digital Networking

Mapping Subscribers to Cisco Unity Servers

Each Cisco Unity server handles a distinct group of subscribers. In large organizations, it is possible that more than one Cisco determine which subscriber accounts to create on each of the Cisco Cisco

Unity server for each subscriber), and keep a record of the mapping. This record is needed for the

following reasons:

• Subscriber phones must forward calls to the Cisco Unity server on which the subscribers are homed.

• If subscriber phones have a “Messages” or a speed-dial button that dials the number to access

Cisco

Unity, the buttons must be configured to call the Cisco Unity server on which the subscribers

are homed.

• To check their messages, subscribers must dial the Cisco Unity server that they are associated with;

therefore you need to tell subscribers the correct number to dial when calling into Cisco that if your Cisco (formerly known as Cisco Unified CallManager), you may want to configure cross-server logon. For more information, see the

To create a record of the mapping, run the Subscribers report on each Cisco Unity server. The information in this report includes the subscriber name and primary location. See the “Subscribers Report” section in the “Reports” chapter of the Maintenance Guide for Cisco information. (The Maintenance Guide for Cisco

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

Unity server will be in use at the same physical location. In this case, you need to

Unity servers are integrated with Cisco Unified Communications Manager (CM)

“Cross-Server Logon, Transfers, and Live Reply” chapter.

Notable Behavior

Unity servers (the “home”

Unity. Note

Unity for more

Unity is available at

OL-13844-01

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

2-25

Notable Behavior

Chapter 2 Digital Networking

2-26

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

OL-13844-01

CHAP T ER

Cross-Server Logon, Transfers, and Live Reply

This chapter describes the cross-server logon, transfer, and live reply features for Cisco Unity servers networked via Digital Networking. Phone system and network considerations for deploying cross-server features are discussed. The underlying architecture for the cross-server features is described, and design and monitoring recommendations are provided. Also included in this chapter are the procedures for activating the cross-server features.

See the following sections:

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

• Cross-Server Logon, page 3-5

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

• Cross-Server Live Reply, page 3-12

• Troubleshooting, page 3-15

• Dialing Domain Options Page Reference, page 3-16

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

The cross-server features are an extension of the existing Digital Networking feature. Digital Networking provides basic messaging functionality for subscribers who are homed on different Cisco

Unity servers that access the same global directory. When the networked Cisco Unity servers are integrated with the same phone system, the servers can be grouped into a dialing domain so that calls can be transferred—via release to switch—from the automated attendant (for example, from the opening greeting) or from a directory handler on one Cisco Digital Networking and dialing domains provide basic messaging and call transfer functionality for subscribers who are homed on different Cisco network continues to serve only those subscribers whose accounts were created on the server. The purpose of the cross-server features is to make the subscriber experience in a Digitally-Networked environment almost the same as in a single Cisco

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

OL-13844-01

Unity server to a subscriber on another. Even though

Unity servers, each Cisco Unity installation in the

Unity server environment, as shown in Table 3-1.

3-1

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

Ta b l e 3-1 Cross-Server Features

Feature Description

Cross-server logon Cross-server logon allows administrators to provide subscribers who are

Cross-server transfer Cross-server transfer enables calls from the automated attendant or from a

Cross-server live reply Cross-server live reply allows subscribers who listen to their messages by

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

homed on different Cisco phone number that they can call to log on to Cisco outside the organization to log on to Cisco which is their home Cisco transferred to the applicable home Cisco

directory handler of one Cisco on another Cisco

Unity server in the dialing domain, according to the call

Unity servers in the same dialing domain with one

Unity. When calling from

Unity, subscribers—no matter

Unity server—call the same number and are

Unity server to log on.

Unity server to be transferred to a subscriber

transfer and screening settings of the called subscriber.

phone to reply to a message from a subscriber on another Cisco

Unity server in the dialing domain by calling the subscriber (according to the call transfer and screening settings of the called subscriber).

Although the cross-server features are distinct features, they all use the same underlying functionality—an enhanced supervised call transfer:

1. The Cisco Unity server on which a logon, transfer, or live reply originates puts the caller on hold

and calls the home Cisco

2. When the destination Cisco Unity server answers, the originating Cisco Unity server sends a

Unity server.

sequence of DTMF tones that identify the call as a cross-server logon, transfer, or live reply.

3. The destination Cisco Unity server responds with a sequence of DTMF tones, and the originating

Cisco

Unity server hands off the call to the destination server for processing.

4. At this point the functionality is the same as though the call had originated on the home Cisco Unity

server.

In this chapter, an originating Cisco Unity server is defined as a server that calls other Cisco Unity servers. A destination Cisco

Unity server is defined as a server that answers a cross-server call.

Phone System Considerations for Cross-Server Features

The cross-server features are supported for integrations with Cisco Unified Communications Manager through PIMG/TIMG units, and/or integrations with Cisco SIP Proxy Server (CSPS). Integrations with phone systems through voice cards are not supported.

The following factors can contribute significantly to delays in cross-server call handoff:

• Longer subscriber extensions. A four-digit extension does not take as long for Cisco Unity to dial

• Longer dialing strings to reach the destination Cisco Unity server. A four-digit dialing string does

(CM) (formerly known as Cisco Unified CallManager), integrations with phone systems

as a ten-digit extension.

not take as long for Cisco

Unity to dial as a ten-digit dialing string.

3-2

• Multiple elements (such as PIMG/TIMG units, voice gateways, TDM trunks, and PSTN interfaces)

in the call path between the originating Cisco More elements in the call path require more processing time for handing off cross-server calls.

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

Unity server and the destination Cisco Unity server.

OL-13844-01

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

In your environment, these factors can create delays that may cause the cross-server features to be unusable or unfeasible for callers. You must test your cross-server configuration on a representative call path in your environment to determine whether the delays that callers experience are acceptable.

Planning for Increased Port Usage

The cross-server features require the use of ports on both the originating and destination Cisco Unity servers. Depending on how busy your Cisco additional Cisco configured. For example, you may need to enable more ports to accept incoming calls.

After enabling the cross-server features, we recommend that you monitor activity on the Cisco Unity servers closely until you are confident that the servers can handle the increased load. You can use the Port Usage Analyzer for this task. The Port Usage Analyzer is available in the Report Tools section of Tools Depot. See Port Usage Analyzer Help for detailed instructions. Be sure to monitor the Windows Event Viewer on both the originating and destination Cisco to problems with ports.

Unity server before enabling these features. You may also need to adjust how ports are

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

Unity servers are, you may need to add more ports or an

Unity servers for event log messages related

A Brief Look at Cisco Unity Data Architecture

To understand why the cross-server features are needed, it is helpful to have a basic understanding of Cisco

Unity data architecture. Cisco Unity stores information about subscribers (and other Cisco Unity objects such as call handlers) in a SQL Server database on the Cisco information about subscribers, distribution lists, and location objects is also stored in Active Directory. Because all of the Cisco access to the information stored in the directory by other Cisco distribution list, and location data from other Cisco Cisco

Unity server detects the data and updates its local SQL Server database.

The data that is stored in the directory is limited to just what is needed to provide basic Digital Networking functionality:

• Messaging between subscribers homed on different Cisco Unity servers.

• Release to switch call transfers from the automated attendant or directory handler to subscribers on

different Cisco

Why Cross-Server Logon Is Needed

Without cross-server logon, subscribers have to call the specific Cisco Unity server they are homed on to log on to their mailboxes over the phone. There are several reasons for this restriction:

• The subscriber conversation requires access to subscriber greetings and subscriber call handler, call

transfer, and call screening information. However, subscriber greetings and most of the other subscriber information is stored only on the Cisco created. This data is not replicated across the directory because of size considerations.

Unity servers access the same global directory, each Cisco Unity server has

Unity servers in the dialing domain.

Unity server. A small subset of

Unity servers. When subscriber,

Unity servers replicates in the directory, each

Unity server on which the subscriber account was

OL-13844-01

• The message store services on each Cisco Unity server log on with a domain account that has the

permissions needed to access local subscriber mailboxes. If different domain accounts are assigned to the message store facing services on other Cisco Cisco

Unity server may be unable to log on to the mailboxes of subscribers on other Cisco Unity

servers.

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

Unity servers, the message store services on one

3-3

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

Why Cross-Server Transfer Is Needed

In installations with multiple Cisco Unity servers networked via Digital Networking, the number that Cisco

Unity uses for call transfers to a subscriber is the only number replicated among the Cisco Unity servers; none of the other call transfer and screening settings are replicated. For example, in call transfers are set to ring the subscriber at the number 9,5551212. The only call transfer setting that is replicated to other Cisco “Yes, Ring Subscriber’s Extension,” the number 3047 would be replicated.

Figure 3-1 Only the Call Transfer Number Is Replicated

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

Figure 3-1,

Unity servers is the call transfer number 9,5551212. If the setting was instead

When the call transfer setting is set to “No (Send Directly to Subscriber’s Greeting),” the call transfer number is automatically set to the subscriber extension (3047 in the example in

Figure 3-1), which is

replicated to the other networked Cisco Unity servers.

Without cross-server transfer, call transfers to subscribers whose accounts were created on other Cisco

Unity servers are always handled by the phone system (release to switch)—rather than by Cisco

Unity (supervised transfer)—even if the subscribers are set up for supervised transfers (as in the example in

Figure 3-1). On a release to switch transfer, Cisco Unity dials the call transfer number

configured for the subscriber and hangs up, leaving the phone system to handle the call. Note the following limitations with release to switch transfers:

• The subscriber call screening, call holding, and announce features are ignored.

• The call transfer setting “No (Send Directly to Subscriber's Greeting)” is ignored. Cisco Unity dials

the subscriber extension and hangs up. If the subscriber extension is a valid extension on the phone system that Cisco

Unity is integrated with, the subscriber phone rings. If the subscriber extension is not a valid phone extension, what happens to the call after that depends on the phone system and how it is configured. If you do not configure the phone system to handle calls to the subscriber extensions, the caller may be disconnected.

3-4

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

OL-13844-01

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

Why Cross-Server Live Reply Is Needed

Cross-server live reply is needed for the same reasons detailed in the “Why Cross-Server Transfer Is

Needed” section on page 3-4:

• Only the subscriber call transfer number is replicated to the networked Cisco Unity servers.

• The subscriber call transfer, call screening, call holding, and announce features are ignored.

Cross-Server Logon

Without cross-server logon, subscribers need to call the Cisco Unity server on which their accounts were created to log on and access their messages. This is particularly problematic for sites that move subscribers between different Cisco account is moved to another Cisco Cisco

Unity server when calling in from outside the organization.

Cross-server logon solves the problem when the networked Cisco Unity servers are integrated with the same phone system and grouped in a dialing domain. When enabled, cross-server logon allows you to provide subscribers with one phone number that they can call to log on to Cisco organization. After cross-server logon is configured, subscribers call the pilot number for one Cisco

Unity server and are transferred correctly to their home Cisco Unity server to log on. The call is

handled as follows:

1. A subscriber calls the Cisco Unity server configured for cross-server logon and logs on to

Cisco

Unity.

2. The conversation looks up the caller’s ID in the SQL Server database to determine whether the

subscriber account is homed on the local Cisco domain.

Cross-Server Logon

Unity servers for load balancing, because each time a subscriber

Unity server, the subscriber must be notified to access a different

Unity from outside your

Unity or another Cisco Unity server in the dialing

• If the subscriber account is homed on the local server, the logon proceeds as usual.

• If the subscriber account is homed on another server, Cisco Unity plays a “Please wait” prompt (if

configured to do so), puts the subscriber on hold, and calls the subscriber home Cisco

Unity server by using the same port that the subscriber called in on. Note that if the subscriber is calling from a number that matches a primary or alternate extension, the “Please wait” prompt is the first prompt that the subscriber hears.

When the destination Cisco Unity server answers, the originating Cisco Unity server sends a sequence of DTMF tones that identifies the call as a cross-server logon.

3. The destination Cisco Unity server responds with a sequence of DTMF tones.

4. The origination server hands off the call to the destination Cisco Unity server for processing. The

conversation on the destination Cisco point, the behavior is as though the subscriber had called the destination Cisco

Unity server prompts for the subscriber password. At this

Unity server directly.

The intended use of this feature is limited to subscribers calling in from outside your organization. Also note that:

• Subscriber phones must still forward calls to the subscriber home Cisco Unity server.

• On subscriber phones, the “Messages” or speed-dial button that dials the number to access

Cisco

Unity must still be configured to call the home Cisco Unity server of the subscriber.

OL-13844-01

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

3-5

Cross-Server Logon

Although cross-server logon will transfer the calls to the home server in the above cases, doing so for a large number of subscribers will increase the load on the Cisco subscriber account is moved to another Cisco to call the home server.

Unity server, the subscriber phone still must be configured

Prerequisites: Enabling Cross-Server Logon

• All of the Cisco Unity servers must be configured for Digital Networking as described in the

“Setting Up Digital Networking” section on page 2-3.

• The cross-server features are supported for integrations with Cisco Unified Communications

Manager through PIMG/TIMG units, and/or integrations with Cisco SIP Proxy Server (CSPS). Integrations with phone systems through voice cards are not supported. See the

for Cross-Server Features” section on page 3-2 for more information.

(CM) (formerly known as Cisco Unified CallManager), integrations with phone systems

Task List: Enabling Cross-Server Logon

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

Unity servers. Therefore, when a

“Phone System Considerations

Use the following task list to enable cross-server logon. The cross references take you to detailed procedures.

1. Verify that all of the networked Cisco Unity servers are configured to be in the same dialing domain,

as described in the

2. On the destination Cisco Unity servers, verify that the Cisco Unity call routing rules are set to route

calls to the Opening Greeting call handler. (This is the default when Cisco installed.) See the

Greeting” section on page 3-6.

3. On the Cisco Unity server that you have designated to handle cross-server logons (the server that

subscribers will be calling), enable cross-server logon and enter the pilot numbers of the destination Cisco

Unity servers. See the “Enabling Cross-Server Logon and Entering the Pilot Numbers of

Destination Cisco Unity Servers” section on page 3-7.

4. Test the cross-server logon functionality. See the “Testing Cross-Server Logon” section on page 3-7.

Note Subsequently, if a new Cisco Unity server is added to the dialing domain, you will have to add the pilot

number of the new server to the Network > Dialing Domain Options page.

“Customizing the Primary Location” section on page 2-6.

“Verifying That Call Routing Rules Are Set to Route Calls to the Opening

Procedures: Enabling Cross-Server Logon

Verifying That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Unity is initially

3-6

Do the following procedure on each of the destination servers. For failover systems, do the procedure on both the primary and secondary servers.

To Verify That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Step 1 In the Cisco Unity Administrator, go to the Call Routing > Direct Calls page.

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

OL-13844-01

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

Cross-Server Logon

Step 2 Verify that calls to the pilot number for the server are routed to the Opening Greeting.

The Default Call Handler routing rule (which cannot be deleted or modified) sends calls to the Opening Greeting. Therefore, if you have not added any routing rules, the server is already set to correctly process cross-server calls.

Enabling Cross-Server Logon and Entering the Pilot Numbers of Destination Cisco Unity Servers

If the system is using failover, do the following procedure on both the primary and secondary server, because most of the settings on the Network > Dialing Domain Options page are stored in the registry. (Registry settings are not replicated to the secondary server.)

To Enable Cross-Server Logon and to Enter the Pilot Numbers of Destination Cisco Unity Servers

Step 1 In the Cisco Unity Administrator, go to the Network > Dialing Domain Options page.

Step 2 In the Cross Server Logon section, check the Subscribers Dial the Same Number to Log On to

Cisco

Unity check box.

Step 3 In the Pilot Numbers for Cross-Server Logon, Transfer, and Live Reply section, enter the pilot number

in the Dial String field for each Cisco that you enter are stored in the SQL Server database UnityDb on the Cisco the system is using failover, the pilot numbers will be replicated to the secondary server.)

Step 4 Check the Play Prompt During Cross-Server Logon, Transfer, and Live Reply so That Callers

Know Something Is Happening check box. Although playing the “Please wait” prompt is optional, we

recommend that you check the check box because the cross-server process can take several seconds before the destination Cisco

Unity prompts subscribers to enter their passwords.

Unity server displayed in the table. (Note that the pilot numbers

Unity server. Therefore, if

Note It is particularly important for the “Please wait” prompt to be played when a subscriber calls

from a phone number configured as a primary or alternate extension, because the originating Cisco played, the first prompt that the subscriber hears will be when the destination server prompts for a password, which could take several seconds.

Step 5 Click the Save icon.

Testing Cross-Server Logon

We recommend that you test cross-server logon before allowing subscribers to use the feature.

For failover systems, first test that the primary destination servers answer cross-server calls. Then manually fail over the destination servers to verify that the secondary server answers cross-server calls. If the destination servers are properly configured for failover, the secondary server should answer cross-server calls when the primary server is unavailable.

Unity server will not prompt for the subscriber ID. If the “Please wait” prompt is not

OL-13844-01

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

3-7

Cross-Server Transfer from the Automated Attendant and Directory Handlers

To Test Cross-Server Logon

Step 1 For each number listed in the Pilot Numbers section on the Network > Dialing Domain Options page,

use a phone to call the number and verify that the call is routed to the Opening Greeting of the destination Cisco

Unity server.

Step 2 Create a new subscriber account (or use an existing account) on each of the destination servers for testing

purposes. Be sure to verify that the subscriber account information has replicated to all of the Cisco

Unity servers that you will be testing. The time that it takes for the subscriber data to replicate

depends on your network configuration and replication schedule.

Step 3 For each subscriber account, call the pilot number for the server configured for cross-server logon, and

attempt to logon. Verify that:

• The “Please wait” prompt is played (if configured to do so).

• You successfully log on.

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

Cross-Server Transfer from the Automated Attendant and Directory Handlers

A cross-server transfer is a special kind of supervised transfer that passes control of a call from the automated attendant or a directory handler to the home Cisco

1. A caller calls a Cisco Unity server on which an audio text application has been configured.

2. The caller does one of the following:

–

In a call handler (such as the opening greeting), enters the extension of a subscriber on another Cisco

Unity server in the dialing domain, or

–

In a directory handler, spells the name of a subscriber on another Cisco Unity server in the dialing domain.

3. The Cisco Unity server that is handling the call puts the caller on hold, and calls the subscriber home

Cisco

Unity server.

4. When the destination Cisco Unity server answers, the originating Cisco Unity server sends a

sequence of DTMF tones that identify the call as a cross-server transfer.

5. The destination server responds with a sequence of DTMF tones.

6. The originating server hands off the call to the destination Cisco Unity server for processing. At this

point, the behavior is as though the caller had directly called the automated attendant or directory handler on the destination Cisco

When cross-server transfers have been configured, subscriber call transfer, call screening, call holding, and announce features are available.

Unity server.

Unity server of the called subscriber.

Prerequisites: Enabling Cross-Server Transfer

• All of the Cisco Unity servers must be configured for Digital Networking as described in the

“Setting Up Digital Networking” section on page 2-3.

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

3-8

OL-13844-01

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

Cross-Server Transfer from the Automated Attendant and Directory Handlers

• The cross-server features are supported for integrations with Cisco Unified Communications

Manager through PIMG/TIMG units, and/or integrations with Cisco SIP Proxy Server (CSPS). Integrations with phone systems through voice cards are not supported. See the

for Cross-Server Features” section on page 3-2 for more information.

(CM) (formerly known as Cisco Unified CallManager), integrations with phone systems

Task List: Enabling Cross-Server Transfer

Use the following task list to enable cross-server transfer. The cross references take you to detailed procedures.

1. Verify that all of the networked Cisco Unity servers are configured to be in the same dialing domain,

as described in the

2. Verify that the directory handler and automated attendant search scopes have been set to the dialing

domain, as described in the

Search Scopes” section on page 2-6.

3. On the destination Cisco Unity servers, verify that the Cisco Unity call routing rules are set to route

calls to the Opening Greeting call handler. (This is the default setting when Cisco installed.) See the

Greeting” section on page 3-9.

4. On the Cisco Unity server that has the audio-text application that handles calls from outside callers,

enable cross-server transfer and enter the pilot numbers of the destination Cisco the

“Enabling Cross-Server Transfer and Entering the Pilot Numbers of Destination Cisco Unity

Servers” section on page 3-10.

“Customizing the Primary Location” section on page 2-6.

“Setting the Addressing, Directory Handler, and Automated Attendant

“Verifying That Call Routing Rules Are Set to Route Calls to the Opening

“Phone System Considerations

Unity is initially

Unity servers. See

5. Optionally, if you want to enable cross-server transfers to external subscribers, change the

“Networking—Cross-Server Transfer Behavior for External Subscribers” setting in the Advanced Settings Tool. Both the originating and destination Cisco later to enable this feature. See the

Subscribers” section on page 3-10.

6. Optionally, if you want to enable the transfer override digit sequence for subscribers that are homed

on other Cisco Transfer Handoff” setting in the Advanced Settings Tool. Both the originating and destination Cisco

Unity servers must be at version 5.0(1) or later to enable this feature. See the “Optional:

Enabling Transfer Override on Cross-Server Transfer Handoff” section on page 3-11.

7. Test the cross-server logon functionality. See the “Testing Cross-Server Transfer” section on

page 3-11.

Note Subsequently, if a new Cisco Unity server is added to the dialing domain, you will need to add the pilot

number of the new server to the Network > Dialing Domain Options page.

Unity servers, change the “Networking—Allow Transfer Override on Cross-Server

“Optional: Enabling Cross-Server Transfer for External

Unity servers must be at version 5.0(1) or

Procedures: Enabling Cross-Server Transfer

Verifying That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Do the following procedure on each of the destination servers. For failover systems, do the procedure on both the primary and secondary servers.

OL-13844-01

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

3-9

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

Cross-Server Transfer from the Automated Attendant and Directory Handlers

To Verify That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Step 1 In the Cisco Unity Administrator, go to the Call Routing > Direct Calls page.

Step 2 Verify that calls to the pilot number for the server are routed to the Opening Greeting.

Enabling Cross-Server Transfer and Entering the Pilot Numbers of Destination Cisco Unity Servers

To Enable Cross-Server Transfer and to Enter the Pilot Numbers of Destination Cisco Unity Servers

Step 1 In the Cisco Unity Administrator, go to the Network > Dialing Domain Options page.

Step 2 Click Pass Control to the Called Subscriber's Cisco Unity Server.

Step 3 In the Pilot Numbers for Cross-Server Logon, Transfer, and Live Reply section, enter the pilot number

in the Dial String field for each Cisco

Unity server displayed in the table. (Note that the pilot numbers that you enter are stored in the SQL Server database UnityDb on the Cisco the system is using failover, the pilot numbers will be replicated to the secondary server.)

Step 4 Check the Play Prompt During Cross-Server Logon, Transfer, and Live Reply so That Callers

Know Something Is Happening check box. Although playing the “Please wait” prompt is optional, we

recommend that you check the box because the cross-server process can take several seconds before the caller is transferred.

Click the Save icon.

Optional: Enabling Cross-Server Transfer for External Subscribers

By default, transfers to external subscribers (AMIS, Bridge, VPIM, Internet, and Trusted Internet subscribers) who are homed on a server in the dialing domain other than the server from which the transfer is initiated will be conducted as release to switch transfers. Do the following procedure if you want transfers to external subscribers who are homed on another Cisco cross-server transfer. Note that both the originating and destination Cisco Cisco

Unity version 5.0(1) or later to enable this feature.

Unity server. Therefore, if

Unity server to be done via

Unity servers must be at

3-10

To Enable Cross-Server Transfer for External Subscribers

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Networking—Cross-Server Transfer Behavior for External

Subscribers.

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

OL-13844-01

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

Cross-Server Transfer from the Automated Attendant and Directory Handlers

Step 4 In the New Value list, click 0, and then click Set.

Step 5 When prompted, click OK.

You do not need to restart the Cisco Unity software or server when you make a change.

Note For Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on

the other Cisco Unity server, because registry changes are not replicated.

Optional: Enabling Transfer Override on Cross-Server Transfer Handoff

When a caller enters an extension in the automated attendant followed by the digits “#2,” the caller will be routed directly to the greeting for the extension entered without a transfer being attempted. This is known as the transfer override digit sequence. By default, the transfer override digit sequence is ignored when the subscriber who is associated with the extension preceding the “#2” is homed on another Cisco

Unity server in the dialing domain. If you want to enable the transfer override digit sequence for subscribers who are homed on other Cisco originating and destination Cisco

Unity servers must be at version 5.0(1) or later to enable this feature.

Unity servers, do the following procedure. Both the

To Enable Transfer Override on Cross-Server Transfers

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, under Administrative Tools, double-click Advanced Settings Tool.

Step 3 In the Unity Settings pane, click Networking—Allow Transfer Override on Cross-Server Transfer

Handoff.

Step 4 In the New Value list, click 1, and then click Set.

Step 5 When prompted, click OK.

You do not need to restart the Cisco Unity software or server when you make a change.

Note For Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on

the other Cisco Unity server, because registry changes are not replicated.

Testing Cross-Server Transfer

We recommend that you test cross-server transfer before allowing subscribers to use the feature.

OL-13844-01

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

3-11

Cross-Server Live Reply

To Test Cross-Server Transfer

Step 1 For each number listed in the Pilot Numbers section on the Network > Dialing Domain Options page,

use a phone to call the number and verify that the call is routed to the Opening Greeting of the destination Cisco

Unity server.

Step 2 Create a new subscriber account (or use an existing account) on each of the destination servers for testing

purposes.

Step 3 For each subscriber account, call the pilot number for the server configured for cross-server transfer, and

enter the subscriber extension at the opening greeting. Verify that:

• The “Please wait” prompt is played.

• The call is transferred to the subscriber phone or the greeting, according to the call transfer settings

of the called subscriber.

Cross-Server Live Reply

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

Live reply, when enabled, allows a subscriber who is listening to messages by phone to reply to another subscriber message by calling the subscriber directly. Note that whether subscribers have access to the live reply feature is controlled by the class of service.

In order for the live reply option to be offered when a subscriber listens to a message that was left by a subscriber on another Cisco and the Cisco

Unity server on which the message was recorded must have identified the sender of the

Unity server in the dialing domain, cross-server live reply must be enabled

message as a subscriber. By default, live reply between subscribers who are homed on different Cisco

Unity servers is not enabled.

When live reply and cross-server live reply are enabled:

1. After listening to a message from a subscriber on another Cisco Unity server in the dialing domain,

a subscriber chooses to call the subscriber who left the message.

Note that if identified subscriber messaging (ISM) between networked servers has not been set up, or if ISM is disabled on the Cisco only be available for messages that are sent by subscribers who log on to Cisco

Unity server that recorded the message, the live reply option will

Unity and address

and send the message from their mailboxes.

2. Cisco Unity puts the subscriber on hold and looks up the extension in the SQL Server database to

determine whether the subscriber who is being replied to is on the same server or is on another Cisco

Unity server in the dialing domain. If the subscriber is on the same server, processing

proceeds as usual.

However, if the subscriber who is being replied to is on another Cisco Unity server, the local Cisco

Unity server calls the applicable home Cisco Unity server.

3. When the destination Cisco Unity server answers, the originating Cisco Unity server sends a

sequence of DTMF tones that identify the call as a cross-server live reply.

3-12

4. The destination server responds with a sequence of DTMF tones.

5. The originating server hands off the call to the destination Cisco Unity server for processing. Note,

however, that if the subscriber account on the destination server is set to disable call transfers (that is, the call transfer option is set to send calls to the subscriber greeting), the live reply call fails. In

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

OL-13844-01

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

this case, the subscriber conversation on the originating Cisco Unity plays a prompt to the caller saying that live reply is unavailable and suggesting that the caller reply to the message instead of calling the subscriber directly.

Prerequisites: Enabling Cross-Server Live Reply

• All of the Cisco Unity servers must be configured for Digital Networking as described in the

“Setting Up Digital Networking” section on page 2-3.

• The cross-server features are supported for integrations with Cisco Unified Communications

Manager through PIMG/TIMG units, and/or integrations with Cisco SIP Proxy Server (CSPS). Integrations with phone systems through voice cards are not supported. See the

for Cross-Server Features” section on page 3-2 for more information.

• Subscribers must belong to a class of service for which live reply is enabled. Live reply is enabled

on the Subscribers > Class of Service > Messages page in the Cisco checking the Subscribers Can Reply to Messages from Subscribers by Calling Them check box.

• Transfer numbers must be configured for each Cisco Unity subscriber.

• For live reply to be available to messages that were sent when the sender called the recipient from

a recognized phone number and was forwarded to Cisco must be set up between networked Cisco

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

(CM) (formerly known as Cisco Unified CallManager), integrations with phone systems

Unity servers. See the “Setting Up Identified Subscriber

Cross-Server Live Reply

“Phone System Considerations

Unity Administrator, by

Unity, identified subscriber messaging

Task List: Enabling Cross-Server Live Reply

Use the following task list to enable cross-server live reply. The cross references take you to detailed procedures.

1. Verify that all of the networked Cisco Unity servers are configured to be in the same dialing domain,

as described in the

2. Verify that the directory handler and automated attendant search scopes have been set to the dialing

domain, as described in the

Search Scopes” section on page 2-6.

3. On the destination Cisco Unity servers, verify that the Cisco Unity call routing rules are set to route

calls to the Opening Greeting call handler. (This is the default when Cisco installed.) See the

Greeting” section on page 3-14.

4. On each Cisco Unity server in the dialing domain, enable cross-server live reply and enter the pilot

numbers of the destination Cisco

Entering the Pilot Numbers of Destination Cisco Unity Servers” section on page 3-14.

5. Test the cross-server live reply functionality. See the “Testing Cross-Server Live Reply” section on

page 3-14.

Note Subsequently, if a new Cisco Unity server is added to the dialing domain, you will need to add the pilot

number of the new server to the Network > Dialing Domain Options page of each Cisco the dialing domain.

“Customizing the Primary Location” section on page 2-6.

“Setting the Addressing, Directory Handler, and Automated Attendant

“Verifying That Call Routing Rules Are Set to Route Calls to the Opening

Unity servers. See the “Enabling Cross-Server Live Reply and

Unity is initially

Unity server in

OL-13844-01

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

3-13

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

Cross-Server Live Reply

Procedures: Enabling Cross-Server Live Reply

Verifying That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Do the following procedure on each Cisco Unity server in the dialing domain. For failover systems, do the procedure on both the primary and secondary servers.

To Verify That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Step 1 In the Cisco Unity Administrator, go to the Call Routing > Direct Calls page.

Step 2 Verify that calls to the pilot number for the server are routed to the Opening Greeting.

Enabling Cross-Server Live Reply and Entering the Pilot Numbers of Destination Cisco Unity Servers

Do the following procedure on each Cisco Unity server in the dialing domain. If the system is using failover, do the following procedure on both the primary and secondary server, because most of the settings on the Network > Dialing Domain Options page are stored in the registry. (Registry settings are not replicated to the secondary server.)

To Enable Cross-Server Live Reply and to Enter the Pilot Numbers of Destination Cisco Unity Servers

Step 1 In the Cisco Unity Administrator, go to the Network > Dialing Domain Options page.

Step 2 In the Cross-Server Live Reply section, check the Subscribers Can Call Back a Cisco Unity

Subscriber on a Different Cisco

Step 3 In the Pilot Numbers for Cross-Server Logon, Transfer, and Live Reply section, enter the pilot number

Step 4 Check the Play Prompt During Cross-Server Logon, Transfer, and Live Reply so That Callers

Know Something Is Happening check box. Although playing the “Please wait” prompt is optional, we

recommend that you check the box because the cross-server process can take several seconds before the caller is transferred.

Step 5 Click the Save icon.

Unity Server check box.

Unity server displayed in the table. (Note that the pilot numbers

Unity server. Therefore, if

Testing Cross-Server Live Reply

We recommend that you test cross-server transfer before allowing subscribers to use the feature.

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

3-14

OL-13844-01

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

To Test Cross-Server Live Reply

Step 1 For each number listed in the Pilot Numbers section on the Network > Dialing Domain Options page,

use a phone to call the number and verify that the call is routed to the Opening Greeting of the destination Cisco

Unity server.

Step 2 Create a new subscriber account (or use an existing account) on each Cisco Unity server in the dialing

domain for testing purposes. Make sure that the test subscribers belong to a class of service in which live reply is enabled, and that call transfers are enabled in the subscriber accounts.

Step 3 Log on as a subscriber on one Cisco Unity server and send a message to the test subscribers on the other

Cisco

Unity servers.

Step 4 For each subscriber that receives the test message, log on, listen to the message, and choose to call the

subscriber. Verify that:

• The “Please wait” prompt is played (if configured to do so).

• The call is transferred to the subscriber phone of the subscriber who left the message.

Troubleshooting

You can use the following tools to troubleshoot problems with cross-server logon, transfer, and live reply, on both the originating and destination Cisco

• The Windows application event logs

• The Port Status Monitor, available in Tools Depot

• The Unity Diagnostic tool, available in Tools Depot. In the Unity Diagnostic tool, enable the

following micro traces:

–

• When gathering log files in the Unity Diagnostic tool, select the applicable AvCsMgr log file. For

SCCP (skinny) integrations, gather the applicable svchost log file.

Unity servers:

CDE: 10 State Machine Trace

Conversation: 10 Call Progress

MiuCall: All traces

MiuGeneral: 12, 13, 14, 16 (12 Tapi Events, 13 Tone Generation/Detection, 14 Digit Generation/Detection, 16 Event Wait Result) For SIP or PIMG integrations, also enable: 20, 21, 22 (20 Sip Media, 21 Sip Call Control State Machine, and 22 Sip Media State Machine)

MiuMethods: All traces

For SCCP (skinny) integrations: All Skinny TSP traces.

OL-13844-01

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

3-15

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

Dialing Domain Options Page Reference

For information about dialing domain options settings, see the “Dialing Domain Options Page” section in the “Network Settings” chapter of the Interface Reference Guide for the Cisco available at

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

Unity Administrator,

3-16

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

OL-13844-01

Internet Subscribers

See the following sections:

• Overview: Internet Subscribers, page 4-1

• Prerequisites for Setting Up Internet Subscriber Accounts, page 4-1

• Creating Internet Subscriber Accounts, page 4-2

• Internet Subscriber Concepts and Definitions, page 4-11

Overview: Internet Subscribers

By creating Internet subscriber accounts, you enable Cisco Unity subscribers to send voice messages to recipients whose computers are connected to the Internet. Messages are sent over the Internet or any TCP/IP network via the Simple Mail Transfer Protocol (SMTP). The recipient receives a voice message as an e-mail with a WAV attachment.

CHAP T ER

In this chapter, you will find procedures for creating Internet subscriber accounts, followed by detailed discussions of the concepts and terminology you need to understand.

Prerequisites for Setting Up Internet Subscriber Accounts

Before creating the Internet subscriber accounts, verify that the following prerequisites have been met.

• Cisco Unity is already installed on the server(s), and they are connected to the network as applicable

for your installation.

• The Exchange servers have been configured as applicable for your installation such that Cisco Unity

subscribers can send e-mail to the people who will have Internet subscriber accounts. Cisco hands off messages to Exchange for delivery; therefore, if e-mail is successfully delivered, there should not be a problem with the delivery of voice messages.

• If you will be creating Trusted Internet subscribers, you must first configure at least one Trusted

Internet Location, and install the Voice Connector for Exchange 2000 for Trusted Internet Locations.

In installations with multiple Cisco Unity servers networked together via Digital Networking, Internet subscriber accounts can be created on any Cisco set up for Digital Networking as described in the settings:

Unity server. After the Cisco Unity servers have been

“Digital Networking” chapter, verify the following

Unity

OL-13844-01

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

4-1

Creating Internet Subscriber Accounts

• Verify that the addressing search scope is set to either the dialing domain or the global directory on

all of the networked servers, so that Cisco

Unity subscribers, no matter which server they are associated with, can send messages to Internet subscribers. See the

Scope” section on page 2-6 for details.

• If you want outside callers to be able to reach Internet subscribers from the automated attendant (for

example, from the opening greeting) or from directory assistance:

–

Verify that the Cisco Unity server(s) on which the Internet subscribers will be created are in the same dialing domain as the Cisco

Unity server that outside callers call into. See the

“Customizing the Primary Location” section on page 2-6 for details on creating the dialing

domain, and the “Dialing Domains” section on page 2-15 for background information.

–

Verify that the automated attendant and directory handler(s) search scopes are set to the dialing domain scope. See the

“Setting the Directory Handler Search Scope” section on page 2-7 and

the “Setting the Automated Attendant Search Scope” section on page 2-7.

Creating Internet Subscriber Accounts

You can create Internet subscriber accounts by using the Cisco Unity Bulk Import wizard or the Cisco

Unity Administrator. See the following sections:

Chapter 4 Internet Subscribers

“Setting the Addressing Search

• Before Creating Internet Subscriber Accounts, page 4-2

• Before Creating Trusted Internet Subscriber Accounts, page 4-4

• Using the Cisco Unity Bulk Import Wizard to Create Multiple Internet Subscriber Accounts, page

4-6

• Correcting Import Errors, page 4-8

• Using the Cisco Unity Administrator to Create Internet Subscriber Accounts, page 4-9

• Enabling Cross-Server Transfer for Internet Subscribers, page 4-10

• After Creating Internet Subscriber Accounts, page 4-10

Before Creating Internet Subscriber Accounts

This section lists—in order—the issues that you must consider before creating Internet Subscriber accounts.

1. Cisco Unity Configuration and Permissions

If you are unsure whether the account that you are using has sufficient rights and permissions to create Internet subscribers, or whether Cisco the following procedure to run the SysCheck diagnostic tool.

To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool

Unity is properly configured to work with your message store, use

4-2

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane of the Tools Depot window, in the Diagnostic Tools directory, double-click SysCheck.

Step 3 On the Welcome to the Cisco Unity Configuration wizard page, click Select Configuration Tests, and

click Next.

Step 4 Uncheck the check boxes for the message stores that are not connected to Cisco Unity.

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

OL-13844-01

Chapter 4 Internet Subscribers

Step 5 Click Te st.

Step 6 In the Test Results box, click the link provided to view the test results.

Step 7 If no errors are reported, proceed to Step 8. Otherwise, do the following sub-steps:

a. Follow the advice offered in the Resolution column to correct each configuration or permissions

b. Return to the Completing the Check Unity Configuration wizard page, and click Finish.

c. Repeat Step 2 through Step 7 until no errors are reported.

Step 8 Click Finish.

2. Classes of Service

A class of service (COS) defines limits and permissions for subscribers who use Cisco Unity. For example, a COS dictates the maximum length of subscriber messages and greetings. Although most COS settings are not applicable to Internet subscribers, they still must be members of a COS. In the Cisco to the COS that is specified in the template upon which the Internet subscriber account is based. Cisco of service. For details, see the “Managing Classes of Service” chapter in the System Administration

Guide for Cisco

Creating Internet Subscriber Accounts

error.

Unity Administrator, a COS is specified in each subscriber template; thus, a subscriber is assigned

Unity includes predefined classes of service that you can modify. You can also create new classes

Unity.

3. Restriction Tables

Each COS specifies a restriction table for call transfers, one for message notification, and one for fax deliveries. Cisco an error message if the phone number is not allowed. Cisco

Unity applies the restriction table associated with the COS of a subscriber, and displays

Unity comes with predefined restriction

tables that you can modify.

Although most restriction table settings do not apply to Internet subscribers because they cannot log on to Cisco

Unity or use the Cisco Personal Communications Assistant (PCA), administrators can enter call transfer numbers for Internet subscribers. For security purposes, you should modify the restriction table used for transfers in the COS to which Internet subscribers belong, as necessary. For details, see the “Managing Restriction Tables” chapter in the System Administration Guide for Cisco

4. Public Distribution Lists

Unity.

Public distribution lists are used to send voice messages to multiple subscribers at the same time. Cisco

Unity assigns new subscribers to the public distribution lists that are specified in the template on which the Internet subscriber account is based. For details, see the “Managing Distribution Lists” chapter in the System Administration Guide for Cisco

5. Subscriber Templates

Unity.

In the Cisco Unity Administrator, you can specify settings for a group of Internet subscribers by using a subscriber template. Subscriber templates contain settings that are applicable for subscribers of a particular type, such as a department. The settings from the template you choose are applied to Internet subscriber accounts as they are created. Cisco

Unity comes with a default subscriber template that you can modify, and you can create an unlimited number of additional templates. For more details, see the “Managing Subscriber Templates” chapter in the System Administration Guide for Cisco

Unity.

Internet subscribers correspond to contacts in Active Directory. The contacts are listed in the address book for Microsoft Outlook (or other e-mail client), unless they are explicitly hidden. You may prefer that the associated contacts do not appear in the Outlook address book at all, or you may want to alter how contacts appear in the Outlook address book.

OL-13844-01

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

4-3

Creating Internet Subscriber Accounts

Note The System Administration Guide for Cisco Unity is available at

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

Before Creating Trusted Internet Subscriber Accounts

Before creating Trusted Internet subscriber accounts, you must also consider the following two issues in addition to the issues listed in the

1. Trusted Internet Locations

You must first create as least one Trusted Internet Location.

You can create Trusted Internet delivery locations by using the Cisco Unity Administrator or the Cisco

Unity Bulk Import wizard.

To Create Trusted Internet Delivery Locations by Using the Cisco Unity Administrator

Step 1 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Profile page.

Step 2 Click the Add icon.

“Before Creating Internet Subscriber Accounts” section on page 4-2:

Chapter 4 Internet Subscribers

Step 3 Enter a meaningful name for the location.

Step 4 Enter the Dial ID, which identifies the location in Cisco Unity, and which subscribers use to blind

address messages to recipients at this location.

Step 5 Select Tru s t e d I nternet as the Destination Type for the location.

Step 6 Click Add.

Step 7 Record a voice name for the location.

Step 8 If you are using Secure Messaging, indicate whether to have outgoing messages decrypted.

Step 9 Click the Save icon.

If you prefer to create Trusted Internet delivery locations by using the Cisco Unity Bulk Import wizard, see the Cisco

2. Voice Connector for Exchange 2000

Unity Bulk Import wizard Help for instructions.

You must install the Voice Connector for Trusted Internet Locations.

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

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

Do the following two procedures in the order listed.

4-4

The following procedure is for installing Voice Connector version 12.0(1), which ships with Cisco

Unity 5.0(1). We recommend that you first check for a later version of the Voice Connector, and that you install that version instead. Follow the installation instructions in the release notes for the applicable version. To check for a later version, go to the Cisco Software Download page at

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

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

Unity Voice Connector for Exchange

OL-13844-01

Chapter 4 Internet Subscribers

To Install the Voice Connector for Exchange 2000

Step 1 Log on to the Exchange server on which you are installing the Voice Connector.

Step 2 Disable any virus-scanning services on the Exchange server.

Step 3 If Cisco Unity is also on the server on which you are installing the Voice Connector, disable the Cisco

Security Agent service, if applicable.

Step 4 If you are installing the Voice Connector from a Cisco Unity DVD or CD, insert the disc in the computer,

and browse to the VoiceConnector-Ex2000 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 5 Double-click Install.exe, and click Next.

Step 6 On the Voice Connector Setup Wizard Select Components dialog box, check the Voice Connector for

Exchange check box.

Step 7 If you are setting up secure messaging and if Cisco Unity is not on the Exchange server, check the Cisco

Secure Messaging Service check box.

Step 8 Click Next.

Creating Internet Subscriber Accounts

Step 9 On the Welcome screen, click Next.

Step 10 On the Confirm SMTP Pickup Directory screen, click Next.

Step 11 In the Address Types dialog, check the Trusted Internet Location check box.

Step 12 If you are setting up the system to use other networking options, check the check boxes of the applicable

address types.

Note Setting up VPIM Networking also requires the installation of the Transport Event Sink.

Step 13 Click Next.

Step 14 On the Confirm Directory dialog box, click Next to launch the setup.

Step 15 If you did not check the Cisco Secure Messaging Service check box in Step 7, skip to Step 16.

Otherwise, do the following sub-steps in the Cisco Unity Secure Messaging Service Setup wizard:

a. On the Welcome screen, click Next.

b. On the Choose Destination Folder dialog, specify the destination, and click Next.

c. Optionally, on the Message Security Settings screen, check the Enable Message Aging check box,

and enter the number of days that encrypted messages should be available. (If the check box is unchecked, Cisco

d. Click Next.

e. On the Ready to Install Software screen, click Install.

Step 16 When the setup is complete, click Finish to exit Setup and restart the server.

Unity will not limit the number of days that encrypted messages will be available.)

OL-13844-01

Step 17 Enable virus-scanning and the Cisco Security Agent services, if applicable.

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

4-5

Creating Internet Subscriber Accounts

To view Voice Connector properties in Exchange System Manager, Windows Script Host version 5.6 or later must be installed on the Exchange server. (Note that if the Exchange server uses an earlier version of Windows Script Host, the Voice Connector functions properly, but you will not be able to view Voice Connector properties in Exchange System Manager.)

To Determine Whether to Update Windows 2000 Script Host

Step 1 On the Exchange server on which the Voice Connector has been installed, browse to Winnt\System32.

Step 2 Right-click the file Wshom.ocx, and click Properties.

Step 3 Click the Ve rs io n tab.

Step 4 In the Item Name list, click Product Version to view the version in the Value box.

Step 5 If the version is earlier than 5.6, update Windows Script Host so the Voice Connector properties can be

displayed in Exchange System Manager. (Go to the downloads page of the Microsoft website, and do a keyword search for Windows Script Host. Follow the installation instructions.)

Chapter 4 Internet Subscribers

Using the Cisco Unity Bulk Import Wizard to Create Multiple Internet Subscriber Accounts

The Cisco Unity Bulk Import wizard allows you to create multiple Internet subscriber accounts at once by importing user data directly from Active Directory, or by importing user data from a comma-separated value (CSV) file. CSV is a common text file format for moving data from one data store to another.

As long as the user data contained in the CSV file is formatted correctly, you can use it to create new Active Directory contacts at the same time that you create Internet subscriber accounts. Alternatively, the Cisco with existing Active Directory contact data.

To create Internet subscriber accounts by importing user data directly from Active Directory, see the “To

Create Internet Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard” procedure on page 4-7. Otherwise, use the following “To Prepare a CSV File for Creating Internet Subscriber Accounts” procedure to prepare your CSV file. See the Cisco Unity Bulk Import wizard Help to find

additional information about using the wizard to create Internet subscriber accounts, or about the required and optional column headers for your CSV file.

To Prepare a CSV File for Creating Internet Subscriber Accounts

Step 1 Save the data that you will use to create Cisco Unity accounts as a CSV file.

As a best practice, do not include more than 7,500 records in a single CSV file, as you may encounter unexpected results when the Cisco

Unity Bulk Import wizard allows you to use a CSV file to create Internet Subscriber accounts

Unity Bulk Import wizard imports the data.

4-6

Step 2 Copy the CSV file to the Cisco Unity server or to a directory that you can browse to from the server.

Step 3 Open the CSV file in a spreadsheet application or another application with which you can edit and

reorganize the data. Do the following:

• Confirm that the data is separated by commas, and that no tabs, spaces, or semicolons separate the

data in the file.

• If any data includes a space, quotes, or commas, contain it within quotes.

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

OL-13844-01

Chapter 4 Internet Subscribers

Step 4 Rearrange the data so that the columns are in the same order as the column headers that you will add in

Step 5. The order of the column headers does not matter, though it is a good practice to set up your CSV

file as indicated here.

For example, the columns of data in this sample are sorted so that the last name of the user is followed by the first name, and then by the remote address:

Note The example in this procedure illustrates how to set up a CSV file so that the Cisco Unity Bulk

Step 5 Enter the required column headers above the first row of data. Column headers must be in uppercase,

separated by commas, and spelled as indicated below:

Creating Internet Subscriber Accounts

Abade,Alex,aabade@cisco.com Bader,Kelly,kbader@cisco.com Campbell,Terry,tcampbell@cisco.com Cho,Li,lcho@cisco.com

Import wizard creates Internet subscriber accounts and new Active Directory contacts at the same time. If you choose to create new Internet subscriber accounts with data on existing Active Directory contacts, you must also include the ALIAS column header and data in your CSV file. Also note that to create Trusted Internet subscriber accounts, last name, first name, DTMF access ID, and remote address fields are required.

LAST_NAME,FIRST_NAME,REMOTE_ADDRESS

For Trusted Internet subscribers, the headers should be spelled as follows:

LAST_NAME,FIRST_NAME,DTMF_ACCESS_ID,REMOTE_ADDRESS

Step 6 If desired, add optional column headers to the first row, and the corresponding data that you want to

import in the subsequent rows below. As you do so, confirm that:

• Column headers and data are separated by commas. Note that every row does not have to contain

data for each optional column header.

• Any data that includes a space, quotes, or commas is contained within quotes.

Step 7 If your CSV file contains columns of data that you do not want to import, delete the columns.

Alternatively, you can title one column NOTES. The Cisco

Unity Bulk Import wizard ignores data beneath any NOTES column header, but the wizard does not support more than one NOTES column in a CSV file.

Step 8 Confirm that each row contains the applicable data corresponding to each column header.

Step 9 Save the file as a CSV file.

Step 10 Continue with the following “To Create Internet Subscriber Accounts by Using the Cisco Unity Bulk

Import Wizard” procedure.

To Create Internet Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard

Before you run the Cisco Unity Bulk Import wizard, disable virus-scanning services and intrusion-detection software on the Cisco Import wizard may run slowly. See the Cisco

Unity server, if applicable. Otherwise, the Cisco Unity Bulk

Unity Bulk Import wizard Help for procedures.

OL-13844-01

Step 1 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity

Bulk Import.

Step 2 Follow the on-screen instructions.

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

4-7

Creating Internet Subscriber Accounts

To learn more about the options presented in the dialog boxes that appear as the wizard proceeds, click Help.

Step 3 When prompted to choose the type of subscriber to create, click Internet or Trusted Internet, as

applicable.

Step 4 Click Next, and proceed through the wizard. If the wizard reports any errors, you can:

• Click OK to continue with the import, and fix the errors later.

• Fix the errors. See the “Correcting Import Errors” section on page 4-8 for details.

Step 5 When the Internet Subscriber accounts are created, click Finish.

Step 6 If you had import errors, but in Step 4 you chose to correct them later, see the “Correcting Import Errors”

section on page 4-8.

Step 7 If you had no import errors, or if all errors have now been corrected, see the “After Creating Internet

Subscriber Accounts” section on page 4-10.

Correcting Import Errors

Chapter 4 Internet Subscribers

The error log file contains data that the Cisco Unity Bulk Import wizard could not import. The Cisco

Unity Bulk Import wizard reports the first error it detects in any user mailbox or row in a CSV file. Once you correct that error, the wizard may detect additional errors in the same mailbox or row when the data is imported again. Thus, you may need to repeat the correction process—running the Cisco

Unity Bulk Import wizard and correcting an error—several times to find and correct all errors.

The output log file contains all the records that were not imported. You can save it as a CSV file, and use it when you run the Cisco

Unity Bulk Import wizard again. Note that each time you run the Cisco Unity Bulk Import wizard, the error and output log files are overwritten (unless you specify new names for the files).

To correct import errors, use one of the following procedures:

• To Correct Errors That Occurred When Importing Data from a CSV File, page 4-8

• To Correct Errors That Occurred When Importing Data from the Directory, page 4-9

To Correct Errors That Occurred When Importing Data from a CSV File

Step 1 Browse to the directory location of the error log file that you specified during the import. (The default

location and file name is C:\Error.log.)

Step 2 Use a text editor to open the error log file. You will use the error codes in the file to make corrections.

Step 3 Browse to the directory location of the output log file that you specified during the import. (The default

location and file name is C:\Output.log.)

Step 4 Use a text editor to open the output log file.

Step 5 Correct any records in the output file that are listed as errors in the error log file.

Step 6 When you have finished editing the output log file, save it as a CSV file with a new name.

4-8

Step 7 Run the Cisco Unity Bulk Import wizard again with the CSV file that you saved in Step 6.

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

OL-13844-01

Chapter 4 Internet Subscribers

Step 8 Repeat this procedure until all Internet subscriber accounts are created without error, and then proceed

to the

To Correct Errors That Occurred When Importing Data from the Directory

Step 1 Browse to the directory location of the error log file that you specified during the import. (The default

location and file name is C:\Error.log.)

Step 2 Use a text editor to open the error log file. You will use the error codes in the file to make corrections.

Step 3 Open Active Directory Users and Computers.

Step 4 Double-click a contact that contains an error to see the properties.

Step 5 Enter corrections in the applicable boxes in the contact.

Step 6 Click OK.

Step 7 Repeat Step 4 through Step 6 for each contact listed in the error log file.

Step 8 Run the Cisco Unity Bulk Import wizard again.

Step 9 Repeat this procedure until all Internet subscriber accounts are created without error, and then proceed

to the

Creating Internet Subscriber Accounts

“After Creating Internet Subscriber Accounts” section on page 4-10.

Using the Cisco Unity Administrator to Create Internet Subscriber Accounts

By using the Cisco Unity Administrator, you can create an Internet subscriber account by adding a new account, or by importing existing data for an Active Directory contact. When you add a new Internet subscriber account, Cisco

To create an Internet subscriber account, do one of the following procedures:

• To Create an Internet Subscriber Account by Adding a New Contact, page 4-9

• To Create an Internet Subscriber Account by Importing Existing User Data, page 4-10

To Create an Internet Subscriber Account by Adding a New Contact

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.

Step 2 Click the Add icon.

Step 3 Click New Subscriber, and then select Internet or Trusted Internet from the list.

Step 4 Enter the First Name and Last Name.

Step 5 Enter the Extension of the Internet subscriber on Cisco Unity. This is the number that other Cisco Unity

subscribers will use when addressing a message to the Internet subscriber that you are about to create.

Step 6 Select the Subscriber Template to use.

Step 7 Enter the SMTP Address in the applicable format.

Step 8 If you are creating a Trusted Internet subscriber, select a Trusted Internet location.

Step 9 Click Add.

Unity creates a contact in Active Directory.

OL-13844-01

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

4-9

Creating Internet Subscriber Accounts

Step 10 On the subscriber record, customize settings as applicable, and then click the Save icon.

To Create an Internet Subscriber Account by Importing Existing User Data

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.

Step 2 Click the Add icon.

Step 3 Select Import Existing Exchange User.

Step 4 Click Select.

Step 5 Select Internet.

Step 6 In the Find By list, indicate whether to search by first name, last name, or Exchange alias. You can also

indicate the domain for the search.

Step 7 Enter the applicable name or alias. You also can enter * to display a list of all users, or enter one or more

characters followed by * to narrow your search.

Step 8 Click Find.

Step 9 On the list of matches, click the name of the user to import.

Chapter 4 Internet Subscribers

Step 10 Enter the applicable information on the Add Subscriber page.

Step 11 Click Add.

Step 12 On the subscriber record, customize settings as applicable, and then click the Save icon.

Enabling Cross-Server Transfer for Internet Subscribers

By default, call transfers to Internet subscribers that are created on other Cisco Unity servers are always handled by the phone system (release to switch)—rather than by Cisco transfer)—even if the subscribers are set up for supervised transfers. Optionally, you can configure Cisco

Unity to use the cross-server transfer settings when transferring calls to Internet subscribers

homed on a different Cisco

Unity server. For more information about cross-server transfers, see the

“Cross-Server Transfer from the Automated Attendant and Directory Handlers” section on page 3-8. If

you already have cross-server transfer configured, see the “Optional: Enabling Cross-Server Transfer for

External Subscribers” section on page 3-10 for details on expanding the cross-server transfer

functionality to include Internet subscribers.

After Creating Internet Subscriber Accounts

After creating Internet subscriber accounts, consider the following:

• It takes a few minutes for a newly-created Internet subscriber account to be available to receive

messages.

Unity (supervised

4-10

• You can make changes to the settings for individual Internet subscriber accounts in the Cisco Unity

Administrator.

• When you want to modify settings for multiple subscribers at once, you can (re)run the Cisco Unity

Bulk Import wizard. To learn more, see the Cisco

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

Unity Bulk Import wizard Help.

OL-13844-01

Chapter 4 Internet Subscribers

Internet Subscriber Concepts and Definitions

• When a subscriber leaves the organization or otherwise no longer needs a Cisco Unity account, you

can delete the Internet subscriber account. See the

“Deleting Internet Subscribers” section on

page 4-12 for details.

Internet Subscriber Concepts and Definitions

Internet subscribers are a representation in Cisco Unity of users who do not have mailboxes on the local Exchange network. Instead, messages for Internet subscribers are sent to an e-mail address that you specify when you create the Internet subscriber account. The recipient receives voice messages as e-mails with attached WAV files.

Trusted Internet subscribers are Internet subscribers that are trusted with decrypted secure messages. Trusted Internet subscribers must be associated with a Trusted Internet Location. Based on the security settings of the Trusted Internet location, secure messages to Trusted Internet subscribers are decrypted by the Cisco (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)

Trusted Internet subscribers are the same as Internet subscribers except the following differences:

• Trusted Internet subscribers are associated with a Trusted Internet location.

Unity Voice Connector for Microsoft Exchange before they are sent by the Exchange server.

• Messages to Trusted Internet subscribers are processed by the Voice Connector.

• Trusted Internet subscribers must have a DTMF extension, whereas extensions are optional for

Internet subscribers.

The concepts discussed in this section apply to both regular Internet subscribers and Trusted Internet subscribers, except where specifically noted.

Internet subscribers are represented as mail-enabled contacts in Active Directory. You create and manage Internet subscriber accounts in much the same way that you do regular subscriber accounts. For example, a subscriber template is used when the Internet subscriber accounts are created, and you can adjust the call transfer settings for Internet subscriber accounts as needed.

Extensions are optional for Internet subscribers whereas they are mandatory for regular subscribers and Trusted Internet subscribers. If an Internet subscriber has not been assigned an extension, subscribers can address messages to that Internet subscriber only in spelled-name mode (if the Internet subscriber has a voice name). Subscribers can also address messages to Internet subscribers without extensions by using Cisco

Unity ViewMail for Microsoft Outlook or by using the Cisco Unity Inbox.

If you have specified extensions for the Internet subscribers, you can configure the call transfer settings for the Internet subscribers so that they can be reached by outside callers.

Internet subscribers do not require additional Exchange client access licenses (CALs), and they do not consume Cisco

Unity subscriber licenses. The Cisco Unity subscriber license count does not change

when you create Internet subscribers.

Other than receiving messages (and possibly calls), Internet subscribers do not have access to other Cisco

Unity features, and some sections of the Cisco Unity Administrator are disabled for Internet

subscribers. Internet subscribers:

OL-13844-01

• Cannot log on to Cisco Unity by phone to check or send messages.

• Cannot log on to Cisco Unity by phone—or use the Cisco Unity Assistant—to adjust personal

settings, so their recorded names and greetings can only be recorded or changed in the Cisco

Unity

Administrator.

• Cannot use Cisco Unity ViewMail for Microsoft Outlook or the Cisco Unity Inbox.

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

4-11

Internet Subscriber Concepts and Definitions

• Cannot own private lists.

• Cannot set up or receive message notifications.

• Cannot receive message waiting indications.

Subscriber Experience with Internet Subscribers

Provided that Internet subscribers have extensions, are listed in the phone directory, and have had voice names and greetings recorded for them:

• Subscribers can address messages to Internet subscribers by using the phone, ViewMail, or the

Cisco

Unity Inbox.

• Contacts that correspond to Internet subscribers are included in Exchange address lists, which

means that they are listed in the Outlook address book (unless the contact has been explicitly prevented from appearing there) and the Cisco addressing to Internet subscribers—either by using Outlook or the Cisco as for regular subscribers.

• When using the phone, subscribers can address messages to Internet subscribers by spelled-name

mode (if enabled on the system) or by extension or alternate extension.

• Subscribers get voice name confirmation when addressing a message to an Internet subscriber.

• Internet subscribers can be added to distribution lists.

Unity Inbox address book. Therefore, message

Chapter 4 Internet Subscribers

Unity Inbox—is the same

• You can configure call transfer settings for the Internet subscribers just as you can for Cisco Unity

subscribers so that unidentified callers and subscribers can call an Internet subscriber and leave a message.

Extensions are optional for Internet subscribers whereas they are mandatory for regular subscribers. If an Internet subscriber has not been assigned an extension:

• The Internet subscriber cannot be listed in the phone directory.

• Unidentified callers will be unable to leave messages for the Internet subscriber.

• When addressing messages to the Internet subscriber, subscribers are limited to spelled-name mode,

provided that the Internet subscriber has a recorded voice name. If neither an extension nor a voice name has been set, messages cannot be addressed to the Internet subscriber.

Deleting Internet Subscribers

Each Internet subscriber is associated with an Active Directory contact. When you delete Internet subscribers in the Cisco directory objects.

Unity Administrator, you are offered the option to delete the associated

4-12

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

OL-13844-01

AMIS Networking

Overview: AMIS

Cisco Unity supports the Audio Messaging Interchange Specification analog (AMIS-a) protocol, which provides a mechanism for transferring voice messages between different voice messaging systems.

AMIS Networking is a licensed feature. If your organization has multiple Cisco Unity servers networked together by using Cisco directory), only one server in the Digital Network needs to be licensed and configured for AMIS Networking. The Cisco bridgehead server. For more information about obtaining licenses for Cisco applicable Licensing for Cisco

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

To use AMIS Networking, you must choose the applicable options when you run the Cisco Unity Permissions wizard. For detailed information, see the Permissions wizard Help, which is available in Tools Depot on the Cisco

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

CHAP T ER

Unity Digital Networking (and, therefore, accessing subscriber data in the same

Unity server that is configured for AMIS Networking is referred to as the

Unity white paper, at

Unity server.

Unity features, see the

• Setting Up Cisco Unity to Use AMIS, page 5-1—This section describes the prerequisites and

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

• Procedures for Setting Up Cisco Unity to Use AMIS, page 5-4—This section contains all of the

step-by-step procedures necessary to set up Cisco Unity to use AMIS.

• AMIS Concepts and Definitions, page 5-25—This section explains AMIS concepts in detail. You

may want to read this section prior to doing the setup procedures.

• Maintenance, page 5-40—This section provides information about monitoring system activity.

• Troubleshooting, page 5-41—This section provides links to troubleshooting information.

• Notable Behavior, page 5-41—This section provides information about notable behavior related to

AMIS Networking.

Setting Up Cisco Unity to Use AMIS

See the following sections:

• Prerequisites, page 5-2

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

OL-13844-01

5-1

Setting Up Cisco Unity to Use AMIS

• Considerations for Deploying AMIS with Cisco Unified Communications Manager and Cisco

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

Prerequisites

Before starting the setup, verify that the following prerequisites have been met.

• Cisco Unity is already installed on the server(s), and they are connected to the network as applicable

• A license file with an AMIS license has been obtained and installed on the Cisco Unity bridgehead

• Cisco Unity meets the requirements as described in the “AMIS Networking Requirements” section

• The voice messaging system with which Cisco Unity will be networked meets the requirements

• Verify that the Cisco Unity call routing rules route calls to a call handler, such as the Opening

For installations with multiple Cisco Unity servers that access the same directory, you should first set up the servers for Digital Networking as described in the AMIS Networking. After the Cisco Unity servers have been set up for Digital Networking, verify the following settings:

Chapter 5 AMIS Networking

Gateways, page 5-3

to your installation.

server.

of the Networking Options Requirements for Cisco

Unity, at

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

listed in the “Support Policy for AMIS Voice Messaging Systems” section of the 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.

Greeting. (This is the default when Cisco

Unity is initially installed.)

“Digital Networking” chapter before setting up

• Verify that the addressing search scope is set to either the dialing domain or the global directory on

all of the networked servers so that Cisco

Unity subscribers, no matter which server they are associated with, can address messages to AMIS delivery locations and/or AMIS subscribers. See the

“Setting the Addressing Search Scope” section on page 2-6 for details.

• If you want outside callers to be able to reach AMIS subscribers from the automated attendant (for

example, from the opening greeting) or directory assistance:

–

Verify that the Cisco Unity server(s) on which the AMIS subscribers will be created are in the same dialing domain as the Cisco

Unity server that outside callers call into. See the

“Customizing the Primary Location” section on page 5-12 for details on creating the dialing

domain, and the “Dialing Domains” section on page 2-15 for background information.

–

Verify that the automated attendant and directory handler(s) search scopes are set to the dialing domain scope. See the

“Setting the Directory Handler Search Scope” section on page 2-7 and

the “Setting the Automated Attendant Search Scope” section on page 2-7.

5-2

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

OL-13844-01

Chapter 5 AMIS Networking

Setting Up Cisco Unity to Use AMIS

Considerations for Deploying AMIS with Cisco Unified Communications Manager and Cisco Gateways

In a Cisco Unified Communications Manager (CM) (formerly known as Cisco Unified CallManager) environment where AMIS calls may traverse one or more Cisco gateways or routers, we recommend that customers (or their systems integration partners) test the interoperability of such gateways with Cisco

Unity before the products are deployed. Consider the following when deploying AMIS:

• Call forwarding, call waiting or other tones can sometimes interfere with transmission of DTMF

sequences.

• Where applicable for Cisco Unified CM and gateways, set DTMF duration and interdigit timing to

100 milliseconds.

Task List: Setting Up Cisco Unity to Use AMIS

Use this task list to set up Cisco Unity to use AMIS. The cross-references take you to detailed procedures for the setup.

1. Install the Voice Connector on an Exchange server. See the “Setting Up the Voice Connector for

AMIS Networking” section on page 5-4.

Do the Following Tasks on Each Cisco Unity Server That Is Licensed for AMIS

2. During Cisco Unity installation, when you ran the Cisco Unity Permissions wizard to grant the

necessary permissions to the installation and service accounts, if you did not check the Set Permissions Required by AMIS, Cisco

Unity Bridge, and VPIM check box on the Choose Whether

to Enable Voice Messaging Interoperability page, do the following steps:

a. Log on to a Cisco Unity server that is licensed for AMIS by using an account that:

–

Is a member of the Domain Admins group in the domain that the Cisco Unity server belongs to, or that has permissions equivalent to the default permissions for the Domain Admins group.

–

Is either an Exchange Full Administrator or a member of the Domain Admins group in the domain that contains all of the domains from which you want to import Cisco

b. Re-run the Permissions wizard, and follow the on-screen prompts until the Choose Whether to

Unity subscribers.

Enable Voice Messaging Interoperability page appears.

c. Check the Set Permissions Required by AMIS, Cisco Unity Bridge, and VPIM check box.

d. Follow the on-screen prompts to complete the Permissions wizard.

e. If you have more than one Cisco Unity server that is licensed for AMIS, repeat Step a. through

Step d. on each server that is licensed for AMIS.

For more information on running the Permissions wizard, see the Permissions wizard Help, PWHelp_<language>.htm, in the directory where the Permissions wizard is installed.

If you do not know whether you checked the check box, run the Permissions wizard in report mode. For more information, see the Report Mode Help, PWReportHelp_<language>.htm, in the directory where the Permissions wizard is installed.

3. Create the UAmis account. See the “Creating the UAmis Account” section on page 5-8.

4. Designate voice ports for outbound AMIS calls. See the “Designating Voice Ports for Outbound

AMIS Calls” section on page 5-11.

OL-13844-01

5. Set the AMIS delivery options. See the “Setting AMIS Delivery Options” section on page 5-11.

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

5-3

Procedures for Setting Up Cisco Unity to Use AMIS

6. Customize the AMIS Restriction Table as needed. See the “Customizing the AMIS Restriction

Table” section on page 5-11.

7. Set up the AMIS schedule. See the “Setting Up the AMIS Schedule” section on page 5-12.

8. Customize the primary location profile settings. See the “Customizing the Primary Location”

section on page 5-12.

9. Create a delivery location for each remote voice messaging system. See the “Creating AMIS

Delivery Locations” section on page 5-13.

10. Optionally, create AMIS subscribers. See the “Creating AMIS Subscribers” section on page 5-16.

11. Optionally, extend identified subscriber messaging to include AMIS subscribers. See the “Extending

Identified Subscriber Messaging to Include AMIS Subscribers” section on page 5-22.

12. Optionally, enable cross-server transfers for AMIS subscribers. See the “Enabling Cross-Server

Transfer for AMIS Subscribers” section on page 5-24.

Finish the Setup

13. Set up the other voice messaging system for AMIS. The other voice messaging system will require

the number to dial into Cisco

14. Test the setup to verify that Cisco Unity can exchange messages with the other voice messaging

system. Optionally, you can configure the macro trace “Basic Incoming and Outgoing AMIS Message” in the Unity Diagnostic tool (on the Windows Start menu, click Programs > Cisco Unity Diagnostic Tool) to verify that Cisco

Chapter 5 AMIS Networking

Unity, and the Node ID that was entered on the primary location.

Unity >

Unity can send and receive AMIS messages.

Procedures for Setting Up Cisco Unity to Use AMIS

This section contains all of the procedures necessary to set up Cisco Unity to use AMIS. Consult the

“Task List: Setting Up Cisco Unity to Use AMIS” section on page 5-3 for information on the order in

which the procedures must be completed.

Setting Up the Voice Connector for AMIS Networking

The Voice Connector installation program is included on Cisco Unity DVD 1 and CD 1. Voice Connector for Exchange 2000 version 11.0(1) or later can be installed on either an Exchange 2000 or an Exchange

The Voice Connector installation program does not prompt with a choice of languages for the installation; it always installs in English. To run the Voice Connector installation program by using one of the localized versions (FRA, DEU, or JPN) instead of English, see the

Setup Program in Another Language” section on page 5-42.

Setting Up the Voice Connector for Exchange 2000

Install the Voice Connector on any Exchange 2000 or Exchange 2003 server that is not part of an Exchange cluster (Microsoft does not support third-party connectors on an Exchange cluster server). Although the Voice Connector can be installed on the Cisco server), this is not recommended for performance reasons.

2003 server.

“Running the Voice Connector

Unity server (when Exchange is also on the

5-4

Caution Installing the Voice Connector on an Exchange 2007 server is not supported.

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

OL-13844-01

Chapter 5 AMIS Networking

If the Exchange server on which the Voice Connector will be installed is in a different routing group than the Exchange servers on which Cisco configured between the routing groups.

The Voice Connector service is automatically configured to log on as the account that is associated with the Exchange server on which the Voice Connector is installed (sometimes referred to as the “Local System” account). The account that the service logs on as should not be changed.

Caution Do not change the default permissions for the Local System account. In addition, do not change the

permissions granted to Exchange administrative groups during Exchange installation. The Voice Connector logs on using that account, and if you change permissions, the Voice Connector may not function properly.

The following procedures are for installing Voice Connector version 12.0(1), which ships with Cisco that you install that version instead. Follow the installation instructions in the release notes for the applicable version. To check for a later version, go to the Cisco Software Download page at

Procedures for Setting Up Cisco Unity to Use AMIS

Unity subscribers are homed, routing group connectors must be

Unity 5.0(1). We recommend that you first check for a later version of the Voice Connector, and

Unity Voice Connector for Exchange

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

To Install the Voice Connector for Exchange 2000

As a best practice, back up the Exchange server before installing the Voice Connector.

Step 1 Uninstall any previous versions of the Voice Connector. See the “Uninstalling the Cisco Unity Voice

Connector” section on page 10-4.

Step 2 Log on to the Exchange server on which you are installing the Voice Connector.

Step 3 Disable any virus-scanning services on the Exchange server.

Step 4 If Cisco Unity is also on the server on which you are installing the Voice Connector, disable the Cisco

Security Agent service, if applicable.

Step 5 If you are installing the Voice Connector from a Cisco Unity DVD 1, insert the disc in the computer, and

browse to the VoiceConnector-Ex2000 directory.

If you downloaded the Voice Connector files from the Software Center website, browse to the directory in which the files were extracted.

Step 6 Double-click Install.exe, and click Next.

Step 7 On the Voice Connector Setup Wizard Select Components dialog box, check the Voice Connector for

Exchange check box.

Step 8 If you are setting up secure messaging and if Cisco Unity is not on the Exchange server, check the Cisco

Secure Messaging Service check box.

Step 9 Click Next.

Step 10 On the Welcome screen, click Next.

Step 11 On the Confirm SMTP Pickup Directory screen, click Next.

OL-13844-01

Step 12 In the Address Types dialog, check the AMIS check box.

Step 13 If you are setting up the system to use other networking options, check the check boxes of the applicable

address types.

Note Setting up VPIM Networking also requires the installation of the Transport Event Sink.

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

5-5

Procedures for Setting Up Cisco Unity to Use AMIS

Step 14 Click Next.

Step 15 On the Confirm Directory dialog box, click Next to launch the setup.

Step 16 If you did not check the Cisco Secure Messaging Service check box in Step 7, skip to Step 17.

Otherwise, do the following sub-steps in the Cisco Unity Secure Messaging Service Setup wizard:

a. On the Welcome screen, click Next.

b. On the Choose Destination Folder dialog, specify the destination, and click Next.

c. Optionally, on the Message Security Settings screen, check the Enable Message Aging check box,

and enter the number of days that encrypted messages should be available. (If the check box is not checked, Cisco

d. Click Next.

e. On the Ready to Install Software screen, click Install.

Step 17 When the setup is complete, click Finish to exit Setup and restart the server.

Step 18 Enable virus-scanning and the Cisco Security Agent services, if applicable.

Unity will not limit the number of days that encrypted messages will be available.)

In order to view Voice Connector properties in Exchange System Manager, Microsoft Windows Script Host version 5.6 or later must be installed on the Exchange server. Continue with the following

Determine if the Microsoft Windows Script Host Should Be Updated” procedure. (Also note that if the

Exchange server uses an earlier version of Windows Script Host, the Voice Connector will function properly, but you will not be able to view Voice Connector properties in the Exchange System Manager.)

Chapter 5 AMIS Networking

“To

To Determine if the Microsoft Windows Script Host Should Be Updated

Step 1 On the Exchange server on which the Voice Connector has been installed, browse to Winnt\System32.

Step 2 Right-click the file Wshom.ocx, and click Properties.

Step 3 Click the Ve rs io n tab.

Step 4 In the Item Name list, click Product Version to view the version in the Value box.

If the version is earlier than 5.6, update Windows Script Host so the Voice Connector properties can be displayed in Exchange System Manager. (Go to the downloads page of the Microsoft website, and do a keyword search for Windows Script Host. Follow the installation instructions.)

To Verify the Voice Connector for Exchange 2000 Installation

To verify that the Voice Connector for Exchange 2000 installed properly, verify that the Voice Connector service is running, and that the Voice Connector mailbox has been created.

Step 1 Open the Services applet on the Exchange server on which the Voice Connector is installed. (On the

Windows Start menu, click Programs > Administrative Tools > Services.)

Step 2 Verify that the Status for the Exchange 2000 Voice Connector (<Server name>) service is Started, and

that the Startup Type is set to Automatic.

Step 3 Exit the Services applet.

5-6

Step 4 Open Exchange System Manager on the Exchange server on which the Voice Connector is installed. (On

the Windows Start menu, click Programs > Microsoft Exchange > Exchange System Manager.)

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

OL-13844-01

Chapter 5 AMIS Networking

Procedures for Setting Up Cisco Unity to Use AMIS

Step 5 In the tree in the left pane, expand the Servers container. If the organization properties at the top of the

tree have been set such that administrative groups are displayed in the tree, the Servers container is nested within the administrative group container.

Step 6 Within the Servers container, expand the <Server name>\<Storage group>\Mailbox Store (<Server

name>) container for the server on which the Voice Connector is installed.

Step 7 In the expanded tree, click Mailboxes.

In the right pane, you should see the mailbox for “Exchange 2000 Voice Connector (<Server name>)” or “AvExchangeIVC_<Server name>.” (The name changes from “AvExchangeIVC_<Server name>” to “Exchange 2000 Voice Connector (<Server name>)” after you run Cleanup Agent.)

Step 8 Exit Exchange System Manager.

Controlling What Happens to Messages That Cannot Be Delivered

When the Voice Connector encounters a message that cannot be delivered, and the sender information is incomplete or incorrect such that a nondelivery receipt (NDR) cannot be sent to the message sender, the Voice Connector saves the message in the Archive folder in the Voice Connector mailbox. The Archive folder is accessible only when using tools available from Microsoft. If you want more control over archived messages, you can add to the registry either the AliasToForwardBadMailsTo value or the DeleteArchiveFolderMessages value (but not both).

When you add the AliasToForwardBadMailsTo registry value and set it to the SMTP address of a user or distribution list, when the Voice Connector encounters a problematic message, information about the message is sent to the specified address instead of being saved in the Archive folder. When a problematic AMIS message is encountered, the informational message that the Voice Connector sends to the specified user (or distribution list) includes the MIME header of the problematic message as a text attachment. The MIME header contains the “To” and “From” addresses, which may help in troubleshooting the problem.

When you add the DeleteArchiveFolderMessages registry value and set it to 1, the Voice Connector continues to save problematic messages in the Archive folder, but periodically, the Voice Connector automatically deletes the messages in the Archive folder.

When a message is saved to the Archive folder or sent to the address specified in the AliasToForwardBadMailsTo registry value, an entry is made in the Voice Connector log file. (The information is logged when the Voice Connector properties are set to the default logging level or a higher logging level.) The Voice Connector logs are located on the Exchange server on which the Voice Connector is installed in the directory <ExchangeServerPath>\VoiceGateway\LogFiles. The files are named in the format GwIvc_<YyMmDd >.log, where Yy in the year, Mm is the month, and Dd is the day.

To add the registry values, do the following procedure.

To Control What Happens to Messages That Cannot Be Delivered

Step 1 On the Exchange server on which the Voice Connector is installed, start Regedit.

Caution Changing the wrong registry key or entering an incorrect value can cause the server to

malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (See the “Restoring” topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC .

OL-13844-01

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

5-7

Procedures for Setting Up Cisco Unity to Use AMIS

Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the

registry settings to a file.

Step 3 Expand the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvIvc

Step 4 If you want information about the messages to be sent to a user or distribution list instead of being saved

to the Archive folder, do the following sub-steps. Otherwise, skip to

a. On the Edit menu, click New > String Value.

b. Enter AliasToForwardBadMailsTo as the value name.

c. Double-click AliasToForwardBadMailsTo.

d. In the Edit String dialog box, enter the SMTP address of the recipient (for example

unityadministrator@company.com). This must be the SMTP address of a user, contact, or distribution list object in Exchange. An e-mail with the failed message and information about the message will be sent to this address.

e. Click OK.

f. Exit Regedit.

g. Skip to Step 6.

Chapter 5 AMIS Networking

Step 5.

Step 5 If you want messages that are saved in the Archive folder to be automatically deleted, do the following

sub-steps:

a. On the Edit menu, click New > DWORD Val ue .

b. Enter DeleteArchiveFolderMessages as the value name.

c. Double-click DeleteArchiveFolderMessages.

d. In the Edit DWORD dialog box, enter 1.

e. Click OK.

f. Exit Regedit

Step 6 Open the Services MMC on the Exchange server on which the Voice Connector is installed. (On the

Windows Start menu, click Programs > Administrative Tools > Services.)

Step 7 Right-click Exchange 2000 Voice Connector (<Server name>), and click Restart.

Step 8 Exit the Services MMC.

Creating the UAmis Account

In installations with multiple Cisco Unity servers networked together via Digital Networking, ConfigMgr.exe, the utility that creates the UAmis account, needs to be run only on the Cisco server(s) licensed for AMIS.

Unity

5-8

Do one of the following two procedures, depending on whether the partner Exchange server is running Exchange 2000/2003 or Exchange 2007:

• To Create the UAmis Account When the Partner Exchange Server Is Running Exchange 2000 or

Exchange 2003, page 5-9

• To Create the UAmis Account When the Partner Exchange Server Is Running Exchange 2007, page

5-9

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

OL-13844-01

Chapter 5 AMIS Networking

To Create the UAmis Account When the Partner Exchange Server Is Running Exchange 2000 or Exchange 2003

Step 1 On the Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location

is C:\CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create and Configure AMIS Account and Mailbox.

Step 4 Click OK on the dialog box that displays when the UAmis account is successfully configured.

Step 5 Click Exit to close ConfigMgr.

Step 6 On the Cisco Unity server, start the Services tool. (On the Windows Start menu, click Programs >

Administrative Tools > Services.)

Step 7 Right-click AvNotifierMgr, and select Restart. The CPU usage on the Cisco Unity server will spike for

a few minutes while the AvNotifierMgr reinitializes connections with subscriber mailboxes.

Step 8 Close the Services tool.

To Create the UAmis Account When the Partner Exchange Server Is Running Exchange 2007

Procedures for Setting Up Cisco Unity to Use AMIS

Step 1 On the Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location

is C:\CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create and Configure AMIS Account and Mailbox.

Step 4 In the Create the PowerShell Script That Creates the UAmis Account and Mailbox dialog box, choose

the path and file name for the script that will create the UAmis account.

You must run the script on the partner server or another server on which Exchange Management Shell is installed, so choose one of the following locations to save the script:

• The server that you will run the script on.

• A network location that is accessible to that server.

• A removeable disk.

Step 5 Click Create Script.

Step 6 Click OK.

Step 7 Click Exit to close ConfigMgr.

Step 8 Log on to the Exchange 2007 server on which you want to run the script by using an account that has the

right to run a PowerShell script.

Step 9 If necessary, copy the script locally to the Exchange server.

Step 10 Run Exchange Management Shell. (From the Start menu, click All Program > Microsoft Exchange

Server 2007 > Exchange Management Shell.)

OL-13844-01

Step 11 Run the script. In the Exchange Management Shell window, enter the full pathname of script. For

example:

d:\scripts\UAmis_<ServerName>.PS1

Alternatively, you can change to the directory where the script is located by using the “cd” command, and then run the script by entering:

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

5-9

Procedures for Setting Up Cisco Unity to Use AMIS

.\UAmis_<ServerName>.PS1

For more information, refer to Microsoft documentation.

Step 12 On the Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location

is C:\CommServer).

Step 13 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 14 Click Create and Configure AMIS Account and Mailbox to complete the configuration.

Step 15 Click OK.

Step 16 Click Exit to close ConfigMgr.

Step 17 On the Cisco Unity server, start the Services tool. (On the Windows Start menu, click Programs >

Administrative Tools > Services.)

Step 18 Right-click AvNotifierMgr, and select Restart. The CPU usage on the Cisco Unity server will spike for

a few minutes while the AvNotifierMgr reinitializes connections with subscriber mailboxes.

Step 19 Close the Services tool.

Chapter 5 AMIS Networking

To Verify That the UAmis Account Was Created When the Partner Exchange Server Is Running Exchange 2000 or Exchange 2003

If the partner Exchange server is running Exchange 2007, do the “To Verify That the UAmis Account

Was Created When the Partner Exchange Server Is Running Exchange 2007” procedure on page 5-10.

The mailbox for the UAmis account is located on the partner Exchange server, which is the Exchange server that was selected in the Message Store Configuration wizard during Cisco

Step 1 Open Exchange System Manager on the partner Exchange server.

Step 2 In the tree control in the left pane, expand the Servers > <ExchangeServerName> container (where

Unity setup.

<ExchangeServerName> is the name of the partner Exchange server).

Depending on your installation, the Servers container may be nested within an administrative group and a site container.

Step 3 Expand <Storage Group> > Mailbox Store (<ExchangeServerName>) > Mailboxes.

Step 4 Ve ri fy t ha t UAmis_<ServerName> is in the list of mailboxes in the right pane.

Step 5 Close Exchange System Manager.

To Verify That the UAmis Account Was Created When the Partner Exchange Server Is Running Exchange 2007

Step 1 Open Exchange Management Console on the partner Exchange server.

5-10

Step 2 In the tree control in the left pane, expand Recipient Configuration, and click Mailbox.

Step 3 Ve ri fy t ha t UAmis_<ServerName> is in the list of mailboxes in the right pane.

Step 4 Close Exchange Management Console.

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

OL-13844-01

Chapter 5 AMIS Networking

Designating Voice Ports for Outbound AMIS Calls

In installations with multiple Cisco Unity servers networked together via Digital Networking, designate voice ports for AMIS calls only on those Cisco

Usage and Schedules” section on page 5-26 for guidelines on configuring the ports.

To Designate Voice Ports for Outbound AMIS Calls

Step 1 In the Cisco Unity Administrator, go to the Systems > Ports page.

Step 2 Designate which ports to use for outgoing AMIS calls.

Step 3 Click the Save icon.

Unity server(s) that are licensed for AMIS. See the “Port

Setting AMIS Delivery Options

The AMIS delivery option settings control attributes of outgoing AMIS calls on the Cisco Unity server.

In installations with multiple Cisco Unity servers networked together, set the AMIS delivery options only on those Cisco

Unity server(s) that are licensed for AMIS.

Procedures for Setting Up Cisco Unity to Use AMIS

To Set AMIS Delivery Options

Step 1 In the Cisco Unity Administrator, go to the Network > AMIS Options > Delivery Options page.

Step 2 Select either the Default AMIS restriction table or another restriction table to use as the Local Dial

Restriction Table.

The Local Dial Restriction Table and the AMIS schedule together determine when outgoing AMIS calls are made.

Step 3 Set the other AMIS delivery options as needed.

Step 4 Click the Save icon.

Customizing the AMIS Restriction Table

By default, the AMIS restriction table allows all delivery numbers; however, you can customize the restriction table as needed. The AMIS restriction table and the AMIS schedule together determine when outgoing AMIS calls are made. If a delivery number for an outgoing AMIS message is allowed by the AMIS restriction table, the message is sent immediately—the schedule settings do not apply. If the delivery number is not allowed by the AMIS restriction table, the schedule determines when the message is sent.

In installations with multiple Cisco Unity servers networked together, customize the AMIS restriction table only on those Cisco

Unity server(s) that are licensed for AMIS.

OL-13844-01

To Customize the AMIS Restriction Table

Step 1 In the Cisco Unity Administrator, go to any Call Management > Restriction Tables page.

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

5-11

Procedures for Setting Up Cisco Unity to Use AMIS

Step 2 Click the Find icon.

Step 3 Double-click the AMIS restriction, which by default is named {Default AMIS}.

Note The AMIS restriction table is specified on the Network > AMIS Options > Delivery Options

page in the Local Dial Restriction Table field.

Step 4 As applicable for your installation, do one or more of the following:

• To add a dial string, click Add Dial String and enter settings for the new dial string as applicable.

• To delete a dial string, click the dial string number in the table in the bottom portion of the

Restriction Tables page, and then click Remove Dial String.

• To modify a dial string, click the dial string number in the table in the bottom portion of the

Restriction Tables page, and change settings as applicable.

Step 5 Click the Save icon.

Chapter 5 AMIS Networking

Setting Up the AMIS Schedule

Set up the AMIS schedule for messages that are not allowed by the AMIS restriction table.

In installations with multiple Cisco Unity servers networked together, set up the AMIS schedule only on those Cisco

To Set Up the AMIS Schedule

Step 1 In the Cisco Unity Administrator, go to the Network > AMIS Options > Schedule page.

Step 2 Click boxes on the schedule grid to set the active and inactive half hours. To avoid clicking the same

Unity server(s) that are licensed for AMIS.

blocks for more than one day, use the Copy Day’s Schedule box to copy the settings from one day to other days.

Step 3 Click the Save icon.

Customizing the Primary Location

If your installation consists of multiple Cisco Unity servers networked via Digital Networking, you may have already customized the primary location. In installations with multiple Cisco networked via Digital Networking, you enter the AMIS node ID for the primary location only on the Cisco

Unity Bridgehead server (the field is displayed only on the Cisco Unity servers licensed for

AMIS.)

For detailed information about the settings, see the “Primary Location Profile Settings” section on

page 9-1.

Unity servers

5-12

To Customize the Primary Location

Step 1 In the Cisco Unity Administrator, go to the Network > Primary Location > Profile page.

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

OL-13844-01

Chapter 5 AMIS Networking

Step 2 Enter a meaningful name for the location.

Step 3 Enter a Dial ID. The Dial ID identifies this location to Cisco Unity.

Step 4 Record a voice name for the location.

Step 5 For the Dialing Domain name:

• If your installation consists of only one Cisco Unity server, and if you plan to enable identified

• If your installation consists of multiple Cisco Unity servers that are networked via Digital

Step 6 Enter the numbers for the Node ID, which is transmitted by Cisco Unity to identify itself to other voice

messaging systems during outgoing AMIS calls. The Country Code and Area Code fields can be left blank; however, the Phone Number field is mandatory.

Procedures for Setting Up Cisco Unity to Use AMIS

subscriber messaging to include AMIS subscribers, enter a dialing domain name.

Networking, and if this server is integrated with the same phone system as other networked Cisco

Unity servers, you may have already added this server to a dialing domain. If not, enter the dialing domain name, or select it from the available list. The list contains dialing domain names that are already configured on at least one other Cisco

Unity server in the network.

Unity servers. By doing so, you also confirm that replication is working correctly among the servers. The time that it takes for the primary location data from other Cisco

Unity server and wait for the name to replicate to the other

Unity servers to be

reflected on the local server depends on your network configuration and replication schedule.

Step 7 Click the Save icon.

Creating AMIS Delivery Locations

Create an AMIS delivery location on the bridgehead Cisco Unity server for each remote voice messaging system to which subscribers will send messages. If Cisco of voice messaging systems, you may prefer to configure only a few delivery locations at this time and proceed with the rest of the setup. After verifying that messaging works correctly between Cisco and the voice messaging systems for which delivery locations have been configured, you can create the rest of the delivery locations.

Carefully consider the Dial ID that you will assign to the delivery location. See the “Guidelines for

Assigning Dial IDs and Extensions” section on page 9-2 for detailed information about choosing a Dial

ID.

You can create AMIS delivery locations by using the Cisco Unity Administrator or the Cisco Unity Bulk Location Import wizard. See the following sections:

• Using the Cisco Unity Administrator to Create AMIS Delivery Locations, page 5-13

• Using the Cisco Unity Bulk Import Wizard to Create AMIS Delivery Locations, page 5-14

• Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard, page 5-16

Unity will be messaging with a large number

Unity

Using the Cisco Unity Administrator to Create AMIS Delivery Locations

You can create AMIS delivery locations one at a time by using the Cisco Unity Administrator.

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

OL-13844-01

5-13

Procedures for Setting Up Cisco Unity to Use AMIS

To Create AMIS Delivery Locations by Using the Cisco Unity Administrator

Step 1 In the Cisco Unity Administrator, go to the Network > Delivery Locations > Profile page.

Step 2 Click the Add icon.

Step 3 Enter a meaningful name for the location.

Step 4 Enter the Dial ID. See the “Guidelines for Assigning Dial IDs and Extensions” section on page 9-2 for

detailed information about choosing a Dial ID.

Step 5 Select AMIS as the Destination Type for the location.

Step 6 Click Add.

Step 7 Record a voice name for the location.

Step 8 Enter the Delivery Phone Number. This is the number that Cisco Unity dials to connect to the remote

voice messaging system for outgoing AMIS messages.

Step 9 Enter the numbers for the Node ID, which is used to identify the remote voice messaging system that

corresponds to this delivery location. This Node ID must match the Node ID that the corresponding remote voice messaging system transmits during incoming calls. If desired, the Country Code and Area Code fields may be left blank; however, the Phone Number field is mandatory.

Chapter 5 AMIS Networking

Step 10 In the Outgoing Messages to This Location field, select the applicable option:

• Do Not Decrypt Messages—The Voice Connector will not decrypt or send secure messages and

will send an NDR back to the sender.

• Decrypt Non-Private Messages—The Voice Connector will not decrypt or send secure messages

that are flagged as private. An NDR will be sent back to the sender. All other messages will be decrypted before sending them to the remote location.

• Decrypt All Messages—The Voice Connector will decrypt all secure messages before sending them

to the remote location. Depending on the configuration at the remote location, the message may or may not be re-encrypted before being delivered to the recipient.

Step 11 Click the Save icon.

Using the Cisco Unity Bulk Import Wizard to Create AMIS Delivery Locations

The Cisco Unity Bulk Import wizard allows you to create or modify multiple delivery locations at once by importing data in a CSV file. If you have already created delivery locations, you can run Cisco Bulk Import to export the data about the delivery locations to a CSV file.

Use the following procedure to prepare your CSV file. To learn more about preparing a CSV file for use with the Cisco headers for your CSV file—see the Cisco

Unity Bulk Import wizard—including information on the required and optional column

Unity Bulk Import wizard Help.

Unity

5-14

To Prepare a CSV File for Creating AMIS Delivery Locations

Step 1 Create a CSV file in a spreadsheet application (or another applicable application) on the Cisco Unity

server, or in a directory that you can browse to from the server.

Step 2 Enter the required column headers in the first row. Column headers must be in uppercase, separated by

commas, and spelled as indicated below:

DTMF_ACCESS_ID, DISPLAY_NAME, DELIVERY_PHONE_NUMBER

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

OL-13844-01

Chapter 5 AMIS Networking

Step 3 If desired, add optional column headers to the first row. Be sure to separate the column headers with

commas.

Although the Cisco Unity Bulk Import wizard does not require that you provide the AMIS_NODE_ID column in the CSV file, we recommend that you add the column with the Node ID data to the CSV file.

Step 4 Add the data for the delivery locations in the subsequent rows. When finished:

• Confirm that every row contains the applicable data corresponding to each column header.

• Confirm that the data is separated by commas, and that no tabs, spaces, or semicolons separate the

• If any data includes a space, quotes, or commas, contain it within quotes.

Note Every row does not have to contain data in the optional columns.

Step 5 Save the file as a CSV file.

Step 6 Continue with the following “To Create AMIS Delivery Locations by Using the Cisco Unity Bulk Import

Wizard” procedure.

Procedures for Setting Up Cisco Unity to Use AMIS

data in the file.

To Create AMIS Delivery Locations by Using the Cisco Unity Bulk Import Wizard

Step 1 Before you run the Cisco Unity Bulk Import wizard, disable virus-scanning services and

intrusion-detection software on the Cisco

Unity server, if applicable. Otherwise, the Cisco Unity Bulk

Import wizard may run slowly.

Step 2 On the Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity > Cisco Unity

Bulk Import.

Step 3 On the Welcome page, click Next.

Step 4 On the Select Import Operation, in the Locations section, click CSV File, and then click Next.

Step 5 On the Select Location Operation page, click Create New Locations, and then click Next.

Step 6 On the Type of Locations page, click AMIS, and then click Next.

Step 7 On the Files page, specify the name and location of the input file.

Step 8 Specify the name and location of the output file, or use the default location and file name, which is based

on the input file. For example, if the input file is C:\Temp\AMIS_Locations.csv, the default output file will be C:\Temp\AMIS_Locations.out.csv.

Step 9 Click Next to proceed to the Valid Location Data page, which displays a table with validated rows of

data from the input CSV file. If you do not want to import a row of data, uncheck the check box in the first column of the row.

If errors were found in any of the rows, you can click the Errors link at the bottom of the page to open the output CSV file to correct the errors, or you can ignore the errors for now and proceed with the import.

Step 10 Click Next to start the import process and display the Creating Locations page, which provides status

information about the import.

Step 11 When the delivery locations are created, click Next to display the Cisco Unity Bulk Import Wizard

Finished page, which displays summary information.

OL-13844-01

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

5-15

Procedures for Setting Up Cisco Unity to Use AMIS

Step 12 If you had import errors, continue with the following “To Correct Errors That Occurred When Importing

Delivery Location Data from a CSV File” procedure.

To Correct Errors That Occurred When Importing Delivery Location Data from a CSV File

Step 1 Browse to the directory location of the output file that you specified during the import. (The default

location and file name is based on the input file. For example, if the input file is C:\Temp\AMIS_Locations.csv, the default output file will be C:\Temp\AMIS_Locations.out.csv.)

This file contains all of the records that were not imported.

Step 2 Use a text editor to open the output file.

Step 3 Correct any records in the output file by using the error information listed in the Results column of the

file.

Step 4 When you have finished editing the output file, save it as a CSV file with a new name.

Step 5 Run the Cisco Unity Bulk Import wizard again with the new CSV file.

Step 6 Repeat this procedure until all delivery locations are created without error.

Chapter 5 AMIS Networking

Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

If you want to use the Cisco Unity Bulk Import wizard to make modifications to existing delivery locations, you will need to create a CSV file for the modifications. We recommend that you run the Cisco

Unity Bulk Import wizard to export your existing delivery location data to a CSV file, and then

edit the CSV file to use for the modification.

Note that the DTMF_ACCESS_ID column is used as the primary key to find the existing delivery location, and therefore it cannot be modified by the Cisco

Unity Bulk Import wizard.

Creating AMIS Subscribers

You may prefer to begin by creating only a few AMIS subscribers for testing purposes, until you verify that Cisco that messaging between Cisco the AMIS subscribers. Note that the AMIS subscribers must be created on the same Cisco as the AMIS delivery locations.

You can create AMIS subscriber accounts by using the Cisco Unity Bulk Import wizard or the Cisco

• Before Creating AMIS Subscriber Accounts, page 5-17

• Using the Cisco Unity Bulk Import Wizard to Create Multiple AMIS Subscriber Accounts, page

• Using the Cisco Unity Administrator to Create AMIS Subscriber Accounts, page 5-21

Unity and the remote system can successfully exchange messages. After you have confirmed

Unity and the remote system is working correctly, you can finish creating

Unity Administrator. See the following sections:

5-18

Unity server

5-16

• After Creating AMIS Subscriber Accounts, page 5-22

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

OL-13844-01

Chapter 5 AMIS Networking

Before Creating AMIS Subscriber Accounts

This section lists—in order—the issues that you must consider before creating AMIS subscriber accounts. AMIS subscribers can be created only on a Cisco tasks on the Cisco

1. Cisco Unity Configuration and Permissions

If you are unsure whether the account that you are using has sufficient rights and permissions to create AMIS subscribers, or whether Cisco the following procedure.

To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool

Step 1 On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane of the Tools Depot window, in the Diagnostic Tools directory, double-click SysCheck.

Step 3 On the Welcome to the Cisco Unity Configuration Wizard page, click Select Configuration Tests, and

click Next.

Step 4 Uncheck the check boxes for the message stores that are not connected to Cisco Unity.

Unity Bridgehead server where you will be adding the AMIS subscribers.

“To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool”

Procedures for Setting Up Cisco Unity to Use AMIS

Unity Bridgehead server. Do the following

Unity is properly configured to work with your message store, do

Step 5 Click Te st.

Step 6 In the Test Results box, click the link provided to view the test results.

Step 7 If no errors are reported, proceed to Step 8. Otherwise, do the following sub-steps:

a. Follow the advice offered in the Resolution column to correct each configuration or permissions

error.

b. Return to the Completing the Check Unity Configuration Wizard page, and click Finish.

c. Repeat Step 2 through Step 7 until no errors are reported.

Step 8 Click Finish.

2. Classes of Service

A class of service (COS) defines limits and permissions for subscribers who use Cisco Unity. For example, a COS dictates the maximum length of subscriber messages and greetings. Although most COS settings are not applicable to AMIS subscribers, they still must be members of a COS. In the Cisco Administrator, a COS is specified in each subscriber template; thus, a subscriber is assigned to the COS that is specified in the template upon which the subscriber account is based. Cisco predefined classes of service that you can modify. You can also create new classes of service. For details, see the “Managing Classes of Service” chapter in the System Administration Guide for Cisco

3. Restriction Tables

Each COS specifies a restriction table for call transfers, one for message notification, and one for fax deliveries. Cisco an error message if the phone number is not allowed. Cisco

Unity applies the restriction table associated with the COS of a subscriber, and displays

Unity comes with predefined restriction

tables that you can modify.

Unity

Unity includes

Unity.

OL-13844-01

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

5-17

Procedures for Setting Up Cisco Unity to Use AMIS

Although most restriction table settings do not apply to AMIS subscribers because they cannot log on to Cisco

Unity or use the Cisco Personal Communications Assistant (PCA), administrators can enter call transfer numbers for AMIS subscribers. For security purposes, you should modify the restriction table used for transfers in the COS to which AMIS subscribers belong, as necessary. For details, see the “Managing Restriction Tables” chapter in the System Administration Guide for Cisco

4. Public Distribution Lists

Public distribution lists are used to send voice messages to multiple subscribers at the same time. Cisco

Unity assigns new subscribers to the public distribution lists that are specified in the template on which the subscriber account is based. For details, see the “Managing Distribution Lists” chapter in the

System Administration Guide for Cisco

Public distribution lists correspond to distribution groups in Active Directory. The distribution lists are listed in the address book for Microsoft Outlook (or other e-mail client), unless they are explicitly hidden. To help prevent others from sending e-mail to AMIS subscribers, you may want to create lists that contain only AMIS subscribers, and then hide these distribution lists from the Outlook address book. The option to hide distribution lists is available on the Subscribers > Public Distribution Lists > Profile page in the Cisco

5. Subscriber Templates

Unity Administrator.

In the Cisco Unity Administrator, you can specify settings for a group of subscribers by using a subscriber template. Subscriber templates contain settings that are applicable for subscribers of a particular type, such as a department. The settings from the template you choose are applied to subscriber accounts as the accounts are created. Cisco that you can modify, and you can create an unlimited number of additional templates. For more details, see the “Managing Subscriber Templates” chapter in the System Administration Guide for Cisco

AMIS subscribers correspond to contacts in Active Directory. The contacts are listed in the address book for Microsoft Outlook (or other e-mail client), unless they are explicitly hidden. You may prefer that the associated contacts do not appear in the Outlook address book at all, or you may want to alter how contacts appear in the Outlook address book. See the

the Outlook Address Book” section on page 5-34 for details.

Chapter 5 AMIS Networking

Unity.

Unity comes with a default subscriber template

Unity.

“Determining How AMIS Subscribers Appear in

Note The System Administration Guide for Cisco Unity is available at

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

Using the Cisco Unity Bulk Import Wizard to Create Multiple AMIS Subscriber Accounts

The Cisco Unity Bulk Import wizard allows you to create multiple subscriber accounts at once by importing user data from a comma-separated value (CSV) file. CSV is a common text file format for moving data from one data store to another.

As long as the user data contained in the CSV file is formatted correctly, you can use it to create new contacts in Active Directory at the same time that you create subscriber accounts. Alternatively, the Cisco

Unity Bulk Import wizard allows you to use a CSV file to create subscriber accounts with existing Active Directory contact data.

If you choose to create subscriber accounts with existing contact data, note that the e-mail addresses for the imported contacts are overwritten with extension addresses used for addressing voice messages to the remote voice messaging systems. Thus, the imported objects can no longer be used for outbound message addressing to remote e-mail addresses.

Use the following “To Prepare a CSV File for Creating AMIS Subscriber Accounts” procedure to prepare your CSV file.

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

5-18

OL-13844-01

Chapter 5 AMIS Networking

To learn more about preparing a CSV file for use with the Cisco Unity Bulk Import wizard—including information on the required and optional column headers for your CSV file—see the Cisco Import wizard Help.

To Prepare a CSV File for Creating AMIS Subscriber Accounts

Step 1 Save the data that you will use to create Cisco Unity accounts as a CSV file.

As a best practice, do not include more than 7,500 records in a single CSV file, as you may encounter unexpected results when the Cisco

Step 2 Copy the CSV file to the Cisco Unity Bridgehead server or to a directory that you can browse to from

the server.

Step 3 Open the CSV file in a spreadsheet application or another application with which you can edit and

reorganize the data. Do the following:

• Confirm that the data is separated by commas, and that no tabs, spaces, or semicolons separate the

• If any data includes a space, quotes, or commas, contain the characters within quotes.

Step 4 Rearrange the data so that the columns are in the same order as the column headers that you will add in

Step 5. The order of the column headers does not matter, though it is good practice to set up your CSV

file as indicated here. For example, the columns of data in this sample are sorted so that the last name of the user is followed by the first name, the extension (DTMF_ACCESS_ID), and then by the remote mailbox number (REMOTE_USER_ID):

Procedures for Setting Up Cisco Unity to Use AMIS

Unity Bulk

Unity Bulk Import wizard imports the data.

data in the file.

Abade,Alex,2001,3000 Bader,Kelly,2002,3100 Campbell,Terry,2003,3200 Cho,Li,2004,3300

Step 5 Enter the required column headers above the first row of data. Column headers must be in uppercase,

separated by commas, and spelled as indicated below:

LAST_NAME,FIRST_NAME,DTMF_ACCESS_ID,REMOTE_USER_ID

Note The examples in this procedure illustrate how to set up a CSV file so that the Cisco Unity Bulk

Import wizard creates subscriber accounts and new contacts at the same time. If you choose to create new subscriber accounts with existing contact data, you must also include the ALIAS column header and data in your CSV file.

Step 6 If desired, add optional column headers to the first row, and the corresponding data that you want to

import in the subsequent rows below. As you do so, confirm that:

• Column headers and data are separated by commas. Note that every row does not have to contain

data for any optional column header(s).

• Any data that includes a space, quotes, or commas is contained within quotes.

Step 7 To associate the AMIS subscribers in the CSV file with a delivery location, you can either choose from

the list of defined delivery locations presented by the Cisco

Unity Bulk Import wizard during the import,

or you can add the DELIVERY_LOCATION_ID column to the CSV file.

OL-13844-01

The DELIVERY_LOCATION_ID column contains the dial ID of a delivery location with which the external subscriber will be associated. This value corresponds to the Dial ID field on the Network Delivery Locations > Profile Page in the Cisco

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

Unity Administrator. If this column header is omitted, or

5-19

Procedures for Setting Up Cisco Unity to Use AMIS

if a row does not contain a value, the delivery location that the Cisco Unity Bulk Import wizard prompts for is used as a default. You can import external subscribers for multiple delivery locations by using one CSV file.

Step 8 To help prevent others from sending e-mail to AMIS subscribers, you may want to include the

HIDE_IN_ADDRESS_BOOK column header, and enter a 1 (one) in each row of subscriber data.

A value of 1 indicates that subscribers will be hidden from the e-mail address book; a value of 0 indicates that subscribers will be displayed.

Step 9 If your CSV file contains columns of data that you do not want to import, delete the columns.

Alternatively, you can title one column NOTES. The Cisco beneath any NOTES column header, but the wizard does not support more than one NOTES column in a CSV file.

Step 10 Confirm that every row contains the appropriate data corresponding to each column header.

Step 11 Save the file as a CSV file.

Step 12 Continue with the following “To Create AMIS Subscriber Accounts by Using the Cisco Unity Bulk

Import Wizard” procedure.

Chapter 5 AMIS Networking

Unity Bulk Import wizard ignores data

To Create AMIS Subscriber Accounts by Using the Cisco Unity Bulk Import Wizard

Step 1 Disable virus-scanning services and intrusion-detection software on the bridgehead Cisco Unity server,

if applicable. Otherwise, the Cisco

Unity Bulk Import wizard may run slowly. See Cisco Unity Bulk

Import wizard Help for procedures.

Step 2 On the bridgehead Cisco Unity server, on the Windows Start menu, click Programs > Cisco Unity >

Cisco

Unity Bulk Import.

Step 3 Follow the on-screen instructions.

To learn more about the options presented in the dialog boxes that appear as the wizard proceeds, click Help.

Step 4 When prompted to choose the type of subscriber that you want to create, click AMIS.

Step 5 Click Next, and proceed through the wizard. If the wizard reports any errors, you can:

• Click OK to continue with the import, and fix the errors later.

• Fix the errors. See the “Correcting CSV Import Errors” section on page 5-21 for details.

Step 6 When the subscriber accounts are created, click Finish.

Step 7 If you had import errors, but in Step 5 you chose to correct them later, see the “Correcting CSV Import

Errors” section on page 5-21.

Step 8 If you had no import errors, or if all errors have now been corrected, see the “After Creating AMIS

Subscriber Accounts” section on page 5-22.

5-20

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

OL-13844-01

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)

Customizing the Primary Location

Setting the Addressing, Directory Handler, and Automated Attendant Search Scopes

Setting the Addressing Search Scope

Setting the Directory Handler Search Scope

Setting the Automated Attendant Search Scope

Setting Up Identified Subscriber Messaging Between Networked Cisco Unity Subscribers (Optional)

Setting Permissions on Active Directory Containers Used for Importing Subscribers

Enabling Identified Subscriber Messaging on Each Cisco Unity Server

Modifying the All Subscribers Public Distribution List

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

Changing the Default Search Scope for the Cisco PCA (Optional)

Enabling Live Reply Between Cisco Unity Servers in the Same Dialing Domain (Optional)

Testing the Digital Networking Setup

Digital Networking Concepts and Definitions

Locations and Digital Networking

Dialing Domains

Identified Subscriber Messaging with Networked Cisco Unity Subscribers

Addressing Search Scopes

Addressing Options for Subscribers in a Dialing Domain

Dialing Domains Shield Against Overlapping Numbering Plans

Addressing Options for Non-Networked Phone Systems

When Numbering Plans Do Not Overlap

When Numbering Plans Overlap

Cisco Unity Administrator Scope

Browsing to Another Cisco Unity Administrator from the Local Cisco Unity Administrator

Searching for Subscriber Accounts That Were Created on Another Cisco Unity Server

Using Global Subscriber Manager to Browse to Another Cisco Unity Administrator

Granting Administrative Rights to Other Cisco Unity Servers

Distribution Lists

System Broadcast Messages

Addressing System Broadcast Messages to Digitally Networked Servers

Notable Behavior

How Networked System Broadcast Messages are Processed by Cisco Unity

Mapping Subscribers to Cisco Unity Servers

Cross-Server Logon, Transfers, and Live Reply

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

Phone System Considerations for Cross-Server Features

Planning for Increased Port Usage

A Brief Look at Cisco Unity Data Architecture

Why Cross-Server Logon Is Needed

Why Cross-Server Transfer Is Needed

Why Cross-Server Live Reply Is Needed

Cross-Server Logon

Prerequisites: Enabling Cross-Server Logon

Task List: Enabling Cross-Server Logon

Procedures: Enabling Cross-Server Logon

Verifying That Call Routing Rules Are Set to Route Calls to the Opening Greeting

Enabling Cross-Server Logon and Entering the Pilot Numbers of Destination Cisco Unity Servers

Testing Cross-Server Logon

Cross-Server Transfer from the Automated Attendant and Directory Handlers

Prerequisites: Enabling Cross-Server Transfer

Task List: Enabling Cross-Server Transfer

Procedures: Enabling Cross-Server Transfer

Verifying That Call Routing Rules Are Set to Route Calls to the Opening Greeting