I would be more concerned with IPCC and CallManager compatibility and testing these to make sure the phone loads introduced in the CCM version work with IPCC call center agents. You can preload the phone loads to a couple of phones first for testing, instead of upgrading CCM. Then if the phone loads work, upgrade just the phone loads. Wait a week and then upgrade CCM. Another thing, make sure you use the Cisco downloads for OS patching the CCM and IPCC servers, NOT MICROSOFT. CCM and IPCC are running a stripped-down version of Windows. For Unity, you can use either Cisco's OS patches or Microsoft's. I scrutinize all patches before putting them on Unity and never apply any patches for software that does not exist on the Unity server. One last thing, is there a reason you wouldn't want to go to CCM 4.1 and Unity 4.2(1), the current versions? If you do go to Unity 4.0(5), check out the Engineering Specials, are there were a number. Not that you should apply all of them, but review for applicability in your environment. And you could always check with TAC on this as well.
thanks, I had noted the ccm/ipcc os loads from cisco, and the windows standard ones on unity, thought that was a bit strange of Cisco.. nothing like consistency.
Luckily, the only thing they did do was load new phone loads.. everything else is circa early '04.. In fact, the latest device package from cisco (4.0(46.4) for the 4.0(2) train has an older driver (7-2-4) than the load they are using (8.0(4.0) for the 7940's we are using. So I'm thinking I shouldn't touch the phone loads otherwise I'll be going backward.
I did notice all the engineering specials.. and yes, I'd like to update to later version of ccm/unity/cra, unfortunately, I'm new here, they didn't put it in a budget yada yada yada.. so I'm at least trying to bring them circa 2006 compliant as best I can.
Plus, its a heck of a learning experience wading thru 2 years of Cisco patches :-)
Are you familiar with applying maintenance to CallManager, i.e. you always do the Publisher server first followed by the subscriber(s)? We apply the CCM OS before CCM application upgrade (often times this is a requirement as listed in the compatibility doc). Unity DiRT backup is your friend (run DBWalker and resolve all errors first). And break the mirror sets of all servers before applying any patches or upgrades. Apologize in advance if you already know this!
Just to add a note to Ginger's great info (as always! 5 points from me on this one Ginger)Here are some other docs that may help. As I have discovered through many painful nights, make sure that you scrutinize all Readme documentation (Open Caveats) and use the Bug Toolkit (your best friend) to search for things that may bite you.
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...