5-29
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 5 AMIS Networking
AMIS Concepts and Definitions
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” section on page 9-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 on page 5-38 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 on page 5-30 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 on
page 5-31 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.
E-mail messages cannot be sent to AMIS recipients even though ViewMail allows subscribers to
address them. Instead of being delivered, e-mail 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.