Cisco Unity

Document ID: 41580

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Limitations Subscribers Can Encounter
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document describes a requirement for the use of Cisco Unity Digital Networking in an Exchange mixed-mode environment. This requirement must be kept in mind when you use Digital Networking combined with other networking options such as Audio Messaging Interchange Specification (AMIS) Networking.

In order to use Digital Networking in an Exchange mixed-mode environment, all Cisco Unity servers must use Exchange 2000 or Exchange 2003 for a partner server. When you migrate from Exchange 5.5 to Exchange 2000 or 2003 in stages, all Cisco Unity servers must be reconfigured to use an Exchange 2000 or 2003 partner server. Digital Networking is not supported between a Cisco Unity server with a partner Exchange 5.5 server and a Cisco Unity server with a partner Exchange 2000 or 2003 server

Note: Exchange 2003 is supported only with Cisco Unity 4.0(3) or later.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco Unity data architecture

• Cisco Unity Digital Networking

• The bridgehead server model used in AMIS, Bridge, Simple Mail Transfer Protocol (SMTP), and Voice Profile for Internet Messaging (VPIM) Networking

Components Used

The information in this document is based on Cisco Unity 3.0 and later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Limitations Subscribers Can Encounter

When a Cisco Unity/Exchange 5.5 server is networked with a Cisco Unity/Exchange 2000 or 2003 server, primary locations, delivery locations, and other Cisco Unity-specific attributes needed for messaging do not replicate correctly through the Microsoft Active Directory Connector (ADC). Therefore, subscribers with mailboxes on Exchange 5.5 servers are not able to send messages to subscribers with mailboxes on Exchange 2000 or 2003 servers and the other way around. However, when all the Cisco Unity servers have Exchange 2000 or 2003 for a partner server, subscriber messaging in an Exchange mixed-mode environment functions properly.

This limitation also exists when Digital Networking is combined with AMIS, Bridge, SMTP, and VPIM Networking because delivery locations do not replicate through the ADC. For example, if AMIS delivery locations are created in Cisco Unity/Exchange 5.5, only those subscribers on Cisco Unity/Exchange 5.5 are able to send messages to the remote voice messaging system represented by the AMIS delivery location. Similarly, if the AMIS delivery locations are created in Cisco Unity/Exchange 2000 or 2003, only those subscribers on Cisco Unity/Exchange 2000 or 2003 are able to send messages to the remote voice messaging system represented by the AMIS delivery location. However, when all the Cisco Unity servers have Exchange 2000 or 2003 for a partner server, AMIS messaging in an Exchange mixed-mode environment functions properly.

Note: If the application event logs show the The CsBridgeConnector service will be stopped because the Cisco Unity Bridge feature was not configured on this server error message, you might need to disable the CsBridgeConnector service on the Cisco Unity server in order to resolve the issue. This error occurs when the CsBridgeConnector service is activated on the Cisco Unity server, but the Cisco Unity Bridge feature is not configured on this Unity server. It is always recommended that you disable all the unused services on the server in order to avoid this kind of situation.

NetPro Discussion Forums - Featured Conversations

Related Information

• Requirements for Setting Up Digital Networking
• Voice Technology Support
• Voice and Unified Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support & Documentation - Cisco Systems