I have a customer which has a single forest with multiple child domains. One child domain is currently running Ciscos Unity. In their second child domain they are about to implement Avayas 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?
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.
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...