Table Of Contents
Networking in Cisco Unity
Overview: Networking in Cisco Unity
New and Changed Functionality
Automatic VPIM Subscriber Directory Updates
Cisco Personal Communications Assistant (PCA): Customizable Search Scope for Finding and Checking Names
Enhanced Private Distribution List Management
Importing Subscribers with Recorded Names by Using the Cisco Unity Bulk Import Wizard
Live Reply to Subscribers on Networked Cisco Unity Servers via Release to Phone System Transfer
Private Secure Messaging
SMTP Networking Option Not Supported Beyond the Cisco Unity 4.0(x) Train
Networked System Broadcast Messaging
Population of the vCard "N Property" Field in VPIM Messages
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 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 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(5) and later. For information about new and changed functionality for all of Cisco Unity, see the Release Notes for Cisco Unity Release 4.0(5), at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
•Automatic VPIM Subscriber Directory Updates
•Cisco Personal Communications Assistant (PCA): Customizable Search Scope for Finding and Checking Names
•Enhanced Private Distribution List Management
•Importing Subscribers with Recorded Names by Using the Cisco Unity Bulk Import Wizard
•Live Reply to Subscribers on Networked Cisco Unity Servers via Release to Phone System Transfer
•Private Secure Messaging
•SMTP Networking Option Not Supported Beyond the Cisco Unity 4.0(x) Train
•Networked System Broadcast Messaging
•Population of the vCard "N Property" Field in VPIM Messages
Automatic VPIM Subscriber Directory Updates
In addition to (or instead of) manually creating, modifying or deleting VPIM subscribers, you can configure Cisco Unity to automatically create, modify, or delete VPIM subscriber records based on information contained in incoming VPIM messages and nondelivery receipts. You can use either the Cisco Unity Administrator or the Cisco Unity Bulk Import wizard to configure settings to control the following:
•Whether or not the creation, modification, and deletion occurs automatically
•How the incoming information is used to create or modify a record
The settings can be individually configured for each delivery location. By default, no automatic VPIM subscriber directory updates will occur. For additional information on customizing the settings for automatic directory updates, see the "Customizing VPIM Subscriber Directory Update Settings" section on page 7-23.
The automatic VPIM subscriber directory update functionality requires Cisco Unity version 4.0(5) on any system(s) acting as VPIM bridgehead server(s). It also requires that you install the Cisco Unity Voice Connector for Exchange 2000, version 11.0(3), on any system(s) that will receive incoming VPIM messages. If you are installing the Voice Connector or setting up VPIM Networking for the first time, see the "Setting Up Cisco Unity to Use VPIM Networking" section on page 7-2. See the "Upgrading and Uninstalling Networking Options" chapter for information on upgrading the Voice Connector.
Cisco Personal Communications Assistant (PCA): Customizable Search Scope for Finding and Checking Names
By default, the search scope for the Cisco PCA Address Book is set to the local directory. As a possible convenience to subscribers in your organization, you may want to change the default search scope to the global directory instead. When this is done, subscribers can search for subscribers at different locations without having to change the search scope themselves. In addition, subscribers will not need to keep track of which Cisco Unity subscribers are listed in the local directory and which are listed in the global directory.
Changing the default search scope for the Cisco PCA Address Book changes the default search scope for the following user interfaces:
•The Find Names and Check Names dialog boxes in the Cisco Unity Inbox, which subscribers use to resolve addressing when they send messages.
•The Find Names dialog box in the Cisco Unity Assistant, which subscribers use to add members to private lists.
See the "Changing the Default Search Scope for the Cisco PCA (Optional)" section on page 2-13 for instructions for changing the default search scope.
Enhanced Private Distribution List Management
In Cisco Unity 4.0(5) and later, 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.
Importing Subscribers with Recorded Names by Using the Cisco Unity Bulk Import Wizard
The Cisco Unity Bulk Import wizard that is included with Cisco Unity version 4.0(5) has the ability to import audio files that are used to populate the recorded voice name for each subscriber. You can import audio files for regular, Internet, AMIS, Bridge, and VPIM subscribers, both when importing new subscribers and when updating existing ones. The audio files must be recorded by using a codec playable on all networked Cisco Unity servers; no conversion from one codec to another can be done during the import.
Live Reply to Subscribers on Networked Cisco Unity Servers via Release to Phone System Transfer
Live reply allows subscribers who listen to their messages by phone to respond to a message from other subscribers by calling them. Class of service settings control whether the live reply option is offered to subscribers. However, when the message sender and the recipient are homed on different networked Cisco Unity servers in the same dialing domain, additional configuration is required for the live reply option to be offered. To enable live reply in a dialing domain, you configure settings on the Dialing Domain Options page in the Cisco Unity Administrator. With Cisco Unity 4.0(5), you can choose the call transfer method used for live reply calls, as follows:
•Release to phone system—New in Cisco Unity 4.0(5), and supported with all phone system integrations.
•Cross-server live reply, with control passed to the Cisco Unity server of the called subscriber—Supported only with Cisco CallManager integrations. With cross-server live reply, you also have to enter the pilot numbers of all of the other Cisco Unity servers in the dialing domain. For more information, see the "Cross-Server Logon, Transfers, and Live Reply" chapter.
Private Secure Messaging
The private secure messaging feature provides security, through the use of public/private key encryption, for Cisco Unity subscriber voice messages that are recorded by using the Cisco Unity conversation. Voice messages that are marked private and secure cannot be heard by anyone other than a Cisco Unity subscriber who is homed on the Cisco Unity server. Private secure messaging is available in Cisco Unity version 4.0(5) and later, for systems running on Microsoft Exchange 2000 or Exchange 2003, including the partner Exchange server, if applicable. Note that if you have multiple Cisco Unity servers in your network, private secure messaging is available only to subscribers who are homed on Cisco Unity servers that are running Cisco Unity version 4.0(5).
If you have a Cisco Unity Bridge or VPIM system, and want the limited private secure messaging functionality available for these subscribers, you need to decide how outgoing private secure and incoming private voice messages will be handled for each delivery location. By default, Cisco Unity Bridge and VPIM delivery locations are not set to encrypt incoming private voice messages or to decrypt outgoing private secure voice messages. Thus, the default configuration does not allow private secure voice messages sent by Cisco Unity subscribers to be decrypted and received by Bridge or VPIM subscribers. (In the default configuration these messages will generate an NDR.) The default configuration also does not allow private messages sent by Bridge or VPIM subscribers to Cisco Unity subscribers to be encrypted.
Bridge and VPIM subscribers have only limited private secure voice messaging functionality available to them because both the public keys required for encryption of private secure voice messages and the private keys required for decryption of private secure voice messages exist only on Cisco Unity servers, and on the Exchange servers on which the Voice Connector is installed.
For additional information on using the private secure messaging feature with Cisco Unity Bridge and VPIM subscribers, see the "Securing Subscriber Messages" chapter of the Cisco Unity Security Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_book09186a008043ea54.html.
SMTP Networking Option Not Supported Beyond the Cisco Unity 4.0(x) Train
Earlier announcements indicated that SMTP Networking would not be supported in Cisco Unity 4.0(5) and later. After further consideration the decision was made to continue to support the SMTP Networking option in the 4.0(x) train because its replacement, VPIM Networking, is not supported in a pure Exchange 5.5 Cisco Unity deployment. Although SMTP Networking support is continuing, it is important to note that 4.0(x) is the last train that will support the option. We recommend that customers who need to network Cisco Unity servers that access separate directories migrate to VPIM Networking instead of using SMTP 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 functionality that is not available in SMTP Networking.
To migrate from SMTP Networking to VPIM Networking, see the "Migrating from SMTP Networking to VPIM Networking" chapter.
Note that VPIM Networking is a licensed feature and is currently supported only with Exchange 2000 and Exchange 2003.
In addition to VPIM Networking, customers will 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.
Networked System Broadcast Messaging
System broadcast messages are recorded announcements sent to everyone in an organization (or to particular location(s) within an organization). System broadcast messages are played immediately after subscribers log on to Cisco Unity by phone—even before they hear message counts for new and saved messages. Subscribers must listen to each system broadcast message in its entirety before Cisco Unity allows them to hear new and saved messages or to change setup options. They cannot fast-forward or skip a system broadcast message.
System broadcast messages can be sent to all subscribers on one or more Cisco Unity servers that access the same subscriber directory. For details, see the "Setting Up System Broadcast Messaging for Sending to All Subscribers in the Directory (Optional)" section on page 2-12.
In organizations where there are multiple Cisco Unity or Cisco Unity Express servers accessing different directories, system broadcast messages can be sent to all subscribers in the organization (or to all subscribers associated with specific sets of digitally networked servers) provided that the networks are connected by using the VPIM Networking option. For information and considerations for setting up system broadcast messages to be distributed to VPIM locations, see the "Networked System Broadcast Messages" section on page 8-7.
Population of the vCard "N Property" Field in VPIM Messages
When Cisco Unity is configured to attach a vCard—containing information about the sending Cisco Unity subscriber—to each outgoing message to a VPIM delivery location, the vCard includes name information for the subscriber in the "N Property" field. The N Property field is populated with the last name and first name of the subscriber, separated by semi-colons, to correspond with the Family name and Given Name as outlined in the vCard specification. The remote VPIM system may use information about the sender that is contained in the vCard, including the N Property, for automatic directory updates or for directory caching.
Receipt Improvements
Beginning with Cisco Unity 4.0(5), the Cisco Unity conversation and the Cisco Unity Inbox present nondelivery receipts (NDRs) and delivery receipts more intuitively, and offer subscribers additional options for managing receipts. The new functionality cannot be disabled.
Cisco Unity Conversation Receipt Improvements
•When subscribers review NDRs, the conversation now identifies all recipients whose mailboxes did not accept the original message. Recipients identified now include blind addressees in addition to regular, Internet, and external subscribers.
•Rather than always presenting the date and time after the recipient information, subscribers hear date and time before other message information when there is more than one recipient related to the NDR or delivery receipt; when there is only one related recipient, the conversation presents the date, time, and reason for the NDR or delivery receipt after playing the recipient information.
•When subscribers review delivery receipts, the conversation now identifies all recipients whose mailboxes accepted the message. Recipients identified include regular, Internet, and external subscribers and blind addressees.
•When subscribers review NDRs, they can also play the original message recording.
•When subscribers resend a message which generated an NDR, they can record an introduction, modify recipient list, and change delivery options.
•When a message could not be delivered from the Cisco Unity Bridge to the remote system because the recipient mailbox is full or does not exist, or because the original message has audio problems, the Cisco Unity conversation presents this information to the subscriber.
In addition, Cisco Unity subscribers receive an NDR for messages that could not be delivered because the Octel user has an extended absence greeting enabled and belongs to an Octel class of service that blocks delivery of incoming messages when the user has an extended absence greeting enabled. Alternatively, subscribers receive a delivery receipt for messages sent to an Octel user who has an extended absence greeting enabled, but belongs to an Octel class of service that permits delivery of incoming messages when the user has an extended absence greeting enabled.
Note that the behaviors described in this bullet occur only when the message was routed through the Voice Connector by using the Bridge 3.0(4) and later.
Networking Options
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 or the same Exchange 5.5 organization. Message routing is done by Exchange.
|
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 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 and Cisco Unity Express, and between Cisco Unity with Exchange and Cisco Unity with Domino systems.
|
Message Addressing Options
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 Exchange 5.5 custom recipients or Exchange 2000 or Exchange 2003 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
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 9-1 for more information.
To set up AMIS, Bridge, SMTP, 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.
Optionally, you may 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 send them messages.
Voice Connector
The Cisco Unity Voice Connector for Exchange is a Cisco Unity networking component that enables messaging between 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. 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. 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 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. The Voice Connector for Exchange 2000 is the only Voice Connector supported with this networking option. 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 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(3)
|
4.0(5)
|
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, see the White Paper: Cisco Unity Data and the Directory (With Microsoft Exchange) (available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_white_paper09186a00800875c5.shtml), 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/en/US/products/sw/voicesw/ps2237/products_white_paper09186a00800e4535.shtml).
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
•Distribution Lists
•Exchange Version Support
•Mailbox ID Translation
•Fax Messaging
•Message Transport Time Considerations
•Private Messages
•Private Secure Messages
•Simultaneous Analog Sessions for Message Delivery to or from Remote Voice Mail Systems
•Urgent Messages
•System Broadcast 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-5 General Connectivity Costs1
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.
|
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, see the "Supported Voice-Fax Cards" section in the Cisco Unity Bridge System Requirements, and Supported Hardware and Software, 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 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.
•In Cisco Unity 4.0(5) and later, 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.
•In Cisco Unity 4.0(5) and later, voice names for Bridge subscribers can be imported by using the Cisco Unity Bulk Import utility.
|
•Cisco Unity with Exchange 4.0(5) and later 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.
•In Cisco Unity 4.0(5) and later, voice names for VPIM subscribers can be imported by using the Cisco Unity Bulk Import utility.
|
Table 1-11 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 may 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.
|
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
|
•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.
•In Cisco Unity with Exchange 4.0(5) and later, 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-14 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. In Cisco Unity 4.0(5) and later, 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. In Cisco Unity 4.0(5) and later, 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. In Cisco Unity 4.0(5) and later, 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-15 Exchange Version Support1
AMIS
|
Bridge
|
VPIM
|
•Exchange 5.5.
•Mixed Exchange 5.5, Exchange 2000 and/or Exchange 2003 (Standard or Enterprise).
•Exchange 2000 or Exchange 2003 (Standard or Enterprise).
|
•Mixed Exchange 5.5, Exchange 2000 and/or Exchange 2003 (Standard or Enterprise).
•Exchange 2000 or Exchange 2003 (Standard or Enterprise).
|
•Mixed Exchange 5.5, Exchange 2000 and/or Exchange 2003 (Standard or Enterprise).
•Exchange 2000 or Exchange 2003 (Standard or Enterprise).
|
Table 1-16 Mailbox ID Translation1
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.
|
Table 1-17 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-18 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-19 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-20 Private Secure Messages
AMIS
|
Bridge
|
VPIM
|
The AMIS protocol does not support this functionality. Messages marked private and secure are undeliverable and will generate an NDR.
|
With default settings: Not supported. Messages marked private and secure are undeliverable and will generate an NDR.
When configured: Supported, with limitations. Messages marked private and secure are decrypted by the Voice Connector and the message is no longer secure.
|
With default settings: Not supported. Messages marked private and secure are undeliverable and will generate an NDR.
When configured: Supported, with limitations. Messages marked private and secure are decrypted by the Voice Connector and can be re-encrypted if the receiving server is Cisco Unity and if private secure messaging is configured; otherwise, the message is only marked private. During transport outside the Cisco Unity system, messages are not encrypted.
|
Table 1-21 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-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.
|
Table 1-23 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: 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, see the Cisco Unity Bridge Networking Guide, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_book09186a0080441979.html.
Regardless of which networking option you choose, you need to customize the settings for the primary location. See the "Primary Location Settings" chapter.
Feedback
