There was a big push to fix a lot of the outstanding bugs in the 4.0(1) product and we closed over 30% of the outstanding bugs that were hanging out in DDTS as part of the project. However as you can see there were a lot of pretty major new features added as well (most notably Dominio support). Short story is 3.1(5) is a pretty stable release and if the new features in 4.0(1) are not important to you, personally I'd roll with 3.1(5). We are continuing to sell 3.1 for some time, a 3.1(6) release is already planned so you aren't going to be abandon on the 3.1 code line.
As a side note, the upgrade from 3.x to 4.x is much, much easier than the upgrade you're going through for 2.x to 3.x... since the back end changed entirely between 2.x and 3.x we had to do a "forklift" upgrade with the export and import tools - something that's not necessary upgrading from 3.x to later versions. If you want to make the jump to 4.x later it will be much more straight forward.
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...