5-31
Networking Guide for Cisco Unity Release 5.x (With Microsoft Exchange)
OL-13844-01
Chapter 5 AMIS Networking
AMIS Concepts and Definitions
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 on page 5-38 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 location(s),
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 on page 5-38 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.