Guest

Cisco Unity

Networking Options Requirements for Cisco Unity (Version 5.x and Later)

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Networking Options Requirements for Cisco Unity (Version 5.x and Later)

Contents

Cisco Unity Connection Networking Requirements

Digital Networking Requirements

Digital Networking Requirements for Cisco Unity with Exchange

Version Requirements for Digital Networking in Cisco Unity with Exchange

Limit on Cisco Unity Subscribers in a Digital Network for Platform Overlay 1 and 2 Servers in Cisco Unity 8.0(3)

Active Directory Schema Extensions Required for Digital Networking

Digital Networking Requirements for Cisco Unity with Domino

Version Requirements for Digital Networking in Cisco Unity with Domino

AMIS Networking Requirements

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

AMIS Networking Requirements for Cisco Unity with Domino

Bridge Networking Requirements

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

Bridge Networking Requirements for Cisco Unity with Domino

Version Requirements for Bridge Networking in Cisco Unity with Domino

VPIM Networking Requirements

VPIM Voice Messaging System Interoperability

VPIM Networking Requirements for Cisco Unity with Exchange

Version Requirements for VPIM Networking with the Cisco Unity Voice Connector for Microsoft Exchange

Version Requirements for VPIM Networking with the Cisco Unity Interoperability Gateway for Microsoft Exchange

Active Directory Schema Extensions Required for VPIM Networking

VPIM Networking Requirements for Cisco Unity with Domino

Interoperability Gateway for Microsoft Exchange Requirements

Cisco Unity Voice Connector for Microsoft Exchange Versions

About Extending the Active Directory Schema for Cisco Unity with Exchange

Related Documentation


Networking Options Requirements for Cisco Unity (Version 5.x and Later)

Revised July 4, 2010

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 (Version 4.x and Earlier), available at http://www.cisco.com/en/US/docs/voice_ip_comm/unity/compatibility/matrix/cunetoptionsreqs4x.html.

Contents

•Cisco Unity Connection Networking Requirements

•Digital Networking Requirements

•AMIS Networking Requirements

•Bridge Networking Requirements

•VPIM Networking Requirements

•Interoperability Gateway for Microsoft Exchange Requirements

•Cisco Unity Voice Connector for Microsoft Exchange Versions

•About Extending the Active Directory Schema for Cisco Unity with Exchange

•Related Documentation

Cisco Unity Connection Networking Requirements

Revised July 4, 2010

You can link a Cisco Unity version 8.x server, failover pair, or Digital Network with a Cisco Unity Connection site to provide directory synchronization, message exchange, and call transfers between servers in both sites. The linked sites are referred to as a Cisco Voicemail Organization.

To create an intersite link, you choose a single location on each site to act as a gateway to the other site. The site gateways exchange directory synchronization information via HTTP or HTTPS. Message exchange occurs via SMTP. On the Cisco Unity site, the Interoperability Gateway for Microsoft Exchange functions as the messaging gateway. On the Connection site, the SMTP server on the Connection site gateway serves as the messaging gateway. Cross-server sign-in, transfers, and live reply can be enabled across the entire Cisco Voicemail Organization.

The following requirements apply to the Cisco Unity site for Connection Networking:

•The server or failover pair used as the site gateway must be version 8.0(3) or later.

•Other servers in the Cisco Unity Digital Network must be version 8.0(3) or later, or version 7.0(2) with Engineering Special (ES) 36 or later, or version 5.0(1) with Engineering Special (ES) 89 or later.

•The Cisco Unity server that will act as the gateway to the Cisco Unity Connection site must be able to route directly to the Connection site gateway via HTTP on port 80 or HTTPS on port 443.

•The Cisco Unity and Microsoft Exchange servers must meet the applicable requirements in the "Interoperability Gateway for Microsoft Exchange Requirements" section.

•The same Active Directory schema extensions that are required for VPIM Networking are also required for Connection Networking. (If you have already extended the schema by using the VPIM extensions for Cisco Unity release 5.0(1) or later, you do not need to further extend the schema for Connection Networking.) See the "Active Directory Schema Extensions Required for VPIM Networking" section.

Note System load testing exposed performance impacts on the Cisco Unity site gateway related to the processing of directory information to and from the remote site. These impacts can be minimized by using a Platform Overlay 2 or 3 server as the site gateway and also by minimizing the number of regular Cisco Unity subscribers homed on the site gateway.

For requirements that apply to the Connection site, see the "Requirements for Intersite Networking" section in System Requirements for Cisco Unity Connection Release 8.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html.

Digital Networking Requirements

This section contains Digital Networking requirements for Cisco Unity with Microsoft Exchange and Cisco Unity with IBM Lotus Domino. See the applicable subsection:

•Digital Networking Requirements for Cisco Unity with Exchange

•Digital Networking Requirements for Cisco Unity with Domino

Note Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x.

Note that Digital Networking between Cisco Unity with Exchange and Cisco Unity with Domino is not supported.

Digital Networking Requirements for Cisco Unity with Exchange

Revised October 15, 2010

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, or Exchange 2010.

See the following sections:

•Version Requirements for Digital Networking in Cisco Unity with Exchange

•Limit on Cisco Unity Subscribers in a Digital Network for Platform Overlay 1 and 2 Servers in Cisco Unity 8.0(3)

•Active Directory Schema Extensions Required for Digital Networking

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:

•8.0(3), 7.0(2), 5.0(1)

•7.0(2), 5.0(1), 4.2(1), 4.1(1), 4.0(5)

(For other supported version combinations specific to Cisco Unity version 4.x and earlier, see the Networking Options Requirements for 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:

•When a feature is introduced in a particular Cisco Unity version, all Cisco Unity servers must be upgraded in order to use the feature.

•Digital Networking between Cisco Unity with Exchange and Cisco Unity with Domino is not supported.

Limit on Cisco Unity Subscribers in a Digital Network for Platform Overlay 1 and 2 Servers in Cisco Unity 8.0(3)

For performance reasons, the following limitations apply when networking Cisco Unity 8.0(3) in a Digital Network:

•Platform Overlay 1 servers that are running Cisco Unity 8.0(3) cannot be used in a Digital Network that includes more than 10,000 Cisco Unity subscribers.

•Platform Overlay 2 servers that are running Cisco Unity 8.0(3) cannot be used in a Digital Network that includes more than 20,000 Cisco Unity subscribers.

If the Digital Network includes both Platform Overlay 1 and 2 servers, any one of which is running Cisco Unity 8.0(3), the lower limit applies.

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.

Digital Networking Requirements for Cisco Unity with Domino

Note Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x.

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:

•7.0(2), 5.0(1), 4.2(1), 4.1(1), 4.0(5)

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

•When a feature is introduced in a particular Cisco Unity version, all Cisco Unity servers must be upgraded in order to use the feature.

•Digital Networking between Cisco Unity with Domino and Cisco Unity with Exchange is not supported.

AMIS Networking Requirements

This section contains AMIS Networking requirements for Cisco Unity with Microsoft Exchange and Cisco Unity with IBM Lotus Domino. See the applicable subsection:

•AMIS Networking Requirements for Cisco Unity with Exchange

•AMIS Networking Requirements for Cisco Unity with Domino

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

•Active Directory Schema Extensions Required for AMIS Networking

Version Requirements for AMIS Networking in Cisco Unity with Exchange

Revised October 15, 2010

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. However, if you are using Cisco Unity version 8.x and you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server.

Caution Installing the Voice Connector on a server running Exchange 2007 or later is not supported. As a result, AMIS Networking is not supported in environments where the forest contains no servers running Exchange 2003 or Exchange 2000. If subscribers will be homed in Exchange 2007 or later and you will be using AMIS to integrate Cisco Unity with another voice-messaging system, you must retain an Exchange 2003 or an Exchange 2000 server in the forest for the Voice Connector.

Note We recommend that you always install the version of the Voice Connector that ships with your version of Cisco Unity, or a later version, in order to take advantage of new features or defect fixes.

Table 1 Supported Version Combinations for AMIS Networking in Cisco Unity with Exchange 

Cisco Unity
Bridgehead Server
Voice Connector
for Exchange 2000

8.0(3)

15.0(1)

7.0(2)

15.0(1), 14.0(1), 12.0(1)

5.0(1)

15.0(1), 14.0(1), 12.0(1), 11.0(3), 11.0(2), 11.0(1)


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.

AMIS Networking Requirements for Cisco Unity with Domino

Note Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x.

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.

Bridge Networking Requirements

This section contains Bridge Networking requirements for Cisco Unity with Microsoft Exchange and Cisco Unity with IBM Lotus Domino. See the applicable subsection:

•Bridge Networking Requirements for Cisco Unity with Exchange

•Bridge Networking Requirements for Cisco Unity with Domino

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

•Active Directory Schema Extensions Required for Bridge Networking

Version Requirements for Bridge Networking in Cisco Unity with Exchange

Revised October 15, 2010

Table 2 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. However, if you are using Cisco Unity 8.0(3) and you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server.

Caution Installing the Voice Connector on a server running Exchange 2007 or later is not supported. As a result, Bridge Networking is not supported in environments where the forest contains no servers running Exchange 2003 or Exchange 2000. If subscribers will be homed in Exchange 2007 or later and you will be using the Cisco Unity Bridge, you must retain an Exchange 2003 or an Exchange 2000 server in the forest for the Voice Connector.

Note We recommend that you always install the version of the Voice Connector that ships with your version of Cisco Unity, or a later version, in order to take advantage of new features or defect fixes.

Table 2 Supported Version Combinations for Bridge Networking in Cisco Unity with Exchange 

Cisco Unity
Bridgehead Server
Voice Connector
for Exchange 2000
Bridge Server

8.0(3)

15.0(1)

3.1(1), 3.0(6)

7.0(2)

15.0(1), 14.0(1)

3.1(1), 3.0(6)

5.0(1)

15.0(1), 14.0(1), 12.0(1)

3.1(1), 3.0(6)


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.

Bridge Networking Requirements for Cisco Unity with Domino

Note Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x.

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 3 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 3 Supported Version Combinations for Bridge Networking in Cisco Unity with Domino 

Cisco Unity
Bridgehead Server
Bridge Server

7.0(2)

3.1(1), 3.0(6)

5.0(1)

3.1(1), 3.0(6)


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 Requirements for Cisco Unity with Exchange

•VPIM Networking Requirements for Cisco Unity with Domino

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 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 with the Cisco Unity Voice Connector for Microsoft Exchange

•Version Requirements for VPIM Networking with the Cisco Unity Interoperability Gateway for Microsoft Exchange

•Active Directory Schema Extensions Required for VPIM Networking

Version Requirements for VPIM Networking with the Cisco Unity Voice Connector for Microsoft Exchange

Revised October 15, 2010

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

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. However, if you are using Cisco Unity 8.0(3) and you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server.

Caution Installing the Voice Connector on a server running Exchange 2007 or later is not supported. Use the Interoperability Gateway for Microsoft Exchange if you need to provide VPIM Networking functionality in an environment where the forest contains no Exchange 2003 or Exchange 2000 servers.

Note We recommend that you always install the version of the Voice Connector that ships with your version of Cisco Unity, or a later version, in order to take advantage of new features or defect fixes.

Table 4 Supported Version Combinations for VPIM Networking with the Cisco Unity Voice Connector for Microsoft Exchange 

Cisco Unity
Bridgehead Server
Voice Connector
for Exchange 2000

8.0(3)

15.0(1)

7.0(2)

15.0(1), 14.0(1), 12.0(1)

5.0(1)

15.0(1), 14.0(1), 12.0(1)


Version Requirements for VPIM Networking with the Cisco Unity Interoperability Gateway for Microsoft Exchange

Table 5 lists the version combinations of the Cisco Unity bridgehead server and the Interoperability Gateway for Microsoft Exchange that are supported, beginning with Cisco Unity 8.0(3), the first release to support the Interoperability Gateway.

Table 5 Supported Version Combinations for VPIM Networking with the Cisco Unity Interoperability Gateway for Microsoft Exchange 

Cisco Unity
Bridgehead Server
Interop Gateway
for Exchange

8.0(3)

8.0(3)


Caution Due to known issues with the Cisco Unity Voice Connector for Microsoft Exchange, if you use VPIM to connect a Cisco Unity deployment that uses the Interoperability Gateway to a Cisco Unity deployment that uses the Voice Connector, we highly recommend that you upgrade the Voice Connector from any earlier supported version to version 15.0(1). If you are using both gateways for VPIM and you call Cisco TAC with a problem related to using an earlier version of the Voice Connector, the Cisco TAC engineer may require that you migrate the Voice Connector to version 15.0(1).

Also see the "Interoperability Gateway for Microsoft Exchange Requirements" section.

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. (In the version of ADSchemaSetup.exe that ships with Cisco Unity release 8.0(3), the Exchange VPIM Connector option has been renamed Exchange VPIM and Connection Networking Connector, because the same schema extensions also apply to Cisco Unity Connection Networking.)

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.

VPIM Networking Requirements for Cisco Unity with Domino

Note Using IBM Lotus Domino as the message store is not supported with Cisco Unity version 8.x.

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.

Interoperability Gateway for Microsoft Exchange Requirements

Revised October 15, 2010

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

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

The Interoperability Gateway version matches the Cisco Unity version with which it is released. For example, the initial version of the Interoperability Gateway is 8.0(3), released with Cisco Unity 8.0(3).

The Interoperability Gateway has the following requirements:

•The Active Directory forest to which the Cisco Unity and Interoperability Gateway servers belong must have Windows 2000 native or higher forest functional level.

•The server on which you install the Interoperability Gateway must be running one of the following two configurations:

–Microsoft Exchange 2010 on 64-bit Windows, configured with the Hub Transport role

–Microsoft Exchange 2007 SP1 or later on 64-bit Windows, configured with the Hub Transport role, and with Microsoft .net Framework 2.0 with SP2 or a later service pack installed.

–Exchange 2003 on 32-bit Windows with Microsoft .net Framework 2.0 with SP2 or a later service pack installed.

Note Separate installation of Microsoft .net Framework 2.0 with SP2 or a later service pack may be necessary. The Interoperability Gateway installation wizard determines whether this is a requirement on your system. If the wizard indicates that .net v2 SP2 is not present, consult the Microsoft documentation for your version and update level of Windows OS to determine which package to install to have .net v2 SP2 capability.

•If the server on which you install the Interoperability Gateway is running Exchange 2003 and Cisco Security Agent for Cisco Unity, Cisco Security Agent for Cisco Unity must be at version 3.1.7 or later.

•The Interoperability Gateway must have access to at least one Cisco Unity server in the Digital Network running Cisco Unity release 8.x, and the Cisco Unity web services resource must be active on the server. (The Interoperability Gateway can be configured to talk to both a primary and a backup Cisco Unity web services server. Each must be running release 8.x. The Cisco Unity web services server provides address translation and resolution, network location information, audio encryption and decryption, and audio codec conversion services to the Interoperability Gateway.)

•Cisco Unity release 8.x is required on the Cisco Unity servers on which VPIM, Trusted Internet, or Connection Networking Locations that use the Interoperability Gateway are homed.

•The Interoperability Gateway cannot coexist with the Voice Connector transport event sink. If you use both Connection Networking and VPIM Networking, you must use the Interoperability Gateway for both types of networking. (You can, however, use the Interoperability Gateway for Connection Networking and VPIM Networking alongside the Voice Connector for AMIS and Bridge Networking).

Cisco Unity Voice Connector for Microsoft Exchange Versions

Revised October 15, 2010

Note If the Cisco Unity system is using IBM Lotus Domino as the message store, this section does not apply.

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. However, if you are using Cisco Unity version 8.0(3) and you call Cisco TAC with a problem related to using the Voice Connector that is tracked to an Exchange 2000 issue, the Cisco TAC engineer may require that you migrate the Voice Connector to an Exchange 2003 server. Earlier versions of the Voice Connector are not supported for installation on an Exchange 2003 server.

Caution Installing the Voice Connector for Exchange 2000 on a server running Exchange 2007 or later is not supported. You can use the Interoperability Gateway on an Exchange 2007 or Exchange 2010 server to provide support for Cisco Unity Connection Networking, VPIM Networking, and trusted Internet subscribers.

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 6 lists the Voice Connector versions and the Cisco Unity versions that they shipped with.

Note The availability of some networking features may require upgrading Cisco Unity as well as the Voice Connector. Descriptions in the "New and Changed Functionality" sections of Release Notes for Cisco Unity Voice Connector for Microsoft Exchange and Release Notes for Cisco Unity note when specific versions are required.

Table 6 Voice Connector and Cisco Unity Versions

Voice Connector Version
Shipped with Cisco Unity Version

15.0(1)

8.0(3)

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 If the Cisco Unity system is using IBM Lotus Domino as the message store, this section does not apply.

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 7, Table 8, and Table 9 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 Changes to Active Directory schema extensions are always backward compatible. When using Digital Networking to network different versions of Cisco Unity, always extend the schema by using the latest version of Avdirmonex2k.ldf. In addition, if you are using the Cisco Unity Bridge or VPIM to communicate with other voice-messaging systems, extend the schema by using the latest version of Omnigateway.ldf or VPIMgateway.ldf, respectively.

Note Cisco Unity versions 3.x are no longer supported. Information about these versions is provided for historical purposes only.

Table 7 Changes to Schema Extensions Required by Cisco Unity 

Cisco Unity Versions
Description

5.0(1) - 8.0(3)

Active Directory schema extensions for Cisco Unity were not changed for Cisco Unity 8.0(3) or 7.0(2).

In Cisco Unity 5.0(1), several Cisco Unity-specific attributes, an auxiliary class, and a structural class were added to Avdirmonex2k.ldf, and the schema was extended in ways that will reduce the need for further schema extensions in the future. The following classes were added:

•ciscoEcsbu-UM-Site—This structural class defines Cisco Unity site objects, but it is not currently used. That is, Cisco Unity does not create any site objects. The class contains the new ciscoEcsbuUMAttributes auxiliary class as well as the following attributes:

–organizationalUnit

–ciscoEcsbuObjectType

–ciscoEcsbuUnityBehaviorVersion—New attribute, but not currently used.

•ciscoEcsbuUMAttributes—This auxiliary class was added to avoid schema extensions in the future. It contains the following new attributes:

–ciscoEcsbuUnityAttributes—Used to store a secure messaging setting on user objects. If needed in future Cisco Unity versions, additional data can be stored in this attribute, which avoids further extensions to the schema.

–ciscoEcsbuUnityAttributesIndexed—Not currently used.

–ciscoEcsbuUnityAttributesEncoded—Not currently used.

Although the ciscoEcsbuUMAttributes auxiliary class was added to users, contacts, groups, and locations, currently, users are the only objects that contain data.

4.2(1)

The property set ciscoEcsbuUnityInformation was added to accommodate changes to the Cisco Unity Permissions wizard.

4.0(1) - 4.1(1)

The following attributes were added:

•ciscoEcsbuUMSystemState attribute to the location object class

•ciscoEcsbuAlternateDtmfIdsOrder attribute to the user object class.

•ciscoEcsbuUMSchemaVersion

3.0(1) - 3.1(6)

The core schema extensions required by Cisco Unity itself, Digital Networking, SMTP Networking, and AMIS Networking.


Table 8 Changes to Bridge Networking Schema Extensions 

Cisco Unity Versions
Description

5.0(1) - 8.0(3)

Active Directory schema extensions for Bridge Networking were not changed for Cisco Unity 8.0(3) or 7.0(2). In Cisco Unity 5.0(1), only the version number of Omnigateway.ldf was changed. However, the Cisco Unity Permissions wizard will not let you proceed if the version of the Bridge Connector schema extensions is not the same as the version of Directory Monitor schema extensions.

4.2(1)

The schema extensions for Bridge Networking changed slightly to accommodate changes to the Cisco Unity Permissions wizard.

4.0(3) - 4.1(1)

The schema extensions for Bridge Networking changed significantly in Cisco Unity 4.0(3), and the attribute ciscoEcsbuUMSchemaVersion was added. The ciscoEcsbuDtmfId attribute was not indexed. The following attributes were added to user objects:

•ciscoEcsbuRemoteNodeID

•ciscoEcsbuLegacyMailbox

The following attributes were added to location objects:

•ciscoEcsbuRemoteMailboxLength

•ciscoEcsbuRemoteMailboxLength

•ciscoEcsbuOptionFlags

4.0(1) - 4.0(2)

The ciscoEcsbuDtmfId attribute was indexed.

3.1(3) - 3.1(6)

The schema extensions required for Bridge Networking.


Table 9 Changes to VPIM Networking Schema Extensions 

Cisco Unity Versions
Description

5.0(1) - 8.0(3)

Active Directory schema extensions for VPIM Networking were not changed for Cisco Unity 8.0(3) or 7.0(2). (However, in the version of ADSchemaSetup.exe that ships with Cisco Unity 8.0(3), the Exchange VPIM Connector option has been renamed Exchange VPIM and Connection Networking Connector, because the same schema extensions also apply to Cisco Unity Connection Networking.)

In Cisco Unity 5.0(1), only the version number of Vpimgateway.ldf was changed. However, the Cisco Unity Permissions wizard will not let you proceed if the version of the VPIM Connector schema extensions is not the same as the version of Directory Monitor schema extensions.

4.2(1)

The schema extensions for VPIM Networking changed slightly to accommodate changes to the Cisco Unity Permissions wizard.

4.0(3) - 4.1(1)

The attribute ciscoEcsbuUMSchemaVersion was added.

4.0(1) - 4.0(2)

The schema extensions required for VPIM Networking.


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:

•Installation Guide for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html

•Networking Guide for Cisco Unity Bridge, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html

•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

•Networking Guide for Cisco Unity, at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guides_list.html

•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

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)

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-2010 Cisco Systems, Inc. All rights reserved.