Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unity and Unified Messenger

I have a customer which has a single forest with multiple child domains. One child domain is currently running Cisco’s Unity. In their second child domain they are about to implement Avaya’s Unified Messenger. Knowing there can be only one exchange organization per forest does anyone know of any potential schema conflicts with existing attributes? Or has anyone ever seen this type of configuration?

New Member

Re: Unity and Unified Messenger

Compare the Avaya documentation with ours. This white paper talks about the AD objects we create and utilize. We create quite a few custom objects with the ADSchemaSetup utility which shouldn't conflict with Avaya, but there are a couple of object they may be using as well as us. Overall, though, as long as you don't try importing a user into both voice mail solutions, you shouldn't have a problem.


Re: Unity and Unified Messenger

Hello -

FYI, we had both UM systems running concurrently in our domain for a transitionary period. But only Unity was configured to Exchange 2K and schema updates performed. The Unified Messenger server was peered to one Exchange 5.5 server. We are only running Unity now, but during the transition, we found using the GSM codec made the voice messages more friendly between the two systems. Don't know if this applies to your customer. And we did test running both the UM 4.01 client and VMO 3.1(5) client on several workstations (one was mine). In our testing, we did not encounter any conflicts.