Table Of Contents
Networking in Cisco Unity
Overview: Networking in Cisco Unity
Networking Options
Message Addressing Options
Locations and External Subscribers
Interop Gateway
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:
•Networking Options
•Message Addressing Options
•Locations and External Subscribers
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 Domino servers used by the Cisco Unity servers are in the same Domino domain. Message routing is done by the Domino router. If the Domino servers are in different Domino domains, the Cisco Unity servers can be configured to monitor the same set of Domino address books.
|
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 use Notes as their mail system. 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 use Notes as their mail system. 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 Domino Person documents that have "Other Internet Mail" set for the Mail 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. 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, 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 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.
Interop Gateway
The Interop Gateway for Domino is a Cisco Unity service (called CsDomInteropGty) that enables messaging between Cisco Unity and other voice messaging systems. The Interop Gateway files are copied to the Cisco Unity server during setup; however, the Interop Gateway is not installed as a service until you run the Interop Gateway Configuration wizard when configuring Cisco Unity for AMIS, Bridge, or VPIM Networking. The Interop Gateway Configuration wizard configures and starts the service. In the Interop Gateway Configuration wizard, you specify a Domino Foreign domain name (for example, "voicemail.domain.com"), a mail file name, and the name of the server where the mail file will be located.
Cisco Unity addresses outbound AMIS, Bridge, and VPIM messages to the specified Foreign domain, and incoming Bridge and VPIM messages are addressed to the specified Foreign domain. Messages addressed to the Foreign domain are routed to the mail file specified in the Foreign domain document by the Domino router. The Interop Gateway monitors the mail file for messages, and performs the following functions:
•AMIS Networking—The Interop Gateway 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 Interop Gateway mail file for processing.
•Bridge Networking—The Interop Gateway performs the message conversion and address translation that allows Cisco Unity to exchange messages with the Cisco Unity Bridge server.
•VPIM Networking—The Interop Gateway performs the message conversion and address translation that allows Cisco Unity to exchange messages with other voice messaging systems by using the VPIM protocol. VPIM Networking also provides messaging between:
–Cisco Unity servers where the Domino servers are in different Domino domains and cannot be configured for Digital Networking
–Cisco Unity with Domino systems and Cisco Unity with Exchange systems
–Cisco Unity and Cisco Unity Express
Note that the Interop Gateway is not needed with Digital Networking because the Cisco Unity servers access the same directory.
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:
•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
•Simultaneous Analog Sessions for Message Delivery to or from Remote Voice Mail Systems
•Urgent Messages
Table 1-3 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-4.)
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.
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-5 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-6 Blind Addressing
AMIS
|
Bridge
|
VPIM
|
Available through the Cisco Unity Telephone User Interface (TUI) and the IBM Lotus Notes client set up with csClient, a DUC for Cisco component.
|
Available through the Cisco Unity TUI and the DUC-enabled Notes client.
|
Available through the Cisco Unity TUI and the DUC-enabled Notes client.
|
Table 1-7 Addressing by Name or by Extension
AMIS
|
Bridge
|
VPIM
|
Available through the Cisco Unity TUI and the DUC-enabled Notes client.
|
Available through the Cisco Unity TUI and the DUC-enabled Notes client.
|
Available through the Cisco Unity TUI and the DUC-enabled Notes client.
|
Table 1-8 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.
|
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-9 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.
|
Table 1-10 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-11 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-12 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 Domino 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 Domino 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 Domino documentation for more information.)
|
Table 1-13 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-14 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-15 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.
|
Domino 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-16 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-17 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-18 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 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 Networking Guide for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Regardless of which networking option you choose, you need to customize the settings for the primary location. See the "Primary Location Settings" chapter.
