I have been told by conversations with TAC that Unity 3.x is supported within an Exchange 5.5 Environment, however, it is not recommended. I was told that Unity 3.x does not "Play Well" with a Unity 3.x, Exchange 5.5 and SQL 2000 integration. <br><br>Could I get some clarification on this. I have several customers that are using 2.4.6 and would like to install 3.x to utilize the features within the product. I just would like a little clarification before making recommendations. <br><br>All of our customers who are running 2.4.6 were installed with W2K and not NT4.<br><br>
Not sure where you're hearing this but it's not correct. Unity 3.0 works fine with Exchange 5.5.
There may be some confusion about folks wanting to MIX Unity 2.4.x and Unity 3.x and use networking features across them (this wont work) or having some users on Exchange 2000 and some users on Exchange 5.5 with Unity in the mix (it's really a good idea to get Unity on Ex2K in this situation). But if a customer is running Exchange 5.5 and they wan to use Unity 3.0, there should be no problem at all with that.
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...