3.3(3) has been running in a few placed fine for me. I would however suggest not moving to 3.3(3) if you are in an IPCC Enterprise environment. It is not fully tested and qualified for IPCC Enterprise.
We have three server cluster with 600 IP phones, 6608, 6624, VG200, HDA, 3600, 2600, and 1760 gateways. Not all the gateways support CCM 3.3 SRST, such as the 1760. We had a problem with Conference Bridge on the 6608 not letting go of a conference and we applied an engineering special to correct the problem and we ended up killing our 6624 modules. We received a new 6624 load, which corrected the problem. Other than that, it has been good. IPCC/Express 3.1 seems to like it. I like the little enhancements that Cisco added, like "Dependency Records" option on the web pages and the web pages remember your last search for the page, which is real handy.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...