Networking Guide for Cisco Unity Release 8.x (With Microsoft Exchange)
AMIS Networking in Cisco Unity 8.x
Downloads: This chapterpdf (PDF - 481.0KB) The complete bookPDF (PDF - 5.33MB) | Feedback

AMIS Networking in Cisco Unity 8.x

Table Of Contents

AMIS Networking in Cisco Unity 8.x

Setting Up Cisco Unity 8.x to Use AMIS

Prerequisites

Considerations for Deploying AMIS with Cisco Unified Communications Manager and Cisco Gateways

Task List: Setting Up Cisco Unity to Use AMIS

Procedures for Setting Up Cisco Unity 8.x to Use AMIS

Setting Up the Voice Connector for AMIS Networking

Setting Up the Voice Connector for Exchange 2000

Controlling What Happens to Messages That Cannot Be Delivered

Creating the UAmis Account

Designating Voice Ports for Outbound AMIS Calls

Setting AMIS Delivery Options

Customizing the AMIS Restriction Table

Setting Up the AMIS Schedule

Customizing the Primary Location

Creating AMIS Delivery Locations

Using the Cisco Unity Administrator to Create AMIS Delivery Locations

Using the Cisco Unity Bulk Import Wizard to Create AMIS Delivery Locations

Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

Creating AMIS Subscribers

Before Creating AMIS Subscriber Accounts

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

Correcting CSV Import Errors

Using the Cisco Unity Administrator to Create AMIS Subscriber Accounts

After Creating AMIS Subscriber Accounts

Extending Identified Subscriber Messaging to Include AMIS Subscribers

Installations with Multiple Cisco Unity Servers Networked via Digital Networking

Single-Server Installations

Setting Permissions on Active Directory Containers That Are Used for Importing Subscribers

Enabling Identified Subscriber Messaging

Extending Identified Subscriber Messaging

Enabling Cross-Server Transfer for AMIS Subscribers

AMIS Concepts and Definitions in Cisco Unity 8.x

Introduction to AMIS

Port Usage and Schedules

UAmis Account

Voice Connector and AMIS Networking

Locations and AMIS Networking

Message Addressing Options

Message Addressing Limitations

Blind Addressing and AMIS Networking

AMIS Subscribers

Subscriber Experience with AMIS Subscribers

Identified Subscriber Messaging

Live Reply to AMIS Subscribers

Deleting AMIS Subscribers

Extension Addresses

Determining How AMIS Subscribers Appear in the Outlook Address Book

Preventing Contacts From Appearing in the Outlook Address Book

Modifying How Contacts Appear in the Outlook Address Book

Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant

Migrating Subscribers from Another Voice Messaging System to Cisco Unity

Migrating Subscribers in Bulk

Migrating Subscribers One at a Time

Private List Considerations for Migrating Subscribers

Considerations for Networked Cisco Unity Servers

Design Considerations

AMIS Networking Maintenance in Cisco Unity 8.x

Monitoring AMIS Message Traffic

Moving the UAmis Mailbox

Troubleshooting AMIS Networking in Cisco Unity 8.x

Notable Behavior of AMIS Networking in Cisco Unity 8.x

Inbound Messages Are Delivered Only to Primary Extensions

Inbound Search Scope

Running the Voice Connector Setup Program in Another Language


AMIS Networking in Cisco Unity 8.x


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 Unity Digital Networking (and, therefore, accessing subscriber data in the same directory), only one server in the Digital Network needs to be licensed and configured for AMIS Networking. The Cisco Unity server that is configured for AMIS Networking is referred to as the bridgehead server. For more information about obtaining licenses for Cisco Unity features, see the applicable Licensing for Cisco Unity white paper, at 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 Unity server.

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:

Setting Up Cisco Unity 8.x to Use AMIS—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 8.x to Use AMIS—This section contains all of the step-by-step procedures necessary to set up Cisco Unity to use AMIS.

AMIS Concepts and Definitions in Cisco Unity 8.x—This section explains AMIS concepts in detail. You may want to read this section prior to doing the setup procedures.

AMIS Networking Maintenance in Cisco Unity 8.x—This section provides information about monitoring system activity.

Troubleshooting AMIS Networking in Cisco Unity 8.x—This section provides links to troubleshooting information.

Notable Behavior of AMIS Networking in Cisco Unity 8.x—This section provides information about notable behavior related to AMIS Networking.

Setting Up Cisco Unity 8.x to Use AMIS

See the following sections:

Prerequisites

Considerations for Deploying AMIS with Cisco Unified Communications Manager and Cisco Gateways

Task List: Setting Up Cisco Unity to Use AMIS

Prerequisites

Before starting the setup, verify that the following prerequisites have been met.

Cisco Unity is already installed on the servers, and they are connected to the network as applicable to your installation.

A license file with an AMIS license has been obtained and installed on the Cisco Unity bridgehead server.

Cisco Unity meets the requirements as described in the "AMIS Networking Requirements" section of the Networking Options Requirements for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

The voice messaging system with which Cisco Unity will be networked meets the requirements 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.

Verify that the Cisco Unity call routing rules route calls to a call handler, such as the Opening Greeting. (This is the default when Cisco Unity is initially installed.)

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 "Digital Networking in Cisco Unity 8.x" chapter before setting up AMIS Networking. After the Cisco Unity servers have been set up for Digital Networking, verify the following settings:

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-7 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 servers 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 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 handlers 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.

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.

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 Unity subscribers.

b. Re-run the Permissions wizard, and follow the on-screen prompts until the Choose Whether to 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.

4. Designate voice ports for outbound AMIS calls. See the "Designating Voice Ports for Outbound AMIS Calls" section.

5. Set the AMIS delivery options. See the "Setting AMIS Delivery Options" section.

6. Customize the AMIS Restriction Table as needed. See the "Customizing the AMIS Restriction Table" section.

7. Set up the AMIS schedule. See the "Setting Up the AMIS Schedule" section.

8. Customize the primary location profile settings. See the "Customizing the Primary Location" section.

9. Create a delivery location for each remote voice messaging system. See the "Creating AMIS Delivery Locations" section.

10. Optionally, create AMIS subscribers. See the "Creating AMIS Subscribers" section.

11. Optionally, extend identified subscriber messaging to include AMIS subscribers. See the "Extending Identified Subscriber Messaging to Include AMIS Subscribers" section.

12. Optionally, enable cross-server transfers for AMIS subscribers. See the "Enabling Cross-Server Transfer for AMIS Subscribers" section.

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 Unity, and the Node ID that was entered on the primary location.

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 > Unity Diagnostic Tool) to verify that Cisco Unity can send and receive AMIS messages.

Procedures for Setting Up Cisco Unity 8.x 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 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 2003 server.

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 "Running the Voice Connector Setup Program in Another Language" section.

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 Unity server (when Exchange is also on the server), this is not recommended for performance reasons.


Caution Installing the Voice Connector on an Exchange 2007 server is not supported.

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 Unity subscribers are homed, routing group connectors must be 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 15.0(1), which ships with Cisco Unity 8.0(3). 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 Unity Voice Connector for Microsoft Exchange Software Download page at 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 11-5.

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.

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.


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 Unity will not limit the number of days that encrypted messages will be available.)

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.


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 "To 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.)

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 Version 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.

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.)

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.

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 Step 5.

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 email 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.

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 Value.

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 Unity servers licensed for AMIS.

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

To Create the UAmis Account When the Partner Exchange Server Is Running Exchange 2007

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


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.)

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:

.\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.


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.

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 Unity setup.


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 <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 Verify that 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.

Step 2 In the tree control in the left pane, expand Recipient Configuration, and click Mailbox.

Step 3 Verify that UAmis_<ServerName> is in the list of mailboxes in the right pane.

Step 4 Close Exchange Management Console.


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 Unity servers that are licensed for AMIS. See the "Port Usage and Schedules" section 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.


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 servers that are licensed for 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 servers that are licensed for AMIS.

To Customize the AMIS Restriction Table


Step 1 In the Cisco Unity Administrator, go to any Call Management > Restriction Tables page.

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.


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 Unity servers that are licensed for AMIS.

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 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 Unity servers 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 in Cisco Unity 8.x" section on page 10-1.

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 name:

If your installation consists of only one Cisco Unity server, and if you plan to enable identified subscriber messaging to include AMIS subscribers, enter a dialing domain name.

If your installation consists of multiple Cisco Unity servers that are networked via Digital 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.

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 Unity server and wait for the name to replicate to the other 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 Unity servers to be reflected on the local server depends on your network configuration and replication schedule.

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.

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 Unity will be messaging with a large number 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 Unity 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 10-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

Using the Cisco Unity Bulk Import Wizard to Create AMIS Delivery Locations

Modifying Existing Delivery Locations by Using the Cisco Unity Bulk Import Wizard

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.

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 10-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.

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 Unity 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 Unity Bulk Import wizard—including information on the required and optional column headers for your CSV file—see the Cisco Unity Bulk Import wizard Help.

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

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 data in the file.

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.


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.

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.


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 Unity and the remote system can successfully exchange messages. After you have confirmed that messaging between Cisco Unity and the remote system is working correctly, you can finish creating the AMIS subscribers. Note that the AMIS subscribers must be created on the same Cisco Unity server as the AMIS delivery locations.

You can create AMIS subscriber accounts by using the Cisco Unity Bulk Import wizard or the Cisco Unity Administrator. See the following sections:

Before Creating AMIS Subscriber Accounts

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

Using the Cisco Unity Administrator to Create AMIS Subscriber Accounts

After Creating AMIS Subscriber Accounts

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 Unity Bridgehead server. Do the following tasks on the Cisco Unity Bridgehead server where you will be adding the AMIS subscribers.

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 Unity is properly configured to work with your message store, do the following "To Check Cisco Unity Setup and Permissions by Using the Cisco Unity SysCheck Tool" 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.

Step 5 Click Test.

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 Unity 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 Unity includes predefined classes of service that you can modify. You can also create new classes of service. For details, see the "Managing Classes of Service in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

3. Restriction Tables

Each COS specifies a restriction table for call transfers, one for message notification, and one for fax deliveries. Cisco Unity applies the restriction table associated with the COS of a subscriber, and displays an error message if the phone number is not allowed. Cisco Unity comes with predefined restriction tables that you can modify.

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 in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

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 in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

Public distribution lists correspond to distribution groups in Active Directory. The distribution lists are listed in the address book for Microsoft Outlook (or other email client), unless they are explicitly hidden. To help prevent others from sending email 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 Unity Administrator.

5. Subscriber Templates

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 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 in Cisco Unity 8.x" chapter in the System Administration Guide for Cisco Unity Release 8.x.

AMIS subscribers correspond to contacts in Active Directory. The contacts are listed in the address book for Microsoft Outlook (or other email 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 "Determining How AMIS Subscribers Appear in the Outlook Address Book" section for details.


Note The System Administration Guide for Cisco Unity Release 8.x is available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/administration/guide/8xcusagx.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 email 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 email addresses.

Use the following "To Prepare a CSV File for Creating AMIS Subscriber Accounts" procedure to prepare your CSV file.

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 Unity Bulk 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 Unity Bulk Import wizard imports the data.

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 data in the file.

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):

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 headers.

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.

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 Unity Administrator. If this column header is omitted, or 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 email 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 email 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 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 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.


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

Step 8 If you had no import errors, or if all errors have now been corrected, see the "After Creating AMIS Subscriber Accounts" section.


Correcting CSV Import Errors

The error log file contains data that the Cisco Unity Bulk Import wizard could not import. The wizard reports the first error it detects in a row in a CSV file. When you have corrected that error, the wizard may detect additional errors in the same 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, do the following "To Correct Errors That Occurred When Importing Data from a CSV File" procedure.

To Correct Errors That Occurred When Importing Data from a CSV File


Step 1 Browse to the directory that contains the error log file 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 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.

Step 7 Run the Cisco Unity Bulk Import wizard again with the CSV file that you saved in Step 6.

Step 8 Repeat this procedure until all subscriber accounts are created without error, and then proceed to the "After Creating AMIS Subscriber Accounts" section.


Using the Cisco Unity Administrator to Create AMIS Subscriber Accounts

By using the Cisco Unity Administrator, you can create AMIS subscriber accounts one at a time. When you add a new AMIS subscriber account, Cisco Unity creates a contact in Active Directory.

To create an AMIS subscriber account, do the following "To Add a New AMIS Subscriber by Using the Cisco Unity Administrator" procedure.

To Add a New AMIS Subscriber by Using the Cisco Unity Administrator


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

Step 2 Click the Add icon.

Step 3 Click New and select AMIS from the list.

Step 4 Enter the First Name and Last Name.

Step 5 Enter the Extension of the AMIS subscriber on Cisco Unity. This is the number that Cisco Unity subscribers will use when addressing a message to this AMIS subscriber.

Step 6 Select the Subscriber Template to use.

Step 7 Enter the Remote Mailbox Number, which is the number that the remote voice messaging system uses to route messages to this AMIS subscriber.

Step 8 Select the Delivery Location with which the subscriber is associated.

Step 9 Click Add.

Step 10 On the subscriber record, customize settings as applicable, and then click the Save icon.


After Creating AMIS Subscriber Accounts

After creating AMIS subscriber accounts, consider the following:

It takes a few minutes for the newly-created subscriber account to be available to receive messages.

You can make changes to subscriber settings for individual accounts in the Cisco Unity Administrator.

When you want to modify unique subscriber settings—such as primary or alternate extensions—for multiple subscribers at once, you can (re)run the Cisco Unity Bulk Import wizard. To learn more, see the Cisco Unity Bulk Import wizard Help.

When a subscriber leaves the organization or otherwise no longer needs a Cisco Unity account, you can delete the subscriber account. See the "Deleting AMIS Subscribers" section for details.

Extending Identified Subscriber Messaging to Include AMIS Subscribers

When a person on a remote voice messaging system who has a corresponding AMIS subscriber account calls a Cisco Unity subscriber and leaves a message, by default Cisco Unity will not identify the message as being from the AMIS subscriber. For Cisco Unity to identify callers whose calling number matches the extension or alternate extension of an AMIS subscriber, identified subscriber messaging (ISM) must be extended to include AMIS subscribers. See the following sections as applicable to your installation.

Installations with Multiple Cisco Unity Servers Networked via Digital Networking

Single-Server Installations

Installations with Multiple Cisco Unity Servers Networked via Digital Networking

In installations with multiple Cisco Unity servers networked via Digital Networking, enabling ISM to include AMIS subscribers requires the following:

The Cisco Unity servers must be connected to the same phone system or phone system network as described in the "Dialing Domains" section on page 2-15.

The servers must be configured to be in the same dialing domain, as described in the "Customizing the Primary Location" section.

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 on each server must be set, as described in the "Setting Permissions on Active Directory Containers That Are Used for Importing Subscribers" section.

Identified subscriber messaging on each server must be enabled as described in the "Enabling Identified Subscriber Messaging" section.

Identified subscriber messaging on each server must be extended for AMIS subscribers as described in the "Extending Identified Subscriber Messaging" section.

Single-Server Installations

In installations with only one Cisco Unity server, enabling ISM to include AMIS subscribers requires the following:

The server must be configured with a dialing domain name, as described in the "Customizing the Primary Location" section.

The applicable permissions must be set, as described in the "Setting Permissions on Active Directory Containers That Are Used for Importing Subscribers" section.

Identified subscriber messaging must be enabled as described in the "Enabling Identified Subscriber Messaging" section.

Identified subscriber messaging must be extended for AMIS subscribers as described in the "Extending Identified Subscriber Messaging" section.

Setting Permissions on Active Directory Containers That Are Used for Importing Subscribers

If you will be importing contacts from two or more containers (for all of the Cisco Unity servers combined), the Cisco Unity message store services account on each Cisco Unity server must be granted SendAs permission on every container from which contacts will be imported on every Cisco Unity server in the forest. Otherwise, identified subscriber messaging may not work between Cisco Unity servers. For example, if CiscoUnityServer1 will import contacts from Container1 and Container2, and if CiscoUnityServer2 will import contacts from Container3 and Container4, Cisco Unity message store services account on each Cisco Unity server must have SendAs permission for all four containers.

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.

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 Unity server.

Choose the applicable containers:

Click Next without changing any options until you arrive at the Choose Active Directory 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

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.

To Enable Identified Subscriber Messaging


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.

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.


Extending Identified Subscriber Messaging

After identified subscriber messaging has been enabled, you must extend it to include AMIS subscribers.

To Extend Identified Messaging


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 - Enable Identified Subscriber Messaging (ISM) for AMIS, Bridge, and VPIM Subscribers.

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

Step 5 When prompted, click OK.

Step 6 Click Exit.

Step 7 Restart Cisco Unity for the registry setting to take effect.


Enabling Cross-Server Transfer for AMIS Subscribers

By default, call transfers to AMIS subscribers that are 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. Optionally, you can configure Cisco Unity to use the cross-server transfer settings when transferring calls to AMIS subscribers who are 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 in Cisco Unity 8.x" section on page 3-8. If you already have cross-server transfer configured, see the "Optional: Disabling Cross-Server Transfer for External Subscribers" section on page 3-10 for details on expanding the cross-server transfer functionality to include AMIS subscribers.

AMIS Concepts and Definitions in Cisco Unity 8.x

The following sections explain AMIS concepts in detail:

Introduction to AMIS

Port Usage and Schedules

UAmis Account

Voice Connector and AMIS Networking

Locations and AMIS Networking

Message Addressing Options

Blind Addressing and AMIS Networking

AMIS Subscribers

Identified Subscriber Messaging

Live Reply to AMIS Subscribers

Deleting AMIS Subscribers

Extension Addresses

Determining How AMIS Subscribers Appear in the Outlook Address Book

Migrating Subscribers from Another Voice Messaging System to Cisco Unity

Considerations for Networked Cisco Unity Servers

Introduction to AMIS

In AMIS terminology, Cisco Unity and the other voice messaging systems that it communicates with are called nodes. Each node is assigned a unique ID, referred to as a Node ID. The node that places an AMIS call and delivers messages is called the originating node. The node that answers the AMIS call and receives messages is called the destination node. If a particular system acts as both an originating node and a destination node, its Node ID is the same for both functions. AMIS nodes correspond to locations in Cisco Unity.

The Cisco Unity subscribers and the users on the other voice messaging systems are identified by mailbox numbers. On Cisco Unity, the mailbox number for a subscriber is the same as the subscriber extension.

Voice messages are transmitted between nodes by using ordinary phone connections. When one node calls another by dialing a specified delivery phone number, the originating node transmits its Node ID by using a sequence of touchtones. If the destination node accepts the call, the originating node transmits each voice message by using analog playback, and the destination node records each message and delivers it to the applicable mailbox. For detailed information about the touchtones that are transmitted during an AMIS call, see the AMIS Analog Networking Definitions white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

In compliance with the AMIS protocol, Cisco Unity batches outgoing messages by node, with a maximum of nine messages per batch. If there are more than nine messages for a particular node, Cisco Unity ends the AMIS session after sending the ninth message, hangs up for a brief period of time, and then redials the node to send the next batch of messages.

The AMIS protocol specifies that a message be a maximum of eight minutes long. During an AMIS transmission, before playing a message, the originating node sends to the destination node the length of the message. If the message is too long, the destination node may refuse the message and skip to the next message. However, some voice messaging systems will accept longer messages. If the voice messaging system refuses the message, a non-delivery receipt (NDR) is returned to the sender. If a subscriber sends a message that is longer than eight minutes, Cisco Unity will attempt to transmit it. In addition, Cisco Unity may accept messages longer than eight minutes. For each incoming message, Cisco Unity checks the space available in the subscriber mailbox and the Maximum Message Length setting on the Subscriber > Messages page to determine whether to accept the message.

Incoming AMIS messages to Cisco Unity are delivered to subscriber mailboxes only, and cannot be delivered to public distribution lists. Additionally, incoming messages must be addressed to the primary extension of the subscriber; messages addressed to an alternate extension will not be delivered. See the "Inbound Messages Are Delivered Only to Primary Extensions" section for additional information.

Note that for incoming AMIS calls, the initial "handshake" between the originating system and Cisco Unity must take place in a call handler, such as the Opening Greeting call handler. For AMIS Networking to be properly configured, you need to ensure that all incoming AMIS calls are routed to a call handler. When Cisco Unity is initially installed, the default setting is for the call routing table to route calls to the Opening Greeting call handler; thus it is properly configured for AMIS Networking. If the call routing table has been modified after installation, you need to make sure that a rule is in place in your call routing table to route any incoming AMIS calls to a call handler.

Port Usage and Schedules

In the Cisco Unity Telephony Integration Manager (UTIM) and in the Cisco Unity Administrator on the System > Ports page, you can designate which ports on your system are used for outgoing AMIS calls. All ports are used for incoming AMIS calls.

AMIS transmissions can be lengthy and thus tie up ports on your Cisco Unity server. For example, 10 hours of AMIS messages take at least 10 hours of port time to transmit. A 2-minute message that is sent to a public distribution list that contains 200 AMIS recipients results in 200 messages in the outbound queue, and would require at least 6.5 hours of port time to transmit.

When multiple ports have been designated for outgoing AMIS messages, Cisco Unity uses all designated ports as message traffic warrants. The total number of ports used is limited by the availability of ports that have been designated for outgoing AMIS calls. For example, if there are 10 ports available for outgoing AMIS messages, and 10 hours of messages to deliver, all 10 ports are used for message delivery, and the time to transmit all of the messages will be about one hour plus the time it takes to place the calls and establish the AMIS sessions.

Outbound messages are sorted according to their destination, and then batched into groups of 9. If there are multiple destinations, multiple ports are used to transmit the messages. If there are numerous messages to one destination, each batch of messages (with a maximum of nine per batch) is transmitted on a different port, if one is available. In other words, if you have multiple ports designated for AMIS message delivery, multiple ports will be used to handle the messages to a single node, as needed. As the number of messages for a particular node increases, an additional port is added when the number of outgoing messages reaches a multiple of nine. For example, one port will be used for message delivery if there are nine or fewer messages to a node. For 10-18 messages, two ports will be used. For 19-27 messages, three ports will be used, and so on.

After a port starts an AMIS session, it continues sending messages as long as there are messages to be sent. The port disconnects only when there are no more outgoing messages, or after it sends the ninth message to the same node. In this case, the port disconnects briefly, and then continues sending messages if there are more messages that need to be sent.

Because the transmission of outgoing AMIS messages can tie up voice ports for long periods of time, you may want to adjust the schedule so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls. Additionally, if most or all of your AMIS delivery numbers are long distance, you may want to schedule the outgoing AMIS calls when the long distance phone rates are lower. Keep in mind, however, that outgoing messages are queued up in the UAmis mailbox, so there must be sufficient storage available if you restrict the delivery window.

You can override the AMIS schedule so that messages that are marked urgent are sent immediately. Additionally, by setting up a restriction table, you can specify which delivery numbers are sent immediately and which numbers must wait for the AMIS schedule to become active.

If you adjust the AMIS schedule so that outgoing AMIS calls are made only after normal business hours, be sure to inform subscribers. They may choose to contact users on the other voice messaging system directly, or send email, rather than send a voice message that will not be delivered immediately.

If your schedule is such that outbound AMIS calls are placed during normal business hours or when call volumes are heavy, you may want to dedicate certain ports exclusively for incoming calls and other ports exclusively for TRAP. By excluding AMIS outbound calls from those ports, you ensure that there will be ports available for calls of a time-sensitive nature. Use the Ports Usage Analyzer, available in Tools Depot, to monitor traffic for a few days and then adjust the ports as needed.

When Cisco Unity has an outbound AMIS call to make, it searches backwards for a port to use, starting with the last port (which is the highest numbered port), until it finds an available port that is configured for outbound AMIS calls. When integrated with multiple phone systems, Cisco Unity starts the search for an available port with the last port in the last integration (again, this is the highest numbered port).

In organizations with multiple Cisco Unity servers networked together, you can set up a "bridgehead" Cisco Unity server to handle all AMIS calls—both inbound and outbound—for all of the Cisco Unity servers in the network. This way, the ports on just one Cisco Unity server are used for AMIS messages.

UAmis Account

Outgoing AMIS messages are placed in a special Exchange mailbox called UAmis_<Server name>. Before AMIS messages can be transmitted, you must create the UAmis account.

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 Unity setup.

The storage limits for the UAmis mailbox are set to the limits that are defined for the mailbox store in which the UAmis mailbox is created. Although you can change the storage limits for the UAmis mailbox by using the Exchange administration application, do so with caution. If the UAmis mailbox is full, subsequent outgoing messages cannot be delivered, and the sender receives a NDR.

Consider the following when determining whether limits should be set on the UAmis mailbox:

If the AMIS dialing restrictions and schedule are configured such that AMIS messages are delivered only during specified periods of the day, messages are queued up in the UAmis mailbox. The storage limit must be high enough to store all AMIS messages during the non-delivery periods.

There could be times during the day when the number of AMIS messages spikes. The storage limit must be high enough to handle this.

If hard disk space on the Exchange server is limited, you may want to set a limit to ensure that available space is not exceeded.

You may want to monitor the outgoing AMIS message traffic by running the AMIS Out Traffic Report before setting limits on the UAmis mailbox. For more information, see the "AMIS Out Traffic Report" section in the "Reports" chapter of the Maintenance Guide for Cisco Unity. The Maintenance Guide for Cisco Unity is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

The UAmis mailbox can be moved and deleted just like any other Exchange mailbox, by using standard Microsoft tools. Be sure to let anyone who administers Active Directory and Exchange know about the UAmis account so that it is not moved or deleted by mistake. To avoid inadvertently moving or deleting the UAmis account, consider changing the Exchange display name so that the account is more clearly identified to you or the Exchange administrator as requiring "special" treatment. You can also hide the UAmis account so that it does not appear in the Outlook address book.

For information on moving the UAmis mailbox, see the "UAmis Mailbox" section in the "Cisco Unity Data and Log Files" chapter of the Maintenance Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.

Messages are sent from the UAmis mailbox at one or more of the following times:

When a message is marked urgent, and the AMIS delivery option settings allow urgent messages to be sent immediately.

When the AMIS restriction table allows the delivery number of a message.

When the AMIS schedule becomes active.

Messages that have not been sent when the schedule becomes inactive remain in the UAmis mailbox until the schedule becomes active again. An error is logged in the Windows Application Event log when messages remain in the UAmis mailbox for more than 24 hours. See the "AMIS Networking Maintenance in Cisco Unity 8.x" section for information about monitoring the UAmis mailbox.

In organizations with multiple Cisco Unity servers networked together, the UAmis account needs to be created only on those Cisco Unity servers that will place and receive AMIS calls. See the "Considerations for Networked Cisco Unity Servers" section for more information.

Voice Connector and AMIS Networking

The Voice Connector allows Cisco Unity to send and receive AMIS messages. When subscribers use the phone to address a message to an AMIS recipient, Cisco Unity constructs an address with the form AMIS:<Location Dial ID>_<Remote Mailbox> for the message. The Voice Connector is registered with Exchange to handle messages with the AMIS address type. For an outbound message to an AMIS recipient, the Voice Connector transforms the message properties and delivers the message to the UAmis mailbox. For installations with multiple Cisco Unity servers that are licensed for AMIS, the Voice Connector delivers the message to the UAmis mailbox that is associated with the Cisco Unity server on which the AMIS location or AMIS subscriber was created.

Install the Voice Connector for Exchange 2000. See the "Setting Up the Voice Connector for AMIS Networking" section for information about setting up the Voice Connector.

The Voice Connector for Exchange 2000 version 11.0(1) or later can be installed on either an Exchange 2000 or Exchange 2003 server.

Installing the Voice Connector on an Exchange 2007 server is not supported.

Locations and AMIS Networking

Central to how you set up AMIS 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. When setting up AMIS, you give the primary location a new name and a Dial ID (which is an identifier for the location within Cisco Unity), enter the AMIS Node ID, and customize other properties as applicable. The AMIS Node ID on the primary location is transmitted on all outgoing AMIS calls and identifies your Cisco Unity system to the destination nodes. See the "Primary Location Profile Settings in Cisco Unity 8.x" section on page 10-1 for details about the settings.

You create a delivery location in Cisco Unity to correspond to each remote voice messaging system with which Cisco Unity communicates. Delivery locations contain the information that Cisco Unity needs to exchange messages with other nodes—the Delivery Phone Number and the AMIS Node ID.

In organizations with multiple Cisco Unity servers networked together, the delivery locations should be created only on those Cisco Unity servers that are licensed for AMIS. See the "Considerations for Networked Cisco Unity Servers" section for more information.

Message Addressing Options

Cisco Unity provides the following message addressing options:

Blind addressing—Allows Cisco Unity subscribers to send messages to subscribers on the remote voice messaging system even though the recipient mailbox number, name, and recorded name are not in the directory. Even though Cisco Unity cannot provide voice name confirmation (hence the term "blind addressing"), the message is addressed and sent. See the "Blind Addressing and AMIS Networking" section for more information.

AMIS subscribers—Allows Cisco Unity subscribers to get voice name confirmation when addressing messages to subscribers on the remote voice messaging system. AMIS subscribers are a representation in Cisco Unity of the subscribers on the remote messaging system. AMIS subscribers are created in Cisco Unity to enable Cisco Unity subscribers to find them in the directory and send messages to them as they would with any other subscriber. See the "AMIS Subscribers" section for more information.

Message Addressing Limitations

Subscribers can use the Cisco Unity phone conversation (also known as the telephone user interface, or TUI), Cisco Unity ViewMail for Microsoft Outlook, or the Cisco Unity Inbox to reply to and forward AMIS messages just as they do with regular voice messages. However, when sending or retrieving AMIS messages, subscribers will encounter the following limitations:

AMIS messages that are marked urgent when they are sent are not marked urgent when they are retrieved by the recipient.

AMIS messages that are marked private when they are sent are not marked private when they are retrieved by the recipient.

Requests for return receipts on AMIS messages are not honored.

Email messages cannot be sent to AMIS recipients even though ViewMail allows subscribers to address them. Instead of being delivered, email messages that are sent to AMIS recipients are returned to the sender as NDRs.

Messages that are sent from AMIS subscribers to Cisco Unity subscribers cannot be encrypted and therefore are not affected by the message aging functionality of Secure Messaging.

Blind Addressing and AMIS Networking

AMIS blind addressing is one of the methods that Cisco Unity provides for addressing AMIS messages to users of another voice messaging system. Blind addressing allows Cisco Unity subscribers to send messages to subscribers on the remote voice messaging system even though the recipient mailbox number, name, and recorded name are not in the directory. Even though Cisco Unity cannot provide voice name confirmation (hence the term "blind addressing"), the message is addressed and sent.

One of the steps to setting up blind addressing is adjusting the Blind Addressing setting on the Primary Location > Addressing Options page. You also create a delivery location that corresponds to each voice messaging system with which Cisco Unity communicates.

You provide the following information for each delivery location:

Delivery Phone Number—The number that Cisco Unity dials to reach the other voice messaging system.

AMIS Node ID—The number that is used by Cisco Unity to identify the remote voice messaging system during an AMIS transmission. For incoming calls, Cisco Unity searches the AMIS delivery locations for an AMIS Node ID that matches the value transmitted by the originating node. If a corresponding location is not found, Cisco Unity follows the AMIS protocol and rejects the call without recording messages.

Dial ID—A unique number that identifies the location to Cisco Unity. This is the number that subscribers dial when blind addressing messages to individuals who use the remote voice messaging system.

When blind addressing a message, subscribers dial a number that is made up of the delivery location Dial ID and the mailbox number of the recipient. Before addressing the message, Cisco Unity parses the number that the subscriber entered and searches for a matching delivery location. If Cisco Unity does not find a matching location, it reports the error to the sender and does not address the message. If a matching delivery location is found, Cisco Unity addresses the message without verifying that the remote mailbox number exists. Cisco Unity does provide voice name confirmation that the delivery location exists before addressing the message (assuming that a voice name was recorded for the delivery location).

Because your Cisco Unity server does not have access to the names and extensions of the users on the other voice messaging system, subscribers cannot use spelling mode when blind addressing a message to someone on the other system.

Subscribers can also address voice messages in ViewMail for Outlook and in the Cisco Unity Inbox to someone on the remote voice messaging system by using the following format: [AMIS:<Location Dial ID>_<Remote Mailbox>]. For example, to send a message to Dial ID 206, mailbox 555, the address is: [AMIS:206_555]; the brackets must be included in the address.

For administrators of Cisco Unity, blind addressing is the option that requires the least amount of work to set up. However, subscribers will encounter some limitations when blind addressing messages to users on the other voice messaging system. Subscribers can address the message only by using number mode, so they must know the delivery location Dial ID and the mailbox number for the recipient. Additionally, Cisco Unity cannot verify that the number entered is correct, so subscribers may inadvertently address a message to the wrong person or to a non-existent mailbox.

Subscribers can use the Cisco Unity conversation to add and delete blind addresses in their private distribution lists. In contrast, subscribers cannot use the Cisco Unity Assistant to add blind addresses to their private lists, though they can use it to view list members and to delete any blind addresses that were added by phone. The Cisco Unity Administrator also does not allow you to add blind addresses to private lists, but you can use it to view and delete list members.

Note that when you delete a delivery location, blind addressees at that location are also removed from all private lists. Consider notifying subscribers of these potential changes to their private lists.

In organizations with multiple Cisco Unity servers networked together, when subscribers use blind addressing to address messages to someone at an AMIS location, the AMIS transmission originates from the Cisco Unity server on which the AMIS delivery location was created. See the "Considerations for Networked Cisco Unity Servers" section for more information.

AMIS Subscribers

AMIS subscribers are a representation in Cisco Unity of the subscribers on the remote messaging system. AMIS subscribers are created in Cisco Unity to enable Cisco Unity subscribers to find them in the directory and to send messages to them as they would with any other subscriber. Voice messages that are addressed to AMIS subscribers are sent to the voice messaging system that they use.

AMIS 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 AMIS subscribers.

To set up AMIS subscribers, you first create an AMIS delivery location that corresponds to each remote voice messaging system with which Cisco Unity communicates. After creating the delivery locations, you create an AMIS subscriber account for each remote user. When creating each AMIS subscriber account, you specify the user mailbox number on the other voice messaging system and select the AMIS delivery location with which the AMIS subscriber is associated. Cisco Unity uses the Delivery Phone Number and AMIS Node ID from the associated delivery location when delivering messages to the AMIS subscriber.

In organizations with more than one Cisco Unity server licensed for AMIS, AMIS subscribers can be associated only with AMIS delivery locations that are created on the same Cisco Unity server that the AMIS subscribers will be created on. When subscribers address messages to an AMIS subscriber, the AMIS transmission originates from the Cisco Unity server on which the AMIS subscriber was created. See the "Considerations for Networked Cisco Unity Servers" section for more information.

AMIS subscribers in Cisco Unity are represented as contacts in Active Directory. When you delete AMIS subscribers in the Cisco Unity Administrator, the underlying contacts are removed automatically.

You create and manage AMIS subscriber accounts in much the same way that you do regular subscriber accounts. You can use the Cisco Unity Administrator to create, modify, and delete AMIS subscriber accounts one at a time, and you can use the Cisco Unity Bulk Import wizard to create and modify multiple AMIS subscriber accounts.

Extensions are mandatory for AMIS subscriber accounts. The extension, which must be unique across the dialing domain, is the number that Cisco Unity subscribers dial when addressing a message to an AMIS subscriber. This number may or may not be the same as the mailbox number of the subscriber on the remote voice messaging system. Callers who reach the opening greeting of your organization can dial the extension of an AMIS subscriber or look up an AMIS subscriber in directory assistance and leave a message.

Other than receiving messages, AMIS subscribers do not have access to other Cisco Unity features, and some sections of the Cisco Unity Administrator are disabled for AMIS subscribers. AMIS subscribers:

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. However, AMIS subscriber voice names can be imported by using the Cisco Unity Bulk Import wizard. See the Cisco Unity Bulk Import wizard Help for details.

Cannot use the Cisco Unity Inbox to check messages.

Cannot own private lists.

Cannot set up or receive message notifications.

Cannot receive message waiting indications.

Setting up AMIS subscribers requires more overhead for administrators of Cisco Unity than AMIS blind addressing does. However, the AMIS subscriber option allows other subscribers to address messages to AMIS subscribers the same way that they address messages to regular subscribers.

Subscriber Experience with AMIS Subscribers

Provided that AMIS subscribers are listed in the phone directory and have had voice names and greetings recorded for them:

Subscribers can address messages to AMIS subscribers by using the phone, ViewMail for Outlook, or the Cisco Unity Inbox.

Contacts that correspond to AMIS 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 Unity Inbox address book. Therefore, message addressing to AMIS subscribers—either by using Outlook or the Cisco Unity Inbox—is the same as for regular subscribers.

When using the phone, subscribers can address messages to AMIS subscribers in spelled-name mode (if enabled on the system) or by extension.

Subscribers get voice name confirmation when addressing a message to a AMIS subscriber.

When subscribers use the phone to listen to messages, the conversation announces who the message is from.

AMIS subscribers can be added to public and private distribution lists.

Note that when Cisco Unity records a message from an unidentified caller for an AMIS subscriber, the Dial ID of the primary location is used as the sending mailbox. Although AMIS subscribers are not prevented from replying to these messages, the replies are returned to the Unity Messaging System mailbox as NDRs.

Identified Subscriber Messaging

Identified subscriber messaging (ISM) affects what subscribers hear when they call other subscribers from their primary or alternate extensions and are forwarded to the greetings of the subscribers they call. If they then leave a message, ISM affects what the called subscriber hears and can do when listening to the message. When ISM is enabled, Cisco Unity recognizes that the calling extension is associated with a subscriber and accordingly plays the internal greeting of the called subscriber. Additionally, when the called subscriber later listens to the message, Cisco Unity plays the recorded voice name of the subscriber who left the message and allows the called subscriber to record a reply.

When a call to a Cisco Unity subscriber is forwarded to the subscriber greeting and ISM is enabled, Cisco Unity compares the calling number (ANI or caller ID) to the primary and alternate extensions of subscribers. If a match is found, Cisco Unity identifies the caller as a subscriber. When Cisco Unity compares the calling number to extensions, by default, only "regular" Cisco Unity subscribers on the local system are included in the comparison. ISM can be expanded to include all Cisco Unity subscribers throughout a dialing domain.

You can enable ISM for AMIS, Bridge, and VPIM subscribers (collectively referred to as external subscribers), so that Cisco Unity will include them when comparing calling numbers to extensions. Note the following:

After enabling ISM for external subscribers, Cisco Unity must be restarted.

If multiple Cisco Unity servers are networked via Digital Networking, ISM functionality can be made available only on the Cisco Unity servers that are in the same dialing domain as the bridgehead server.

You must enable ISM for external subscribers for each Cisco Unity server on which the functionality is desired.

If a single Cisco Unity server is in use, the Cisco Unity server must be a member of a dialing domain for this functionality to be used.

Note the difference between leaving a messaging and sending a message. When a person on the remote voice messaging system with a corresponding external subscriber account records and sends a message to a Cisco Unity subscriber (as opposed to calling and leaving a message), Cisco Unity identifies the message as being from the corresponding external subscriber.

The phone system provides the calling number to Cisco Unity. The number of digits included in the calling number is configurable in most phone systems. For Cisco Unity to find a matching subscriber extension, the phone system must be configured to provide the applicable number of digits in the calling number. You may also need to add alternate extensions to the subscriber accounts to match the calling number. Additionally, there may be other phone system-specific issues that prevent Cisco Unity from matching the calling number to a subscriber extension. Refer to your phone system documentation and the applicable Cisco Unity integration guide for details about the call information provided by the phone system.

Live Reply to AMIS Subscribers

Live reply allows subscribers who listen to their messages by phone to respond to messages from other subscribers by calling them. When live reply is enabled, subscribers who are listening to messages by phone can reply to a subscriber message by choosing the "call the subscriber" option to have Cisco Unity call the subscriber directly. Note that subscriber access to the live reply feature depends on their class of service settings. (Live reply is enabled on the Subscribers > Class of Service > Messages page in the Cisco Unity Administrator.)

Subscribers can live reply to messages from subscribers on other voice messaging systems who have corresponding AMIS subscriber accounts in Cisco Unity. In order for the live reply call to be successfully transferred, a call transfer number must be configured for the AMIS subscribers.

Note that a live reply to an AMIS subscriber is always done via a release to phone system transfer, even when both the Cisco Unity subscriber who is replying to a message and the AMIS subscriber have accounts on the same Cisco Unity server. On a release to switch transfer, Cisco Unity dials the call transfer number that is configured for the AMIS subscriber and hangs up, leaving the phone system to handle the call. Note the following limitations with release to switch transfers:

The AMIS 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 AMIS subscriber extension and hangs up. If the subscriber extension is a valid extension on the phone system that Cisco Unity is integrated with, then 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.

Note the following:

Live reply to AMIS subscribers is enabled automatically, and cannot be disabled.

Live replies to AMIS subscribers with accounts on other Cisco Unity servers do not use the cross-server live reply functionality that can be used to live reply to Cisco Unity subscribers with accounts on other Cisco Unity servers. However, for live reply to be offered when a Cisco Unity subscriber replies to a message from an AMIS subscriber with a subscriber account on another Cisco Unity server, the servers must be in the same dialing domain.

Deleting AMIS Subscribers

Each AMIS subscriber is associated with an Active Directory contact. When you delete AMIS subscribers in the Cisco Unity Administrator by deleting the subscriber accounts individually, the underlying directory objects are automatically deleted. To delete all of the AMIS subscribers that are associated with a delivery location, the underlying contacts for those subscribers, and the delivery location itself, use the Global Subscriber Manager, available in Tools Depot.

Note that when you delete an AMIS delivery location, blind addressees are also removed from all private lists. Consider notifying subscribers of these potential changes to their private lists.

Extension Addresses

When you create an AMIS subscriber, Cisco Unity automatically generates an email address in the following format:

AMIS:<Location Dial ID>_<Remote Mailbox>

This special email address is referred to as an extension address (or a remote address). The extension address is a combination of the delivery location Dial ID with which the AMIS subscriber is associated, and the Remote Mailbox Number of the AMIS subscriber. Each contact in Active Directory that corresponds to an AMIS subscriber contains an extension address.

When subscribers use the phone to address messages to an AMIS subscriber, they dial an extension. Cisco Unity recognizes the recipient as an AMIS subscriber and retrieves the extension address from the SQL Server database on the Cisco Unity server.

Extension addresses are generated automatically when you create AMIS subscribers, and are automatically updated if you change the Dial ID of a delivery location or the remote mailbox number.

Determining How AMIS Subscribers Appear in the Outlook Address Book

Depending on your installation, the users of the remote voice messaging system may already have Active Directory accounts and Exchange mailboxes on your local network that they use for email. Therefore, when AMIS subscriber accounts are created for them, the Exchange address lists will contain duplicate listings—the existing user account that is used for email and a new contact that is used only for voice mail. Both listings are included in the Outlook address book. This means that people may inadvertently send email messages to the contact, which should be used only for addressing voice messages.

To discourage people from inadvertently sending email messages to AMIS subscribers, you can prevent the associated contact from appearing in the Outlook address book. Alternatively, you can change how the display name for the contact appears in the Outlook address book so that subscribers can distinguish the contact from a user account. In this way, you can reduce the number of email messages inadvertently sent to contacts and simplify addressing for those who send voice messages to AMIS subscribers at the same time.

If you prefer that the associated contacts for subscribers do not appear in the Outlook address book at all, see the "Preventing Contacts From Appearing in the Outlook Address Book" section.

Alternatively, if you want to alter how contacts appear in the Outlook address book, see the "Modifying How Contacts Appear in the Outlook Address Book" section.

Preventing Contacts From Appearing in the Outlook Address Book

Either before or after you create AMIS subscriber accounts, you can prevent the associated contact from appearing in the Outlook address book by hiding the contacts from Exchange address lists. When you do so, Exchange will still deliver email messages that are addressed to an existing user account (if one exists) and to the contact. However, the number of email messages that are sent to the contact may be reduced because subscribers cannot inadvertently pick the contact from the Outlook address book when addressing messages to them.

To prevent subscribers from appearing in Outlook address books, you can use the Cisco Unity Administrator, the Cisco Unity Bulk Import wizard, Bulk Edit, or Active Directory Users and Computers:

To do so in the Cisco Unity Administrator, uncheck the Show Subscriber In Email Server Address Book check box on the Profile page for the subscriber template that you plan to use when creating AMIS subscribers, or on individual subscriber Profile pages after you have created the subscriber accounts.

To do so by using the Cisco Unity Bulk Import wizard or the Bulk Edit utility, see the Help for each tool.

To do so in Active Directory Users and Computers, click View > Advanced Features to see the Exchange Advanced property page for a user, and then check the Hide From Exchange Address Lists check box on the Exchange Advanced tab.

Modifying How Contacts Appear in the Outlook Address Book

As an alternative to preventing a contact from appearing in the Outlook address book altogether, you may want to alter the display name for the contact so that subscribers can distinguish the contact from the user account. For example, you could append " - Voice mail" to the display name of each AMIS subscriber, and the names would appear in the Outlook address book as follows:

Abade, Alex
Abade, Alex - Voice mail
Bader, Kelly
Bader, Kelly - Voice mail
Campbell, Terry
Campbell, Terry - Voice mail
Cho, Li
Cho, Li - Voice mail

In this way, subscribers can easily determine which address is appropriate to use when they send voice messages to AMIS subscribers. Additionally, when subscribers use the Outlook address book to address a message to a contact, they can be confident that the address is formatted correctly.

Preventing Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant

In the transition from a legacy voice messaging system to Cisco Unity, your organization may choose to migrate users to Cisco Unity in phases. As a result, Cisco Unity will likely support both regular subscribers and "external" subscribers—Bridge, AMIS, or VPIM contacts (as applicable)—at the same time. Regular subscribers can send messages to external subscribers, and even add them to their private distribution lists during the transition.

However, once external subscribers are converted into regular Cisco Unity subscribers, they are automatically removed from all private lists without notifying private list owners. When this occurs, subscribers may continue to send messages to their private lists without realizing that some of their intended recipients no longer receive them.

When convenient and practical, Cisco Unity Administrators should notify subscribers when external subscribers are converted to regular subscribers, notifying subscribers that they should re-add the newly migrated subscribers to existing private lists, as applicable. During the migration phase, you may also want to consider preventing subscribers from adding subscribers to their private lists in the Cisco Unity Assistant, and asking them not to use the Cisco Unity phone menus to do so—at least until the migration process is complete.

Use the following "To Prevent Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant" procedure to prevent all subscribers that are associated with the Cisco Unity server from adding individual subscribers to their private lists in the Cisco Unity Assistant. When the change has been made, when subscribers add members to their lists in the Cisco Unity Assistant, the Find Names dialog box does not display the Subscribers tab. (Subscribers can continue to add distribution lists to their lists from the Distribution Lists tab.)


Note This procedure does not prevent subscribers from using the Cisco Unity phone menus to add regular and external subscribers to their private lists, nor does it prevent subscribers from addressing messages to regular and external subscribers.


To Prevent Subscribers From Adding Individual Subscribers to Private Lists in the Cisco Unity Assistant


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 Assistant—Do Not Allow Subscribers to Add Subscribers to Private Lists.

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

Step 5 When prompted, click OK.

Step 6 Click Exit.

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


Migrating Subscribers from Another Voice Messaging System to Cisco Unity

If you are using AMIS to migrate from another voice messaging system to Cisco Unity, there are several tools that you can use to create Cisco Unity subscribers from AMIS subscriber information.

See the following sections for more information:

Migrating Subscribers in Bulk

Migrating Subscribers One at a Time

Private List Considerations for Migrating Subscribers

Migrating Subscribers in Bulk

Following are the general steps for migrating AMIS subscribers to Cisco Unity subscribers in bulk. See the Help files of each of the tools for more information. (Click the Tools Depot icon on the Cisco Unity server, and click the applicable tool in the left pane to view the Help file.)

1. As a best practice, back up the Cisco Unity server before proceeding.

2. If the voice names of the subscribers on the remote system were recorded in a standard format that can be played on the Cisco Unity server (such as G.711 or G.729a), copy the WAV files to the Cisco Unity server. The Cisco Unity Bulk Import wizard will import the voice names.

3. Run Subscriber Information Dump from Tools Depot, and output the AMIS subscriber information to a CSV file.

4. Modify the output CSV file as needed so that you can use it as the input file when you create Cisco Unity subscribers by using the Cisco Unity Bulk Import wizard.

5. Run Global Subscriber Manager from Tools Depot to delete the AMIS delivery locations and associated AMIS subscribers and underlying contacts.

6. If the former AMIS subscribers do not already have Active Directory accounts, create the accounts. In addition, if the former AMIS subscribers did not use Exchange for email, create Exchange mailboxes for them. Alternatively, you can let the Cisco Unity Bulk Import wizard create the accounts and mailboxes.

7. Run the Cisco Unity Bulk Import wizard by using the input file that you prepared in Step 4.

Migrating Subscribers One at a Time

If you have set up AMIS subscriber accounts for the subscribers on another voice messaging system, and if they have existing Exchange mailboxes, you may want to use the Migrate Subscriber Data utility when the time comes to migrate them to Cisco Unity. The Migrate Subscriber Data utility creates a Cisco Unity subscriber account by combining the Cisco Unity-specific data from an existing AMIS subscriber account (such as the voice name) with an existing mail user. The utility then deletes the AMIS subscriber account and the associated Active Directory contact.

The Migrate Subscriber Data utility is available in Tools Depot on the Cisco Unity server. See the Help file that comes with the utility for more information.

Private List Considerations for Migrating Subscribers

When you migrate AMIS subscribers, consider notifying Cisco Unity subscribers of these potential effects on private distribution list membership:

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

When an AMIS subscriber becomes a regular subscriber, the AMIS subscriber is removed from all private lists.

Considerations for Networked Cisco Unity Servers

In organizations with multiple Cisco Unity servers networked together, when subscribers address messages to an AMIS delivery location (by using blind addressing) or to an AMIS subscriber, the AMIS transmission originates from the Cisco Unity server on which the AMIS delivery location was created. (Note that AMIS subscribers are always created on the same Cisco Unity server as their associated AMIS delivery locations.)

When subscribers address a message to someone on the remote voice messaging system, the Voice Connector delivers the message to the UAmis mailbox that is associated with the Cisco Unity server on which the addressed AMIS delivery location was created. The AMIS schedule and the AMIS delivery options on the pertinent Cisco Unity server are applied.

Only one Cisco Unity server in the network needs to be licensed and set up for AMIS. If allowed by the primary location addressing options, all subscribers, no matter which Cisco Unity server they are associated with, can send messages to an AMIS delivery location or to an AMIS subscriber. The Cisco Unity server that is configured for AMIS acts as the AMIS "bridgehead" server for the other Cisco Unity servers in the network. For example, in Figure 5-1, there are three Cisco Unity servers in the network, but Unity 2 is the only server licensed and configured for AMIS. Unity 2 places and receives all of the AMIS calls. Thus, no matter which Cisco Unity server a subscriber is associated with, when the subscriber sends a message to someone on another voice messaging system, the message is routed to the UAmis mailbox that is associated with Unity 2. This mailbox is homed on the Exchange server that was selected in the Message Store Configuration wizard during the setup of Unity 2.

Figure 5-1 AMIS Bridgehead Configuration

Design Considerations

Because AMIS calls are placed and answered on the Cisco Unity server on which the AMIS delivery locations were created, you can configure your Cisco Unity servers as needed to handle AMIS traffic.

You can set up a bridgehead topology by designating one Cisco Unity server in the network to handle sending and receiving AMIS calls. See Figure 5-1.

Recall that the dialout for an outbound AMIS message originates from the Cisco Unity server on which an AMIS delivery location was created. If the AMIS traffic is too heavy for one Cisco Unity server to handle, you can balance the load by setting up multiple AMIS bridgehead servers. In this case, you need to determine which AMIS delivery locations and AMIS subscribers to create on each of the Cisco Unity servers, and keep a record of the mapping.

For example, assume that there are two AMIS bridgehead servers, Bridgehead A and Bridgehead B, and there are four AMIS delivery locations called London, Paris, Goose Creek, and Monks Corner. You anticipate that message delivery to the London and Paris delivery locations will be heavy, and that message delivery to the Goose Creek and Monks Corner delivery locations will not be as heavy. You can balance the load by creating the London and Goose Creek delivery locations on Bridgehead A, and create the Paris and Monks Corner delivery locations on Bridgehead B. This ensures that the AMIS traffic for the two heavy AMIS locations is split up between the two bridgehead servers, rather than one trying to deliver all of the messages by itself.

For organizations with Cisco Unity servers deployed in different areas around the country or the world, it may be possible to set up a least-cost-routing topology to minimize or eliminate long distance phone charges related to AMIS transmissions.

For example, assume there are Cisco Unity servers in Chicago and in New York, and that there is also another voice messaging system in New York to which subscribers in Chicago want to send messages. To avoid long distance phone charges when subscribers in Chicago send messages to individuals who use the remote voice messaging system in New York, you create an AMIS delivery location, and optionally, AMIS subscribers, on the New York Cisco Unity server. When subscribers who are associated with the Chicago Cisco Unity server address messages to the AMIS subscribers in New York, the messages are first delivered by Exchange and the Voice Connector to the UAmis mailbox that is associated with the New York Cisco Unity server. Then the New York Cisco Unity server dials a local number to deliver the message to the remote voice messaging system, thus avoiding long distance phone charges.

AMIS Networking Maintenance in Cisco Unity 8.x

This section provides information on various tasks that you may need to do in order to maintain your AMIS Networking configuration. See the following sections for details:

Monitoring AMIS Message Traffic

Moving the UAmis Mailbox

Monitoring AMIS Message Traffic

Cisco Unity monitors AMIS transmissions and the UAmis mailbox, and logs error events to the Windows Application Event log. Outgoing messages that cannot be delivered are returned to the sender, or to the Unaddressed Messages public distribution list if Cisco Unity cannot determine who the sender is.

For detailed information about the touchtones that are transmitted during an AMIS call, see the AMIS Analog Networking Definitions white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html. To see the DTMFs that are transmitted during an AMIS call, use the Cisco Unity Diagnostic tool to enable the micro trace 28 AMIS Frames in the Conv AMIS section. You can also use the Port Status Monitor, available in the Switch Integration Tools section of Tools Depot, to observe call progress, and the Port Usage Analyzer, available in the Reporting Tools section of Tools Depot, to monitor port usage.

Cisco Unity also provides reports on AMIS message traffic. For more information, see the "AMIS Out Traffic Report" and the "AMIS In Traffic Report" sections in the "Reports" chapter of the Maintenance Guide for Cisco Unity. (The Maintenance Guide for Cisco Unity is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.)

Although Cisco Unity monitors the UAmis mailbox, you may want to check the UAmis mailbox periodically to confirm that messages are being sent in a timely manner. For example, if there are still messages to be sent when the AMIS schedule becomes inactive, they remain in the UAmis mailbox until the AMIS schedule becomes active again. If messages are often left in the UAmis mailbox, you may need to adjust the AMIS schedule or designate more voice ports for outgoing AMIS calls. Access to the UAmis mailbox is also needed when troubleshooting outbound message delivery problems.

In order to use Microsoft Outlook to access the UAmis mailbox, do the following "To Add the UAmis Mailbox to a User Profile" procedure to add the UAmis mailbox to the user profile of someone with administrative rights to Exchange. Refer to the Outlook documentation for more information.

To Add the UAmis Mailbox to a User Profile


Step 1 Start Microsoft Outlook.

Step 2 On the Tools menu, click Services.

Step 3 On the Services tab, in the field The Following Information Services Are Set Up in This Profile, click Microsoft Exchange Server.

Step 4 Click Properties.

Step 5 On the Advanced tab, click Add.

Step 6 In the Add Mailbox box, enter UAmis.

Step 7 Click OK three times to dismiss the dialog boxes.


Moving the UAmis Mailbox

For information on moving the UAmis mailbox, see the "UAmis Mailbox" section in the "Cisco Unity Data and Log Files" chapter of the Maintenance Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.)

Troubleshooting AMIS Networking in Cisco Unity 8.x

For information on troubleshooting problems with AMIS messages, see the following sections in the Troubleshooting Guide for Cisco Unity Release 8.x, at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/8x/troubleshooting/guide/8xcutsgx.html.

In the "Diagnostic Trace Utilities and Logs in Cisco Unity 8.x" chapter:

"AMIS Diagnostic Traces"

"Cisco Unity Voice Connector Logs"

In the "Troubleshooting Networking in Cisco Unity 8.x" chapter:

"AMIS Networking in Cisco Unity 8.x"

For detailed information about the touchtones that are transmitted during an AMIS call, see the AMIS Analog Networking Definitions white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.

You can use the Port Status Monitor, available in the Switch Integration Tools section of Tools Depot, to observe call progress, and the Port Usage Analyzer, available in the Reporting Tools section of Tools Depot, to monitor port usage.

Notable Behavior of AMIS Networking in Cisco Unity 8.x

This section describes notable behavior of AMIS Networking. See the following sections for more information:

Inbound Messages Are Delivered Only to Primary Extensions

Inbound Search Scope

Running the Voice Connector Setup Program in Another Language

Inbound Messages Are Delivered Only to Primary Extensions

When addressing a message to a Cisco Unity subscriber, users on the remote voice messaging system must use the primary extension of the Cisco Unity subscriber; alternate extensions are not supported. Senders will receive an NDR if they address a message with the alternate extension of a Cisco Unity subscriber.

Note also that Cisco Unity does not accept messages from a remote voice mail system that are sent to Cisco Unity public distribution lists, call handlers, and interview handlers. Cisco Unity accepts messages from a remote voice mail system only when they are sent to a subscriber primary extension.

When designing the numbering plan for Cisco Unity subscribers, as a best practice, configure the primary extension of all Cisco Unity subscribers with the extension that will be used for addressing from the remote voice mail system. Configure all other required extensions as alternate extensions, as all other functionality in Cisco Unity can use alternate extensions.

Inbound Search Scope

In installations with multiple Cisco Unity servers networked together, the search scope for a matching subscriber extension for inbound messages that are sent from another AMIS-compliant voice messaging system is controlled by the primary location addressing options in the Cisco Unity Administrator. The search scope for inbound AMIS messages can be set to the local Cisco Unity server, to the dialing domain that the local Cisco Unity server is a member of, or to the entire global directory. Note that only subscriber extensions are searched. Incoming AMIS messages cannot be delivered to distribution lists.

Running the Voice Connector Setup Program in Another Language

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, do the following "To Run the Voice Connector Setup Program in Another Language" procedure.


Caution Installing the Voice Connector on an Exchange 2007 server is not supported.

To Run the Voice Connector Setup Program in Another Language


Step 1 From the Cisco Unity installation DVD or CD 1, copy the entire VoiceConnector-Ex2000 to your hard disk.

Step 2 In this local directory, browse to the LocalizedFiles\ENU directory.

Step 3 Rename the CiscoUnity_VoiceConnector.dll and SetupRes.dll files. (For example, rename the files CiscoUnity_VoiceConnector_ENU.dll and SetupRes_ENU.dll.)

Step 4 Copy the files CiscoUnity_VoiceConnector.dll and SetupRes.dll from the LocalizedFiles\<XXX> directory (where <XXX> is your language of choice) to the Localized\ENU directory.

Step 5 Run Install.exe from the VoiceConnector-Ex2000 directory on your hard disk. The installation program should be presented in the language you chose.


Note Only the installation program will be in this language; currently, the Event Log messages, logging, properties, and configuration settings are not localized.