Table Of Contents

Networking in Cisco Unity

Overview: Networking in Cisco Unity

New and Changed Functionality

AMIS Restriction Table Selection Is Automatically Replicated Between Servers Set Up for Failover

Cross-Server Live Reply to Subscribers on Networked Cisco Unity Servers

Cross-Server Log On for Multiple Cisco Unity Servers

Cross-Server Transfers from the Automated Attendant or a Directory Handler

Early Notice of Removal of SMTP Networking Option in Cisco Unity 4.0(5)

Identified Subscriber Messaging Extended to Include AMIS, Bridge, and VPIM Subscribers

Live Reply to AMIS, Bridge, and VPIM Subscribers

No Codec Conversion on Outbound VPIM Messages

Nondelivery Receipt Improvements

Networking Options

Message Addressing Options

Locations and External Subscribers

Voice Connector

Voice Connector Versions

Active Directory Schema Extensions

Comparison of AMIS, Bridge, and VPIM Networking

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

Networking in Cisco Unity

---

Overview: Networking in Cisco Unity

In Cisco Unity, "networking" is the general term for messaging between Cisco Unity servers, and between Cisco Unity and other voice messaging systems. The term networking has a broad definition and encompasses the following ideas:

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

–Subscribers associated with another Cisco Unity server.

–Individuals with access to a computer connected to the Internet.

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

•Unidentified callers can find any subscriber in the phone directory and leave a voice message. Depending on the phone system and network configuration, unidentified callers who reach the Cisco Unity automated attendant or directory assistance can be transferred to any subscriber phone, even to the phone of a subscriber who is not associated with the local server.

See the following sections in this chapter for more information:

•New and Changed Functionality

•Networking Options

•Locations and External Subscribers

•Voice Connector

•Active Directory Schema Extensions

•Comparison of AMIS, Bridge, and VPIM Networking

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

New and Changed Functionality

This section provides information about new and changed functionality related to the networking options in Cisco Unity 4.0(4). For information about new and changed functionality for all of Cisco Unity, refer to the Release Notes for Cisco Unity Release 4.0(4), available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/relnote/cu404rn.htm.

AMIS Restriction Table Selection Is Automatically Replicated Between Servers Set Up for Failover

On a 4.0(4) or later system set up for Cisco Unity failover, when you change the restriction table to be used for outgoing AMIS calls, the table selection on the primary server will be replicated to the secondary server. In previous releases of Cisco Unity, this setting was not replicated, and you had to manually select the same AMIS restriction table on the secondary server. The setting is now stored in the SQL server UnityDb database in the Configuration table instead of the registry. You specify the AMIS restriction table in the Cisco Unity Administrator on the Network > AMIS Options page.

Note, however, that the settings on the restriction table itself replicate in all Cisco Unity versions.

Cross-Server Live Reply to Subscribers on Networked Cisco Unity Servers

Live reply allows subscribers who listen to their messages by phone to respond to a message from another subscriber by calling that subscriber. In Cisco Unity 4.0(4), the live reply functionality has been enhanced so that subscribers can live reply to messages from subscribers on other Cisco Unity servers in a dialing domain. To enable cross-server live reply, you configure settings on the new Dialing Domain Options page in the Cisco Unity Administrator, including entering the pilot numbers of other Cisco Unity servers in the dialing domain.

For more information, refer to the White Paper: Using Cross-Server Log On, Transfer, and Live Reply, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/crossbox.htm.

Cross-Server Log On for Multiple Cisco Unity Servers

The cross-server log on feature allows you to provide subscribers with one phone number that they can call to log on to Cisco Unity from outside your organization. To enable cross-server log on, you configure settings on the new Dialing Domain Options page in the Cisco Unity Administrator, including entering the pilot numbers of other Cisco Unity servers in the dialing domain. After cross-server log on is configured, all subscribers can call the pilot number for one Cisco Unity server, and be transferred to their home Cisco Unity server to log on.

For more information, refer to the White Paper: Using Cross-Server Log On, Transfer, and Live Reply, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/crossbox.htm.

Cross-Server Transfers from the Automated Attendant or a Directory Handler

The cross-server transfer feature allows for supervised transfers of calls from the automated attendant or a directory handler of one Cisco Unity server to a subscriber on another Cisco Unity server in the dialing domain. To enable cross-server transfers, you configure settings on the new Dialing Domain Options page in the Cisco Unity Administrator, including entering the pilot numbers of other Cisco Unity servers in the dialing domain. After cross-server transfers are enabled, calls from the automated attendant or a directory handler are first transferred to the Cisco Unity server on which the subscriber in homed. The home Cisco Unity then checks the call transfer settings of the called subscriber before transferring the call to the subscriber.

For more information, refer to the White Paper: Using Cross-Server Log On, Transfer, and Live Reply, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/crossbox.htm.

Early Notice of Removal of SMTP Networking Option in Cisco Unity 4.0(5)

Beginning with Cisco Unity 4.0(5), the SMTP Networking feature will be removed from the product. Customers who need to network Cisco Unity servers that access separate directories will instead use VPIM Networking. Both SMTP Networking and VPIM Networking use SMTP as the mechanism for exchanging messages, but the message format differs. SMTP Networking uses a proprietary message format, while the message format in VPIM Networking adheres to the VPIM industry standard. In addition, VPIM Networking provides some additional functionality that is not available in SMTP Networking, and by removing the redundant networking option, Cisco will be able to focus its resources on enhancements to VPIM Networking.

Customers who are currently using SMTP Networking and who plan to upgrade to 4.0(5) will have to migrate to VPIM Networking. To migrate from SMTP Networking to VPIM Networking before upgrading to 4.0(5), see the "Migrating from SMTP Networking to VPIM Networking" section on page 6-24.

Note that VPIM Networking is a licensed feature and is currently supported only with Microsoft Exchange 2000 and Exchange 2003.

In addition to VPIM Networking, customers will also still be able to set up Internet subscriber accounts for messaging with individuals who do not use Cisco Unity, but who have computers connected to the Internet.

Identified Subscriber Messaging Extended to Include AMIS, Bridge, and VPIM Subscribers

With identified subscriber messaging (ISM), Cisco Unity recognizes that a caller number is associated with a subscriber. By default, ISM is enabled for all Cisco Unity subscribers on the local system, and can be expanded to include all Cisco Unity subscribers throughout a dialing domain. In Cisco Unity 4.0(4), the ISM feature can be configured to include AMIS, Bridge, and VPIM subscribers. When a call to a Cisco Unity subscriber is forwarded to the subscriber greeting, Cisco Unity compares the calling number to the primary and alternate extensions of "regular" Cisco Unity subscribers and AMIS, Bridge, and VPIM subscribers. If a match is found among any of the subscriber types, Cisco Unity identifies the caller as 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 whose extension matched the caller ID information, and allows the called subscriber to record a reply.

Live Reply to AMIS, Bridge, and VPIM Subscribers

Live reply allows subscribers who listen to their messages by phone to respond to messages from other subscribers by calling them. In Cisco Unity 4.0(4), the live reply functionality has been enhanced so that Cisco Unity subscribers can live reply to messages from subscribers on other voice messaging systems who have corresponding AMIS, Bridge, or VPIM subscriber accounts in Cisco Unity. (Collectively, AMIS, Bridge, and VPIM subscribers are referred to as external subscribers.)

Note that a live reply to an external 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 external subscriber have accounts on the same Cisco Unity server. Live replies to external subscribers with accounts on other Cisco Unity servers do not use the cross-server live reply functionality that is used to live reply to Cisco Unity subscribers with accounts on other Cisco Unity servers.

No Codec Conversion on Outbound VPIM Messages

A new setting has been added to the VPIM delivery location page in the Cisco Unity Administrator that allows you to specify that outbound VPIM messages will not be converted by the Voice Connector to another audio format. (In previous versions of Cisco Unity, all outbound VPIM messages were automatically converted by the Voice Connector to the G.726 audio format, which is the format required by the VPIM Version 2 specification and supported by all VPIM-compliant voice messaging systems.) The new Do Not Convert Outgoing Message setting allows outbound messages to be sent in the same format in which they were recorded.

Typically, you choose this option only when you are using VPIM Networking for messaging between Cisco Unity servers in different Active Directory forests. When you are using VPIM Networking with another voice messaging system, consult the documentation for that system to determine which audio formats it supports for VPIM messages.

This functionality requires that you install the Cisco Unity Voice Connector for Exchange 2000 version 11.0(2). The Voice Connector 11.0(2) ships with Cisco Unity 4.0(4) and is available on the Cisco Unity Voice Connector for Exchange Software Download page, at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-voice-connector. See the "Upgrade Information" section for information on upgrading the Voice Connector.

Nondelivery Receipt Improvements

When voice messages that were sent by a Cisco Unity subscriber—via AMIS, VPIM, or the Cisco Unity Bridge—to someone who uses another voice messaging system are returned as undeliverable, the Voice Connector sets a predetermined reason code in the nondelivery receipts (NDRs). The reason code in the NDRs is interpreted by the Cisco Unity Inbox and the TUI to provide subscribers with information as to why the message delivery failed.

Note the following limitations:

•The reason code in the NDR is not interpreted by ViewMail, so subscribers who use ViewMail to read NDR messages are not provided with additional information.

•If the message-delivery failure occurs before the outbound message is processed by the Voice Connector, the additional information is not provided.

•If the receipt with the reason code passes through an Exchange Routing Group Connector, the reason code is stripped off, so the additional information is not available to subscribers. Refer to the release note enclosure for CSCed93440 for more information.

This functionality requires that you install the Cisco Unity Voice Connector for Exchange 2000 version 11.0(2). The Voice Connector 11.0(2) ships with Cisco Unity 4.0(4) and is available on the Cisco Unity Voice Connector for Exchange Software Download page, at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-voice-connector. See the "Upgrade Information" section for information on upgrading the Voice Connector.

Networking Options

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

Table 1-1 Networking Options 

Networking Option	Description
Digital Networking	Allows messaging among multiple Cisco Unity servers connected to a single, global directory. The message transport agent (MTA) is the message transport mechanism between servers. You use this option when the Cisco Unity servers access a shared voice mail directory. That is, the Exchange partner servers must be in the same Active Directory forest or the same Exchange 5.5 organization.
SMTP	Allows messaging among Cisco Unity servers that access separate voice mail directories. That is, the Exchange partner servers are in separate Active Directory forests or separate Exchange 5.5 organizations. Messages are sent over the Internet or any TCP/IP network by using the Simple Mail Transfer Protocol (SMTP). Subscriber accounts created for use with SMTP Networking are called Internet subscriber accounts. With SMTP Networking, you can set up Internet subscriber accounts on the local Cisco Unity server to represent Cisco Unity subscribers on a server in a separate directory, and vice versa. When a subscriber on the local server sends a message to a subscriber on the remote server, the recipient receives voice messages.
Internet Subscribers	Allows messaging with individuals over the Internet or any TCP/IP network by using SMTP. The recipient receives the message as an e-mail with a WAV attachment. Internet subscribers can have local extensions, recorded voice names, and greetings, and be listed in the directory, but they do not have mailboxes in the local Exchange network. Messages are addressed to Internet subscribers as they are to regular subscribers, but the messages are sent to the e-mail address that you specify when creating the Internet subscriber account.
AMIS	Allows messaging with other voice messaging systems that support the Audio Messaging Interchange Specification analog (AMIS-a) protocol. In essence, the sending voice messaging system calls the receiving voice messaging system, there is an exchange of DTMF tones as defined by the protocol, the sending system plays the message, and the receiving system records it.
Bridge	Allows messaging between Cisco Unity and an Octel system on an Octel analog network by using the Cisco Unity Bridge. The Cisco Unity Bridge acts as a networking gateway between Cisco Unity and the Octel system, and allows the systems to exchange voice and fax messages. Messaging between Cisco Unity and the Bridge is done over the Internet or any TCP/IP network by using SMTP. Messaging between the Octel servers and the Bridge is done by using the Octel analog networking protocol. The Bridge must be installed on a separate and dedicated platform.
VPIM	Allows messaging with other voice messaging systems that support the Voice Profile for Internet Messaging (VPIM) protocol. VPIM allows different voice messaging systems to exchange voice, text, and fax messages over the Internet or any TCP/IP network. VPIM is based on SMTP and the Multi-Purpose Internet Mail Extension (MIME) protocol.

Message Addressing Options

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

•Blind Addressing—With blind addressing, Cisco Unity has the information it needs to send messages to the remote voice messaging system, even though the recipient mailbox number, text name, and recorded name are not in the directory.

•"External" Subscribers—You create Internet, AMIS, Bridge, and/or VPIM subscribers on the local Cisco Unity server to correspond to subscribers on the remote voice messaging system. These external subscribers (also referred to as "proxy users") can have local extensions, recorded voice names, and greetings, and can be listed in the directory, but they do not have mailboxes in the local Exchange network. Messages are addressed to an external subscriber as they are to a regular subscriber, but the messages are sent to the applicable mailbox on the remote voice messaging system.

•A Combination—The various ways of sending and receiving messages, as detailed in Table 1-1, are not mutually exclusive. For example, if the Cisco Unity servers in your organization are set up to access a global directory (and thus can make use of the Digital Networking option), you can still add Internet subscriber accounts for contractors working at home, and also set up Cisco Unity so that subscribers can send and receive voice messages from a field sales office where the Cisco Unity server is connected to a separate network. In addition, if you are migrating users from an existing voice messaging system to Cisco Unity in stages, you can add AMIS connectivity to the mix, as Figure 1-1 depicts.

Figure 1-1 Networking in Cisco Unity

Locations and External Subscribers

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

For each networking option, you customize the settings for the primary location. Each Cisco Unity server has a default or primary location, which is created during installation and which cannot be deleted. The primary location contains information that identifies the Cisco Unity server to other messaging systems, which may or may not be Cisco Unity systems. See the "Overview: Primary Location Settings" section on page 7-1 for more information.

For all networking options except Digital Networking, you create delivery locations. A delivery location contains the network information that Cisco Unity needs to send messages to other messaging servers, which may or may not be Cisco Unity servers. You create a delivery location for each voice messaging server with which the local Cisco Unity server will communicate.

For all networking options except Digital Networking, you may need to create "external" subscribers (that is, Internet, AMIS, Bridge, and/or VPIM subscribers). The messages for external subscribers are stored externally to the Cisco Unity voice message store. When creating external subscribers, you supply addressing information so that Cisco Unity can send messages to them. For example, when creating an Internet subscriber, you supply the subscriber e-mail address; messages are sent to that e-mail address instead of to an Exchange mailbox on the local network.

Voice Connector

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

•Cisco Unity servers that access separate directories (this is referred to as SMTP Networking).

•Cisco Unity servers and other voice messaging systems.

There are two Voice Connectors:

•Voice Connector for Exchange 5.5—When your network consists only of Exchange 5.5 servers, use the Voice Connector for Exchange 5.5.

•Voice Connector for Exchange 2000—When your network consists only of Exchange 2000 or Exchange 2003 servers, or a mixture of Exchange 2000 or Exchange 2003 servers and Exchange 5.5 servers, use the Voice Connector for Exchange 2000.

---

Note The Voice Connector for Exchange 2000 can be installed on an Exchange 2003 server.

---

The Voice Connector performs the following functions:

•SMTP Networking—The Voice Connector allows Cisco Unity systems in separate directories to exchange messages. The Voice Connector preserves the Cisco Unity-specific attributes in the outgoing messages for SMTP transport. The Voice Connector on the receiving end interprets and restores the preserved attributes so that the receiving Cisco Unity system recognizes the message as a voice message from a remote Cisco Unity subscriber.

•AMIS Networking—The Voice Connector routes voice messages to the applicable UAmis_<Servername> mailbox for outgoing analog delivery, and routes incoming AMIS voice messages from the Cisco Unity AMIS bridgehead to the recipient mailbox.

•Bridge Networking—The Voice Connector performs the message conversion that allows Cisco Unity to exchange messages with the Bridge. The Voice Connector for Exchange 2000 is the only Voice Connector supported with this networking option.

•VPIM Networking—The Voice Connector performs the message conversion that allows Cisco Unity to exchange messages with other Cisco Unity servers or other voice messaging systems by using the VPIM protocol. The Voice Connector for Exchange 2000 is the only Voice Connector supported with this networking option.

•Digital Networking—The Voice Connector is not needed with Digital Networking because the Cisco Unity servers access the same directory.

The Voice Connector ships with Cisco Unity and is available on the Cisco Unity Voice Connector for Exchange Software Download page, at http://www.cisco.com/pcgi-bin/tablebuild.pl/unity-voice-connector.

Voice Connector Versions

Table 1-2 lists the Voice Connector versions and the Cisco Unity versions they are shipped with.

Table 1-2 Voice Connector and Cisco Unity Versions 

Voice Connector Version	Shipped with Cisco Unity Version
11.0(2)	4.0(4)
11.0(1)	4.0(3)
10.0(2)	4.0(2), 3.1(6)
10.0(1)	4.0(1)
Any other version number	2.4(6) through 3.1(5) The Voice Connector version number matches the version of Cisco Unity. For example, Voice Connector version 3.1(5) shipped with Cisco Unity version 3.1(5).

Active Directory Schema Extensions

When Cisco Unity is installed in a network that consists only of Exchange 2000 or Exchange 2003 servers, or in a mixed-mode environment with both Exchange 2000 or Exchange 2003 servers and Exchange 5.5 servers, a small subset of Cisco Unity data is stored in Active Directory. Therefore, before installing Cisco Unity, the Active Directory schema must be extended. In addition to the schema extensions required before installing Cisco Unity, the Active Directory schema must be extended before setting up the following:

•Bridge Networking

•VPIM Networking

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

For detailed information about the data that is stored in the directory, refer to the White Paper: Cisco Unity Data and the Directory (With Microsoft Exchange) (available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/datadir.htm), and the White Paper: Active Directory Capacity Planning, Cisco Unity Version 3.0(3) and Later (With Microsoft Exchange) (available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/adsizing.htm).

Comparison of AMIS, Bridge, and VPIM Networking

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

•Cisco Unity Version Support

•Interoperability

•General Connectivity Costs

•Supported Voice Gateways

•International Availability

•Blind Addressing

•Addressing by Name or by Extension

•Spoken Name Confirmation

•Audio Formats Supported

•Delivery Receipt/Read Receipt

•Directory Information Sharing

•Directory Synchronization

•Distribution Lists

•Exchange Version Support

•Mailbox ID Translation

•Fax Messaging

•Message Transport Time Considerations

•Private Messages

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

•Urgent Messages

Table 1-3 Cisco Unity Version Support

AMIS	Bridge	VPIM
Cisco Unity 3.1(2) and later.	Cisco Unity 3.1(3) and later.	Cisco Unity 4.0(1) and later.

Table 1-4 Interoperability

AMIS	Bridge	VPIM
For the most up-to-date list of supported voice messaging systems, refer to Cisco Unity System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/ univercd/cc/td/doc/product/ voice/c_unity/sysreq/ 40_sysrq.htm.	For the most up-to-date list of supported voice messaging systems, refer to Cisco Unity Bridge 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/ cc/td/doc/product/voice/c_unity/ bridge30/sysreq/30bsysrq.htm.	For the most up-to-date list of supported voice messaging systems, refer to Cisco Unity System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/univercd/ cc/td/doc/product/voice/c_unity/ sysreq/40_sysrq.htm.

Table 1-5 General Connectivity Costs¹

AMIS	Bridge	VPIM
•License for the Cisco Unity server that functions as an AMIS bridgehead. •Analog ports on the Cisco Unity server. Connectivity can be made in one of two ways: by using voice cards, or through supported voice gateways. (See Table 1-6.) •Analog lines for message delivery. •Applicable long distance charges if the Cisco Unity bridgehead server and the remote voice messaging system are physically located in different areas.	•License for the Bridge server. (Note that a license is no longer required on the Cisco Unity bridgehead server.) •A separate server for the Bridge software. Each server supports up to 24 ports. •Voice cards for the Bridge server. •Analog lines for message delivery between Bridge and Octel nodes. •Applicable long distance charges if the Bridge server and the Octel system are physically located in different areas. •SMTP network bandwidth for message delivery between the Bridge and Cisco Unity.	•License for the Cisco Unity server that functions as a VPIM bridgehead. •SMTP network bandwidth for message delivery.

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

Table 1-6 Supported Voice Gateways

AMIS	Bridge	VPIM
For the most up-to-date list of supported voice gateways, refer to Cisco Unity System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.	For the most up-to-date list of supported voice gateways, refer to Cisco Unity Bridge 3.0 System Requirements, and Supported Hardware and Software at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/sysreq/30bsysrq.htm	N/A.

Table 1-7 International Availability

AMIS	Bridge	VPIM
All countries in which Cisco Unity is sold.	For a list of countries for which there is a voice-fax card approved for use, refer to the "Supported Voice-Fax Cards" section in the Cisco Unity Bridge 3.0 System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/sysreq/30bsysrq.htm. Some deployments may service users in countries that are not on the "Supported Voice-Fax Cards for the Cisco Unity Bridge Server" list, but only when the Bridge server itself is located in one of the countries listed. The Bridge server is supported only when using the English-language version of Windows 2000 server. The locale must be set to English (United States), and the language settings must be set only to Western Europe and United States. (Choosing additional language settings is not supported.) The Bridge software is not localized in any language other than English.	All countries in which Cisco Unity is sold.

Table 1-8 Blind Addressing

AMIS	Bridge	VPIM
Available through the Cisco Unity Telephone User Interface (TUI), Cisco Unity ViewMail for Microsoft Outlook, and the Cisco Unity Inbox.	Available through the Cisco Unity TUI, ViewMail, and the Cisco Unity Inbox.	Available through the Cisco Unity TUI, ViewMail, and the Cisco Unity Inbox.

---

Note In version 3.1 and earlier, the Cisco Unity Inbox was known as the Visual Messaging Interface or VMI.

---

Table 1-9 Addressing by Name or by Extension

AMIS	Bridge	VPIM
Available through the Cisco Unity TUI, ViewMail, and the Cisco Unity Inbox when AMIS subscribers exist in the Cisco Unity directory.	Available through the Cisco Unity TUI, ViewMail, and the Cisco Unity Inbox when Bridge subscribers exist in the Cisco Unity directory.	Available through the Cisco Unity TUI, ViewMail, and the Cisco Unity Inbox when VPIM subscribers exist in the Cisco Unity directory.

Table 1-10 Spoken Name Confirmation

AMIS	Bridge	VPIM
•Available when a recorded voice name exists for the AMIS subscriber. •Voice names for AMIS subscribers must be recorded individually in the Cisco Unity Administrator.	•Available when a recorded voice name exists for the Bridge subscriber. •Voice names for Bridge subscribers may be recorded individually in the Cisco Unity Administrator. However, because the Bridge supports directory information sharing, the text and recorded voice names of Octel subscribers are retrieved on a usage basis, and Bridge subscribers are automatically created in the Cisco Unity directory with the retrieved text and voice names. Similarly, the text and voice names of Cisco Unity subscribers are retrieved by the Octel servers on a usage basis, and directory entries are automatically created on the Octel servers with the retrieved text and voice names.	•Available when a recorded voice name exists for the VPIM subscriber. •Voice names for VPIM subscribers must be recorded individually in the Cisco Unity Administrator.

Table 1-11 Audio Formats Supported¹

AMIS	Bridge	VPIM
•The AMIS protocol is not dependent on audio format. •Any codec supported for use with Cisco Unity may be used.	•Octel Analog Networking is not dependent on audio format. •The Cisco Unity servers must use either the G.711 or the G.729a codec in order to communicate with the Cisco Unity Bridge servers.	•The VPIM Version 3 Specification includes support for the following audio formats: G.711, G.726, and GSM 6.10. •Any codec supported for use with Cisco Unity may be used. •Outbound VPIM messages may be converted to G.726 or sent in the format in which they were recorded. •Incoming VPIM messages may be converted to G.711, G.729a, or GSM 6.10, or remain in the format in which they were sent.

1 Refer to the White Paper: Audio Codecs and Cisco Unity (All Versions), available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/whitpapr/codecs.htm for a list of the audio formats supported by Cisco Unity.

Table 1-12 Delivery Receipt/Read Receipt

AMIS	Bridge	VPIM
The AMIS protocol does not support this functionality. A request for a delivery or read receipt may be allowed on either Cisco Unity or the remote AMIS voice mail system when addressing, but the request will not result in a receipt.	Requests for a delivery or read receipt generated by Cisco Unity are returned from the Octel system as delivery receipts. The receipt is sent to the sender after the message is delivered to the Octel node, regardless of when the Octel system places the message in the subscriber mailbox or when the message is actually read.	Requests for a delivery or read receipt generated by either Cisco Unity or the remote VPIM system are honored, although both are treated as requests for delivery receipts.

Table 1-13 Directory Information Sharing

AMIS	Bridge	VPIM
•If the remote AMIS system is configured to send the recorded voice name in messages, Cisco Unity will play it as part of the message.	•With Octel analog networking, the Avaya Octel NameNet feature is supported. The Cisco Unity Bridge, paired with a Cisco Unity bridgehead server, participates in Octel analog networking, propagating text and voice names among nodes on the analog Octel network. •If the remote Octel system is configured to send the recorded voice name in messages, Cisco Unity will play it as part of the message.	•Cisco Unity can be configured to include the recorded voice name and/or vCard of the sender in messages to the remote VPIM systems. •If the remote VPIM system is configured to send the recorded voice name and/or vCard in messages, Cisco Unity will make them available as part of the message.

Table 1-14 Directory Synchronization

AMIS	Bridge	VPIM
•The AMIS protocol does not support this functionality.	•Cisco Unity synchronizes Cisco Unity subscriber information with the Bridge. •The Bridge synchronizes Octel subscriber information with Cisco Unity. •Subscriber information is retrieved by the Bridge from Octel, and vice versa, based on message activity, or due to administrator request. See Table 1-13.	•The VPIM specification does not support this functionality. •See Table 1-13.

Table 1-15 Distribution Lists

AMIS	Bridge	VPIM
•The AMIS protocol does not support delivery to a distribution list on the recipient voice messaging system. Each message from Cisco Unity to the AMIS system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.) •AMIS subscribers can be members of Cisco Unity public or private distribution lists.	•Octel Analog Networking does not support delivery to a distribution list on the recipient voice messaging system. Each message from Cisco Unity to the Octel system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.) •Bridge subscribers can be members of Cisco Unity public or private distribution lists.	•VPIM subscribers can be members of Cisco Unity public or private distribution lists.

Table 1-16 Exchange Version Support¹

AMIS	Bridge	VPIM
•Exchange 5.5. •Mixed Exchange 5.5/ Exchange 2000 or Exchange 2003 (Standard or Enterprise). •Exchange 2000 or Exchange 2003 (Standard or Enterprise).	•Mixed Exchange 5.5/ Exchange 2000 or Exchange 2003 (Standard or Enterprise). •Exchange 2000 or Exchange 2003 (Standard or Enterprise).	•Mixed Exchange 5.5/ Exchange 2000 or Exchange 2003 (Standard or Enterprise). •Exchange 2000 or Exchange 2003 (Standard or Enterprise).

1 In a mixed-mode environment with Exchange 5.5 and Exchange 2000 or Exchange 2003 servers, all Cisco Unity servers in the organization must be configured to communicate with an Exchange 2000 or an Exchange 2003 server.

Table 1-17 Mailbox ID Translation¹

AMIS	Bridge	VPIM
Not available.	Prefixes can be defined so that Cisco Unity subscribers can address messages to Octel subscribers by entering a network address consistent with phone network dial plans. All Cisco Unity subscribers are mapped to a configurable mailbox and serial number value for use when communicating with Octel servers. This allows any Cisco Unity subscriber to represent mailbox X at node serial number Y within the Octel network, independent of the Cisco Unity numbering plan.	Additional digits can be automatically added to the beginning of the mailbox numbers associated with the Cisco Unity sender and remote recipient on messages sent from Cisco Unity subscribers. The same digits can be removed from the beginning of the remote sender and Cisco Unity mailbox numbers for delivery to Cisco Unity subscribers.

1 Mailbox ID translation gives Cisco Unity users the ability to address a message to remote subscribers with the number of digits that the remote system expects to receive, without having to manually enter extra digits.

Table 1-18 Fax Messaging

AMIS	Bridge	VPIM
The AMIS protocol does not support this functionality.	Supported.	Supported; however, VPIM supports only the TIFF-F message format.

Table 1-19 Message Transport Time Considerations

AMIS	Bridge	VPIM
•Analog delivery of the message from the sending system to the receiving system is the most significant contribution to transport time. •The minimum analog delivery time can be calculated by multiplying the actual recording length of the message by the number of recipients of the message. The AMIS protocol requires a separate analog transmission of the message for each recipient. •For example, a five-minute message with 10 recipients would require a minimum of 50 minutes for the analog transmission.	•Analog delivery of the message from the sending system to the receiving system is the most significant contribution to transport time. •The minimum analog delivery time is the actual recording length of the message. •Octel Analog Networking allows a single analog transmission of a message addressed to multiple recipients, which the receiving node will deliver to all intended recipients. •For example, a five-minute message with 10 recipients would require a minimum of 5 minutes for the analog transmission.	•Exchange routing time and SMTP delivery time to a remote VPIM system are the only considerations. •For example, a five-minute message with 10 recipients would likely take less than one minute to transmit.

Table 1-20 Private Messages

AMIS	Bridge	VPIM
The AMIS protocol does not support this functionality. Messages marked private when they are sent are not marked private when the recipient retrieves them.	Supported. Messages marked private when they are sent are marked private when the recipient retrieves them.	Supported. Messages marked private when they are sent are marked private when the recipient retrieves them.

Table 1-21 Simultaneous Analog Sessions for Message Delivery to or from Remote Voice Mail Systems

AMIS	Bridge	VPIM
Supported. •Limited to Cisco Unity voice mail port availability. •Ports available to place outgoing AMIS calls can be configured in the Cisco Unity Administrator (but not per AMIS destination).	Supported. •Limited to Bridge server analog port availability. •Maximum number of ports to deliver simultaneously to any single node, and the threshold to initiate and disconnect additional calls, can be configured per Bridge server.	N/A.

Table 1-22 Urgent Messages

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

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

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

If you plan to set up blind addressing to other Cisco Unity servers that access separate directories, or to set up Internet subscriber accounts, see the "SMTP Networking" chapter.

If you plan to use AMIS to communicate with another voice messaging system, see the "AMIS Networking" chapter.

If you plan to use VPIM to communicate with another voice messaging system, see the "VPIM Networking"chapter.

If you plan to use the Bridge to communicate with Octel systems on an Octel analog network, refer to the Cisco Unity Bridge Networking Guide, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/bnet30/index.htm.

Regardless of which networking option you choose, you need to customize the settings for the primary location. See the "Primary Location Settings" chapter.

If you have an earlier version of AMIS or the Voice Connector installed, review the information in the "Upgrading and Uninstalling Networking Options" chapter.