Table Of Contents
Cisco Unity Networking Options Requirements (Cisco Unity Version 5.x and Later)
Digital Networking Requirements
Digital Networking Requirements for Cisco Unity with Domino
Version Requirements for Digital Networking in Cisco Unity with Domino
Digital Networking Requirements for Cisco Unity with Exchange
Version Requirements for Digital Networking in Cisco Unity with Exchange
Active Directory Schema Extensions Required for Digital Networking
AMIS Networking Requirements for Cisco Unity with Domino
AMIS Networking Requirements for Cisco Unity with Exchange
Version Requirements for AMIS Networking in Cisco Unity with Exchange
Active Directory Schema Extensions Required for AMIS Networking
Bridge Networking Requirements
Bridge Networking Requirements for Cisco Unity with Domino
Version Requirements for Bridge Networking in Cisco Unity with Domino
Bridge Networking Requirements for Cisco Unity with Exchange
Version Requirements for Bridge Networking in Cisco Unity with Exchange
Active Directory Schema Extensions Required for Bridge Networking
VPIM Voice Messaging System Interoperability
VPIM Networking Requirements for Cisco Unity with Domino
VPIM Networking Requirements for Cisco Unity with Exchange
Version Requirements for VPIM Networking in Cisco Unity with Exchange
Active Directory Schema Extensions Required for VPIM Networking
Cisco Unity Voice Connector for Microsoft Exchange Versions
About Extending the Active Directory Schema for Cisco Unity with Exchange
Cisco Unity Networking Options Requirements (Cisco Unity Version 5.x and Later)
Revised May 21, 2008
This document describes version and compatibility requirements for installing additional Cisco Unity servers, and for adding or combining networking options on a Cisco Unity system.
The information in this document is applicable to Cisco Unity versions 5.x and later. For information applicable to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.
Contents
•
Digital Networking Requirements
•
•
•
Digital Networking Requirements
This section contains Digital Networking requirements for Cisco Unity with IBM Lotus Domino and Cisco Unity with Microsoft Exchange. See the applicable subsection:
•
•
Note that Digital Networking between Cisco Unity with Exchange and Cisco Unity with Domino is not supported.
Digital Networking Requirements for Cisco Unity with Domino
Digital Networking allows messaging among multiple Cisco Unity servers that access the same subscriber directory. The directory (or address book) in which Cisco Unity stores data and from which subscribers and distribution lists are imported is specified in the Message Store Configuration wizard when each Cisco Unity server is set up. Typically, Names.nsf is specified during setup unless you use a different name for your Domino domain directory. By default, the directory that was specified in the Message Store Configuration wizard is monitored by each Cisco Unity server for data from other Cisco Unity servers.
Beginning with Cisco Unity 4.0(5), if any or all of the Cisco Unity servers that will be set up for Digital Networking use a different directory (or a secondary subscriber address book), every Cisco Unity server will need to be configured to monitor the applicable directories on every other server, as described in the "Managing Monitored Address Books" section in the "Digital Networking" chapter of the applicable Networking Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Note that the Interop Gateway is not used in Digital Networking.
Version Requirements for Digital Networking in Cisco Unity with Domino
The following list shows the Cisco Unity version combinations that are supported for networked Cisco Unity servers, when the network includes Cisco Unity 5.x and later:
•
(For other supported version combinations specific to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Note the following considerations when networking multiple versions of Cisco Unity:
•
•
Digital Networking Requirements for Cisco Unity with Exchange
Digital Networking allows messaging among multiple Cisco Unity servers that access the same subscriber directory. To use Digital Networking, the partner Exchange servers must be in the same Active Directory forest, and must be running Exchange 2000, Exchange 2003, or Exchange 2007.
Note that the Voice Connector is not used in Digital Networking.
See the following sections:
•
•
Version Requirements for Digital Networking in Cisco Unity with Exchange
The following list shows the Cisco Unity version combinations that are supported for networked Cisco Unity servers, when the network includes Cisco Unity 5.x and later:
•
(For other supported version combinations specific to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Note the following considerations when networking multiple versions of Cisco Unity:
•
•
Active Directory Schema Extensions Required for Digital Networking
The Active Directory schema extensions needed for Digital Networking are included in the set of core schema extensions required by Cisco Unity itself. These schema modifications are in the file Avdirmonex2k.ldf, which is executed when you run ADSchemaSetup.exe and choose Exchange Directory Monitor. When networking servers that are running different versions of Cisco Unity, run ADSchemaSetup.exe with the Exchange Directory Monitor option from the Cisco Unity installation media version that matches the most recent release of Cisco Unity in the network.
Note that the schema occasionally changes with a new Cisco Unity release. For information on whether the schema changed for your version of Cisco Unity and on applying schema extensions, see the "About Extending the Active Directory Schema for Cisco Unity with Exchange" section.
AMIS Networking Requirements
This section contains AMIS Networking requirements for Cisco Unity with IBM Lotus Domino and Cisco Unity with Microsoft Exchange. See the applicable subsection:
•
•
AMIS Networking Requirements for Cisco Unity with Domino
AMIS Networking allows messaging between Cisco Unity and other voice messaging systems that support the Audio Messaging Interchange Specification analog (AMIS-a) version 1 protocol.
The Interop Gateway for Domino is a Cisco Unity component that enables messaging between Cisco Unity and other voice messaging systems. The Interop Gateway does the same tasks as the Cisco Unity Voice Connector for Microsoft Exchange does for Cisco Unity with Exchange systems. Unlike the Voice Connector (which is installed on an Exchange server), the Interop Gateway is a service that runs on the Cisco Unity server and is not available separately from the rest of Cisco Unity.
AMIS Networking Requirements for Cisco Unity with Exchange
AMIS Networking allows messaging between Cisco Unity and other voice messaging systems that support the Audio Messaging Interchange Specification analog (AMIS-a) protocol.
See the following sections:
•
•
Version Requirements for AMIS Networking in Cisco Unity with Exchange
Table 1 lists the version combinations of the Cisco Unity bridgehead server and the Voice Connector that are supported for AMIS Networking, beginning with Cisco Unity 5.0(1). (For information applicable to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Only the Voice Connector for Exchange 2000 is supported for use with AMIS Networking in Cisco Unity 5.0(1) and later. Note that versions 11.0(1) and later of the Voice Connector for Exchange 2000 can be installed on either an Exchange 2000 or Exchange 2003 server.
Caution
Note
Active Directory Schema Extensions Required for AMIS Networking
The Active Directory schema extensions needed for AMIS Networking are included in the set of core schema extensions required by Cisco Unity itself. These schema modifications are in the file Avdirmonex2k.ldf, which is executed when you run ADSchemaSetup.exe and choose Exchange Directory Monitor. Run ADSchemaSetup.exe with the Exchange Directory Monitor option from the Cisco Unity installation media version that matches the most recent release of Cisco Unity in the network.
Note that the schema occasionally changes with a new Cisco Unity release. For information on whether the schema changed for your version of Cisco Unity and on applying schema extensions, see the "About Extending the Active Directory Schema for Cisco Unity with Exchange" section.
Bridge Networking Requirements
This section contains Bridge Networking requirements for Cisco Unity with IBM Lotus Domino and Cisco Unity with Microsoft Exchange. See the applicable subsection:
•
•
Bridge Networking Requirements for Cisco Unity with Domino
Bridge Networking allows messaging between Cisco Unity and Avaya voice messaging systems on an Octel analog network by using the Cisco Unity Bridge. For a list of voice messaging systems supported for Bridge Networking, see the "Supported Voice Messaging Systems" section of the applicable 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.
The Interop Gateway for Domino is a Cisco Unity component that enables messaging between Cisco Unity and other voice messaging systems. The Interop Gateway does the same tasks as the Cisco Unity Voice Connector for Microsoft Exchange does for Cisco Unity with Exchange systems. Unlike the Voice Connector (which is installed on an Exchange server), the Interop Gateway is a service that runs on the Cisco Unity server and is not available separately from the rest of Cisco Unity.
Version Requirements for Bridge Networking in Cisco Unity with Domino
Table 2 lists the version combinations of the Cisco Unity bridgehead server and the version of the Cisco Unity Bridge that are supported for Bridge Networking, beginning with Cisco Unity 5.0(1). (For information applicable to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Table 2 Supported Version Combinations for Bridge Networking in Cisco Unity with Domino
Bridgehead Server7.0(2)
3.1(1), 3.0(6)
5.0(1)
3.1(1), 3.0(6)
Bridge Networking Requirements for Cisco Unity with Exchange
Bridge Networking allows messaging between Cisco Unity and Avaya voice messaging systems on an Octel analog network by using the Cisco Unity Bridge.
For a list of voice messaging systems supported for Bridge Networking, see the "Supported Voice Messaging Systems" section of the applicable 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.
See the following sections:
•
•
Version Requirements for Bridge Networking in Cisco Unity with Exchange
Table 3 lists the version combinations of the Cisco Unity bridgehead server, the Voice Connector, and the Cisco Unity Bridge software on the Bridge server that are supported for Bridge Networking, beginning with Cisco Unity 5.0(1). (For information applicable to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Only the Voice Connector for Exchange 2000 is supported for use with Bridge Networking. Note that versions 11.0(1) and later of the Voice Connector for Exchange 2000 can be installed on either an Exchange 2000 or Exchange 2003 server.
Caution
Note
Active Directory Schema Extensions Required for Bridge Networking
To support Bridge Networking, in addition to the set of core schema extensions required by Cisco Unity itself, the Active Directory schema must be further extended. The additional schema modifications to support Bridge Networking are in the file Omnigateway.ldf, which is executed when you run ADSchemaSetup.exe and choose Exchange Bridge Connector. Run ADSchemaSetup.exe with both the Exchange Directory Monitor and the Exchange Bridge Connector options from the Cisco Unity installation media version that matches the most recent release of Cisco Unity in the network. For information on whether Omnigateway.ldf changed for your version of Cisco Unity and on applying schema extensions, see the "About Extending the Active Directory Schema for Cisco Unity with Exchange" section.
VPIM Networking Requirements
This section contains VPIM Networking requirements for Cisco Unity with IBM Lotus Domino and Cisco Unity with Microsoft Exchange. See the applicable subsection:
•
•
•
VPIM Voice Messaging System Interoperability
VPIM Networking can be used to provide voice-mail message networking between voice messaging systems that support the Voice Profile for Internet Mail (VPIM) version 2 protocol. This includes Cisco Unity Express 2.1(2) and later and Cisco Unity Connection 2.0(1) and later, as well as third-party voice messaging systems. You can also use VPIM Networking to network Cisco Unity with Exchange and Cisco Unity with Domino systems.
VPIM Networking Requirements for Cisco Unity with Domino
VPIM Networking allows messaging between Cisco Unity and other voice messaging systems that support the Voice Profile for Internet Mail (VPIM) version 2 protocol.
The Interop Gateway for Domino is a Cisco Unity component that enables messaging between Cisco Unity and other voice messaging systems. The Interop Gateway does the same tasks as the Cisco Unity Voice Connector for Microsoft Exchange does for Cisco Unity with Exchange systems. Unlike the Voice Connector (which is installed on an Exchange server), the Interop Gateway is a service that runs on the Cisco Unity server and is not available separately from the rest of Cisco Unity.
VPIM Networking Requirements for Cisco Unity with Exchange
VPIM Networking allows messaging between Cisco Unity and other voice messaging systems that support the Voice Profile for Internet Mail (VPIM) version 2 protocol.
See the following sections:
•
•
Version Requirements for VPIM Networking in Cisco Unity with Exchange
Table 4 lists the version combinations of the Cisco Unity bridgehead server and the Voice Connector that are supported for VPIM Networking, beginning with Cisco Unity 5.0(1). (For information applicable to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for Cisco Unity (Cisco Unity Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.)
Only the Voice Connector for Exchange 2000 is supported for use with VPIM Networking. Note that versions 11.0(1) and later of the Voice Connector for Exchange 2000 can be installed on either an Exchange 2000 or Exchange 2003 server.
Caution
Note
Table 4 Supported Version Combinations for VPIM Networking in Cisco Unity with Exchange
Bridgehead Server
for Exchange 20007.0(2)
14.0(1), 12.0(1)
5.0(1)
14.0(1), 12.0(1)
Active Directory Schema Extensions Required for VPIM Networking
To support VPIM Networking, in addition to the set of core schema extensions required by Cisco Unity itself, the Active Directory schema must be further extended. The additional schema modifications to support VPIM Networking are in the file Vpimgateway.ldf, which is executed when you run ADSchemaSetup.exe and choose Exchange VPIM Connector. Run ADSchemaSetup.exe with both the Exchange Directory Monitor and the Exchange VPIM Connector options from the Cisco Unity installation media version that matches the most recent release of Cisco Unity in the network
Note that the schema occasionally changes with a new Cisco Unity release. For information on whether the schema changed for your version of Cisco Unity and on applying schema extensions, see the "About Extending the Active Directory Schema for Cisco Unity with Exchange" section.
Cisco Unity Voice Connector for Microsoft Exchange Versions
Note
The Cisco Unity Voice Connector for Microsoft Exchange is a Cisco Unity networking component that enables messaging between Cisco Unity servers that access separate directories, and between Cisco Unity servers and other voice messaging systems. The Voice Connector is used with the AMIS, Bridge, and VPIM networking options.
The Voice Connector for Exchange 2000 version 11.0(1) and later can be installed on either an Exchange 2000 or Exchange 2003 server. Earlier versions of the Voice Connector are not supported for installation on an Exchange 2003 server.
Caution
The Voice Connector ships with Cisco Unity. For information on downloading the Voice Connector, see the applicable Release Notes for Cisco Unity Voice Connector for Microsoft Exchange at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
Table 5 lists the Voice Connector versions and the Cisco Unity versions that they shipped with.
Note
Table 5 Voice Connector and Cisco Unity Versions
14.0(1)
7.0(2)
12.0(1)
5.0(1)
11.0(3)
4.2(1), 4.1(1), 4.0(5)
11.0(2)
4.0(4)
11.0(1)
4.0(3)
About Extending the Active Directory Schema for Cisco Unity with Exchange
Note
To extend the Active Directory schema, you run a Cisco Unity utility called ADSchemaSetup.exe. The utility applies the schema extensions specified in the LDIF script files located on Cisco Unity DVD 1 and CD 1 in the directory Schema\LdifScripts.
The user interface for ADSchemaSetup.exe consists of a dialog box with check boxes that correspond to the LDIF script files. Table 6, Table 7, and Table 8 provide a chronology of the schema extension changes in the LDIF script files named Avdirmonex2k.ldf (corresponds to the "Directory Monitor" check box), Omnigateway.ldf (corresponds to the "Bridge Connector" check box) and Vpimgateway.ldf (corresponds to the "VPIM Connector" check box), respectively.
The LDIF files have changed between Cisco Unity versions as needed to provide additional features and functionality, as noted.
Note
Note
For more information about the Active Directory schema extensions required by Cisco Unity, see the applicable Cisco Unity Data and the Directory white paper, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.
A procedure for running ADSchemaSetup.exe is included in the Installation Guide for Cisco Unity, the Networking Guide for Cisco Unity, and the Networking Guide for Cisco Unity Bridge. Use the procedures in these guides if you are installing Cisco Unity or configuring networking features for the first time.
If you are upgrading Cisco Unity to a version that requires a schema update, see the Reconfiguration and Upgrade Guide for Cisco Unity for information on how and when to update the schema.
All versions of the Installation Guides for Cisco Unity and the Reconfiguration and Upgrade Guide for Cisco Unity can be found at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html. The Networking Guide for Cisco Unity and Networking Guide for Cisco Unity Bridge can be found at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html.
Related Documentation
The following documents are available on Cisco.com:
•
•
•
•
•
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007-2008 Cisco Systems, Inc. All rights reserved.
Guest
