I'd like to understand why it is necessary to have a CallManager patch in the first place. Why would the OS patch (CSCsf07541) be tied to a version of CallManager? What are the dependencies with respect to DST/Timezones and when they begin and end for CallManager and Windows. Why is 4.0(x) not included?
The WinOS fix addresses (among other things) the Windows console time and log file time stamps. There is a seperate CCM fix that addresses things like ToD routing and date/time group as displayed on the phone. You also need updated phone firmware for 7961/797x class phones, since these calculate their own time offsets.
Additional patches for earlier versions of CallManager should be released next week.
For the record, this is completely ridiculous. It's also a 685 MB download, this call manager cluster has been stable for the past 2 years on this release, and I don't honestly see why I have to upgrade to 4.13. Lazy developers.
I suppose we should just blame US congress for this. Bunch of dorks.
Your not ranting alone from what I have read. It does seem odd to say the least that there is no patch for CCM 4.0 :(
There is also a manual workaround just in case you are running out of time;
CCM OS Manual Workaround 3.x and 4.x
On the new US DST date, Logon with sufficient privileges to CCM Windows Server (starting with Publisher)
Click Start, Settings, Control Panel, Date and Time
Adjust the time accordingly
Click on TimeZone tab
Uncheck the Automatically adjust clock for daylight savings changes
Click Apply or Ok
Repeat steps for all servers in the cluster.
When DST ends in the Fall, the clock would have to be manually adjusted again using the same method described in steps 1-3 and 6-7 above. Please note, however, that manually adjusting the clock on CCM servers could result in a conflict in time which may produce time synchronization issues.
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...