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

Networking in Cisco Unity 8.x

Table Of Contents

Networking in Cisco Unity 8.x

Networking Options in Cisco Unity 8.x

Message Addressing Options in Cisco Unity 8.x

Locations and External Subscribers in Cisco Unity 8.x

Voice Connector in Cisco Unity 8.x

Interoperability Gateway for Microsoft Exchange in Cisco Unity 8.x

Active Directory Schema Extensions in Cisco Unity 8.x

Comparison of AMIS, Bridge, and VPIM Networking in Cisco Unity 8.x

Road Map to the Networking Documentation for Cisco Unity 8.x: Where to Go from Here


Networking in Cisco Unity 8.x


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

Networking Options in Cisco Unity 8.x

Message Addressing Options in Cisco Unity 8.x

Locations and External Subscribers in Cisco Unity 8.x

Networking Options in Cisco Unity 8.x

The main goal of networking in Cisco Unity is to deliver messages from a Cisco Unity server to a target, and to deliver messages from the target to Cisco 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. That is, the Exchange partner servers must be in the same Active Directory forest. Message routing is done by Exchange.

Internet Subscribers

Allows messaging with individuals over the Internet or any TCP/IP network by using SMTP. The recipient receives the message as an email 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 email address that you specify when creating the Internet subscriber account.

Trusted Internet Subscribers

Trusted Internet subscribers are Internet subscribers that are trusted with decrypted secure messages. Trusted Internet subscribers must be associated with a Trusted Internet Location. Secure messages to Trusted Internet subscribers are decrypted by the Interoperability Gateway for Microsoft Exchange or the Cisco Unity Voice Connector for Microsoft Exchange before they are sent by the Exchange server. (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)

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 Mail (VPIM) protocol. VPIM allows different voice messaging systems to exchange voice, text, and fax messages over the Internet or any TCP/IP network. VPIM is based on SMTP and the Multi-Purpose Internet Mail Extension (MIME) protocol. VPIM Networking can be used for messaging between Cisco Unity servers that access different directories, between Cisco Unity with Exchange and Cisco Unity with Domino, between Cisco Unity and Cisco Unity Express, and between Cisco Unity and Cisco Unity Connection systems.

Cisco Unity Connection Networking

Allows messaging and directory synchronization with Cisco Unity Connection servers. A Cisco Unity server or Digital Network can be joined to a Connection site of one or more servers by designating a Cisco Unity site gateway and a Connection site gateway. Directory synchronization is done by the site gateways via HTTP or HTTPS. Message routing is handled by Exchange on the Cisco Unity side, with the Interoperability Gateway for Microsoft Exchange providing message formatting, audio transcoding and encryption or decryption, and so on.


Message Addressing Options in Cisco Unity 8.x

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

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

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

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. In addition, if you are migrating users from an existing voice messaging system to Cisco Unity in stages, you can add AMIS, Bridge, or VPIM connectivity to the mix. Figure 1-1 depicts a configuration that uses a mix of the various networking options.

Figure 1-1 Networking in Cisco Unity

Locations and External Subscribers in Cisco Unity 8.x

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 "Primary Location Settings in Cisco Unity 8.x" chapter for more information.

To set up AMIS, Bridge, or VPIM 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.


Note Trusted Internet Locations are a special type of delivery location. They do not contain information about other messaging servers, but rather serve as a delivery location for Trusted Internet subscribers that are trusted with decrypted secure messages. Based on the configuration settings of the Trusted Internet Location, messages are decrypted by the Interoperability Gateway or the Voice Connector before they are sent by Exchange over the Internet or any TCP/IP network via SMTP. (Messages to regular Internet subscribers are sent directly by the Exchange server and cannot be decrypted and therefore cannot be played by the recipient.)


Optionally, you can also create "external" subscribers (that is, AMIS, Bridge, and/or VPIM subscribers). The messages for external subscribers are stored externally to the Cisco Unity voice message store. When creating an external subscriber, you specify a delivery location that the external subscriber is associated with so that Cisco Unity has the information it needs to send messages to them.

To set up Cisco Unity Connection Networking, you create an intersite link between the Cisco Unity site gateway and the Connection site gateway. When initial synchronization completes between the site gateways, the Cisco Unity site gateway automatically creates Connection Networking delivery locations for each server in the Connection site. Likewise, the Cisco Unity site gateway automatically creates Connection Networking subscribers to represent users homed on servers in the Connection site.

Voice Connector in Cisco Unity 8.x

Revised October 15, 2010

The Cisco Unity Voice Connector for Microsoft Exchange is a Cisco Unity networking component that enables messaging between Cisco Unity servers and other voice messaging systems.

The Voice Connector for Exchange can be used when your network consists of Exchange 2003 servers, a mixture of Exchange 2000 and Exchange 2003 servers, or a mixture of Exchange 2000 and/or Exchange 2003 with Exchange 2007 and/or Exchange 2010 servers.


Caution The Voice Connector for Exchange cannot be installed on an Exchange 2007 or later server.

The Voice Connector performs the following functions:

AMIS Networking—The Voice Connector routes voice messages to the applicable UAmis_<Servername> mailbox for outgoing analog delivery. Incoming AMIS voice messages received by the Cisco Unity AMIS bridgehead are routed to the Voice Connector for processing.

Bridge Networking—The Voice Connector performs the message conversion and address translation that allows Cisco Unity to exchange messages with the Bridge server.

VPIM Networking—The Voice Connector performs the message conversion and address translation that allows Cisco Unity to exchange messages with other Cisco Unity servers or other voice messaging systems by using the VPIM protocol. VPIM Networking also provides messaging between:

Cisco Unity servers that access separate directories

Cisco Unity with Domino systems and Cisco Unity with Exchange systems

Cisco Unity and Cisco Unity Express

Note that the Voice Connector is not needed with Digital Networking because the Cisco Unity servers access the same directory.

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


Note To access the software download page, you must be logged on to Cisco.com as a registered user.


Interoperability Gateway for Microsoft Exchange in Cisco Unity 8.x

Revised October 15, 2010

The Interoperability Gateway for Microsoft Exchange is a Cisco Unity networking component that enables messaging between Cisco Unity servers and other voice messaging systems.

The gateway can be installed on an Exchange 2010, Exchange 2007 or Exchange 2003 server to provide VPIM Networking, trusted Internet subscriber, or Cisco Unity Connection Networking functionality in all Exchange environments that are supported by Cisco Unity, including pure Exchange 2010, pure Exchange 2007 or any mixture of Exchange 2010, Exchange 2007, Exchange 2003, and Exchange 2000. However, if your deployment also includes AMIS or Bridge networking, you must use the Cisco Unity Voice Connector for Microsoft Exchange for those protocols, either along with or instead of the Interoperability Gateway. (The Voice Connector also supports VPIM networking and trusted Internet subscribers, but installing the Voice Connector on an Exchange 2010 or Exchange 2007 server is not supported.)

Table 1-2 shows which messaging gateways you can use for each networking feature in a particular Exchange environment. Note that if you deploy more than one networking feature, you may need both messaging gateways, and you may need to retain a mixed Exchange environment to install both.

Table 1-2 Supported Messaging Gateways for Networking Features in a Particular Exchange Environment

 
AMIS
Bridge
VPIM
Trusted Internet
Connection Networking
Exchange 2000 Only 1

Voice Connector

Voice Connector

Voice Connector

Voice Connector

Not Supported

Mixed Exchange 2003 and Exchange 2000

Voice Connector

Voice Connector

Interoperability Gateway2

Voice Connector

Interoperability Gateway2

Voice Connector

Interoperability Gateway2

Exchange 2003 Only

Voice Connector

Voice Connector

Interoperability Gateway

Voice Connector

Interoperability Gateway

Voice Connector

Interoperability Gateway

Mixed Exchange 2010/ 2007 and Exchange 2000/2003

Voice Connector3

Voice Connector3

Interoperability Gateway2

Voice Connector3

Interoperability Gateway2

Voice Connector3

Interoperability Gateway2

Exchange 2010 Only

Not Supported

Not Supported

Interoperability Gateway

Interoperability Gateway

Interoperability Gateway

Exchange 2007 Only

Not Supported

Not Supported

Interoperability Gateway

Interoperability Gateway

Interoperability Gateway

1 If you are using Cisco Unity version 8.x and you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server.

2 The Interoperability Gateway cannot be installed on an Exchange 2000 server.

3 The Voice Connector cannot be installed on an Exchange 2010 or 2007 server.


For the purposes of load balancing or redundancy, you can install the Interoperability Gateway on multiple Exchange servers in the same organization. However, you can only install one instance of the gateway per Exchange server.

Active Directory Schema Extensions in Cisco Unity 8.x

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

Cisco Unity Connection Networking (uses the same schema extensions as VPIM Networking)

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

For detailed information about the data that is stored in the directory, see the following white papers: Cisco Unity Data and Active Directory (Cisco Unity 5.x and Later with Microsoft Exchange) and Active Directory Capacity Planning (Cisco Unity Version 5.x and Later with Microsoft Exchange). Both white papers are available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html).

Comparison of AMIS, Bridge, and VPIM Networking in Cisco Unity 8.x

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

Interoperability

General Connectivity Costs

Supported Voice Gateways

International Availability

Blind Addressing

Addressing by Name or by Extension

Spoken Name Confirmation

Audio Formats Supported

Delivery Receipt/Read Receipt

Directory Information Sharing

Distribution Lists

Mailbox ID Translation

Fax Messaging

Message Transport Time Considerations

Private Messages

Secure Messages

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

Urgent Messages

System Broadcast Messages

Table 1-3 Interoperability 

AMIS
Bridge
VPIM

For the most up-to-date list of supported voice messaging systems, see the applicable Supported Hardware and Software, and Support Policies for Cisco Unity, at http://www.cisco.com/en/US/
products/sw/voicesw/ps2237/
prod_installation_guides_list.html
.

For the most up-to-date list of supported voice messaging systems, see the applicable System Requirements, and Supported Hardware and Software for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/
sw/voicesw/ps2237/prod_installation_
guides_list.html
.

For the most up-to-date list of supported voice messaging systems, see the applicable Supported Hardware and Software, and Support Policies for Cisco Unity, at http://www.cisco.com/en/US/products/
sw/voicesw/ps2237/prod_installation_
guides_list.html
.


Table 1-4 General Connectivity Costs1  

AMIS
Bridge
VPIM

License for the Cisco Unity server that functions as an AMIS bridgehead.

Ports on the Cisco Unity server. Connectivity can be made through supported voice gateways. (See Table 1-5.)

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.

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-5 Supported Voice Gateways 

AMIS
Bridge
VPIM

For the most up-to-date list of supported voice gateways, see the applicable Supported Hardware and Software, and Support Policies for Cisco Unity, at http://www.cisco.com/en/US/
products/sw/voicesw/ps2237/prod_
installation_guides_list.html
.

For the most up-to-date list of supported voice gateways, see the applicable System Requirements, and Supported Hardware and Software for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/
sw/voicesw/ps2237/prod_installation_
guides_list.html
.

N/A.


Table 1-6 International Availability 

AMIS
Bridge
VPIM

All countries in which Cisco Unity is sold.

For a list of countries for which there is a voice-fax card approved for use, see the "Supported Voice-Fax Cards" section in the System Requirements, and Supported Hardware and Software for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/
sw/voicesw/ps2237/prod_installation_
guides_list.html
.

Some deployments may service users in countries that are not on the "Supported Voice-Fax Cards for the Cisco Unity Bridge Server" list, but only when the Bridge server itself is located in one of the countries listed.

The Bridge server is supported only when using the English-language version of Windows. The locale must be set to English (United States), and the language settings must be set only to Western Europe and United States. (Choosing additional language settings is not supported.) The Bridge software is not localized in any language other than English.

All countries in which Cisco Unity is sold.


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


Table 1-8 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-9 Spoken Name Confirmation 

AMIS
Bridge
VPIM

Available when a recorded voice name exists for the AMIS subscriber.

Voice names for AMIS subscribers must be recorded individually in the Cisco Unity Administrator.

Voice names for AMIS subscribers can be imported by using the Cisco Unity Bulk Import utility.

Available when a recorded voice name exists for the Bridge subscriber.

Voice names for Bridge subscribers can be recorded individually in the Cisco Unity Administrator. However, because the Bridge supports directory information sharing, the text and recorded voice names of Octel subscribers are retrieved on a usage basis, and Bridge subscribers can be automatically created in the Cisco Unity directory with the retrieved text and voice names. Similarly, the text and voice names of Cisco Unity subscribers are retrieved by the Octel servers on a usage basis, and directory entries are automatically created on the Octel servers with the retrieved text and voice names.

Voice names for Bridge subscribers can be imported by using the Cisco Unity Bulk Import utility.

Cisco Unity includes support for the automatic creation of VPIM subscribers. Therefore, the text and recorded voice names of senders on remote VPIM systems can be derived from incoming VPIM messages, and VPIM subscribers can be automatically created in the Cisco Unity directory with the derived text and voice names.

Available when a recorded voice name exists for the VPIM subscriber.

Voice names for VPIM subscribers can be recorded individually in the Cisco Unity Administrator.

Voice names for VPIM subscribers can be imported by using the Cisco Unity Bulk Import utility.


Table 1-10 Audio Formats Supported1  

AMIS
Bridge
VPIM

The AMIS protocol is not dependent on audio format.

Any codec supported for use with Cisco Unity can be used.

Octel Analog Networking is not dependent on audio format.

The Cisco Unity servers must use either the G.711 or the G.729a codec in order to communicate with the Cisco Unity Bridge servers.

The VPIM Version 3 Specification includes support for the following audio formats: G.711, G.726, and GSM 6.10.

Any codec supported for use with Cisco Unity can be used.

Outbound VPIM messages can be converted to G.726 or sent in the format in which they were recorded.

Incoming VPIM messages can be converted to G.711, G.729a, or GSM 6.10, or remain in the format in which they were sent.

1 For a list of audio formats supported by Cisco Unity, see the Audio Codecs and Cisco Unity white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.


Table 1-11 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 with Voice Connector versions 14.0(1) and earlier, both are treated as requests for delivery receipts.


Table 1-12 Directory Information Sharing 

AMIS
Bridge
VPIM

The AMIS protocol does not provide any mechanism for sharing or synchronizing directory information.

If the remote AMIS system is configured to send the recorded voice name in messages, Cisco Unity will play it as part of the message.

Avaya Octel analog networking includes the NameNet feature, which provides a mechanism to propagate text and voice names among nodes on the Octel analog network, based on message activity or by administrator request.

The Cisco Unity Bridge participates in NameNet. The Bridge retrieves Octel subscriber names and voice names from other Octel nodes, and stores the data in a directory on the Bridge server. The Bridge also maintains a directory of Cisco Unity subscribers, and sends Cisco Unity names and voice names to the Octel nodes upon request.

The Bridge synchronizes Octel subscriber information with Cisco Unity. By default, Cisco Unity allows the automatic creation, modification, and deletion of Bridge subscribers based on the information sent by the Bridge.

Cisco Unity synchronizes Cisco Unity subscriber information with the Bridge.

If the remote Octel system is configured to send the recorded voice name in messages, Cisco Unity will play it as part of the message.

Although the VPIM specification does not define a mechanism for directory information sharing or synchronization, some VPIM-compliant voice mail systems may process vCards or header information in VPIM messages and update their directories based on message activity.

Cisco Unity can be configured to include the recorded voice name and/or vCard of the sender in messages to the remote VPIM systems.

The delivery location settings for a remote voice messaging system can be configured to allow automatic creation, modification, and deletion of VPIM subscribers for that location, based on vCard or header information received in incoming voice messages from that location.

If the remote VPIM system is configured to send the recorded voice name and/or vCard in messages, Cisco Unity will make them available as part of the message.


Table 1-13 Distribution Lists 

AMIS
Bridge
VPIM

The AMIS protocol does not support delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco Unity to the AMIS system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco Unity can be addressed to a Cisco Unity public or private distribution list that includes AMIS subscribers. Private distribution lists can include blind addresses.

Incoming AMIS messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco Unity public distribution lists. (However, you may be able to set up a Cisco Unity subscriber account whose sole purpose is to forward messages to a Cisco Unity public distribution list. See your Microsoft Exchange and Outlook documentation for more information.)

Octel Analog Networking does not support delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco Unity to the Octel system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco Unity can be addressed to a Cisco Unity public or private distribution list that includes Bridge subscribers. Private distribution lists can include blind addresses.

Incoming Bridge messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco Unity public distribution lists. (However, you may be able to set up a Cisco Unity subscriber account whose sole purpose is to forward messages to a Cisco Unity public distribution list. See your Microsoft Exchange and Outlook documentation for more information.)

The VPIM specification does not include support for message delivery to a distribution list on the recipient voice messaging system.

Outbound messages from Cisco Unity to the VPIM system must be addressed to a mailbox ID on the remote system. (However, an administrator on the remote system may be able to configure a mailbox ID to forward messages to a distribution list.)

Outbound messages from Cisco Unity can be addressed to a Cisco Unity public or private distribution list that includes VPIM subscribers. Private distribution lists can include blind addresses.

Incoming VPIM messages are delivered to subscriber mailboxes only, and cannot be delivered to Cisco Unity public distribution lists. (However, you may be able to set up a Cisco Unity subscriber account whose sole purpose is to forward messages to a Cisco Unity public distribution list. See your Microsoft Exchange and Outlook documentation for more information.)


Table 1-14 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 that are associated with the Cisco Unity sender and remote recipient on messages that are 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.


Table 1-15 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-16 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-17 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-18 Secure Messages 

AMIS
Bridge
VPIM

Incoming messages cannot be encrypted before being delivered to the local recipient.

With default settings: Outgoing secure messages are undeliverable and will generate an NDR.

When configured: Outgoing secure messages are decrypted by the Voice Connector and the message is no longer secure.

With default settings: Incoming messages will not be encrypted before being delivered to the local recipient. Outgoing secure messages are undeliverable and will generate an NDR.

When configured: Incoming messages are encrypted before being delivered to the local recipient. Outgoing secure messages are decrypted by the Voice Connector and the message is no longer secure.

With default settings: Incoming messages will not be encrypted before being delivered to the local recipient. Outgoing secure messages are undeliverable and will generate an NDR.

When configured: Incoming messages are encrypted before being delivered to the local recipient. Outgoing secure messages are decrypted by the Voice Connector and can be re-encrypted if the receiving server is Cisco Unity with Exchange and if secure messaging is configured. During transport outside the Cisco Unity system, messages are not encrypted.


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

AMIS
Bridge
VPIM

Supported.

Limited to the voice mail port availability on the AMIS bridgehead server.

Ports available to place outgoing AMIS calls can be configured in the Cisco Unity Administrator (but not per AMIS destination).

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


Table 1-21 System Broadcast Messages 

AMIS
Bridge
VPIM

Not available.

Regular voice messages can be sent to a bulletin mailbox on an Octel Aria system or to a System Distribution List (SDL) on an Octel Serenade system. Similarly, system broadcast messages can be sent to a bulletin mailbox or SDL. Both types of message will be transmitted in the same way by the Cisco Unity Bridge and treated identically when delivered to the bulletin mailbox or SDL.

System broadcast messages can be sent between Cisco Unity with Exchange servers that do not share the same directory, or between Cisco Unity with Exchange and Cisco Unity Express servers, using VPIM. Other types of remote messaging systems will treat the system broadcast message in the same way they would treat a regular voice message.


Road Map to the Networking Documentation for Cisco Unity 8.x: 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 in Cisco Unity 8.x" chapter. Start with that chapter even if you will also be using other networking options.

If you plan to use AMIS to communicate with another voice messaging system, see the "AMIS Networking in Cisco Unity 8.x" chapter.

If you plan to use VPIM to communicate with another voice messaging system, see the "VPIM Networking in Cisco Unity 8.x" chapter.

If you plan to use the Bridge to communicate with Octel systems on an Octel analog network, see the Networking Guide for Cisco Unity Bridge at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.

If you plan to use Cisco Unity Connection Networking, see the Networking Guide for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/networking/guide/8xcucnetx.html.

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