Yes, CCM 6.1 is stable enough for new deployments. There were many bugs in 6.0 but these have been fixed in the new releases. I wouldn't roll out 4.1(3) as it has been announced as End of Life. The feature sets in 6.1 really add alot of nice functionality over 5.1 so I wouldn't go with 5.1 either :)
We just moved from 4.1.3 to 6.1.1, the only issue we have found is Attendant Console's ability to connect has been buggy. We are still working with TAC on the issue, but basically it takes 2 full minutes to find the server and log in, then never populates the directory with status.
Other than that, its very nice. Administration is faster and the expanded feature set is worth the effort.
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...