We're running Callmanager 184.108.40.20600-7 and I came in this morning to all our 7940s set an hour ahead. I've checked and the callmanager server and NTP server are both correct and time zones are set correctly.
I'm a bit confused, does anyone know if there is a patch or workaround for this?
Solved! Go to Solution.
we have this problem on :
- 1 cluster 7.1.5
- 2 cluster 8.5
- 4 cluster 8.6
we have juste upgrade one cluster of 8.6 and this problem is fixed.
it seems the COP file ist not working at CUCM version 9.1.1, does anybody have the same experience or know a fix for this release as well?
At version 8.5 and 8.6 it works fine, that`s i have tested today
I had the same issue with the version: 220.127.116.1100-11 Unrestricted.
(the cop ciscocm.dst-updater.2012j-1.el18.104.22.168.cop was installed)
All is fixed on CCM 8.5 and 8.6
I updated my SR, i am now waiting their feedback,
I have updates a CM 8.5 Cluster, and all worked ok.
However i also have several clients with CM7.1.5 Business Edition (i.e. includes Unity Connection on the same box)
i get the following logs at the end of the log when installing the patch
[Capture] Removing the IBM JTZU temp directory
OS execution complete
Executing Product component
[Capture] Unity Connection upgrade script not found. Unity Connection shall not be upgraded
Component execution failed
Execution failed. Please see the log file.
Rolling back the changes
Unsuccessfully installed ciscocm.ciscocm.dst-updater-tzdata-2012j-1.el4-7.1.5.cop
(25927) Tue Mar 26 21:38:15 GMT 2013
ERROR: Install script of option /common/download//ciscocm.dst-updater.2012j-1.el22.214.171.124.cop failed
And therefore it does not install/activate the DST updater fo rthe CM part.
Any ideas, has cisco tested on all versions?
I have been writing with Cisco TAC about 2014 and 2015 because we will be facing the same problem in 2014 and 2015. The reason why we will have the same issue in 2014 and 2015 is because the timezone configuration in CUCM database is fixed and this value is set for the DST to change on the 4th Sunday of March which is correct most of the time.
In Marts 2014 and 2015 there are also 5 sundays like 2013 and Cisco will provide a new timezone update installation file for 2014 that correct the issue for 2014 and it will be available in late February/early March 2014.
Best regards, Kennet
Did you get anywhere with Cisco TAC about the DST changes.
Very good catch by the way and has stopped us from deploying mutiple patches that could be no use.
I have just hear from Cisco TAC today and they are working on a more flexible solution(bugid CSCuf78904) and I have also asked Cisco if it was possible to get the timezone update sooner because I think a 3 weeks notice is too late if you have a lot of CUCM clusters to implement this update on but unfortunately it isn't possible to get the update sooner so we have to wait until Marts 2014 for the update. Maybe the flexible solution will be available before Marts (My fingers are crossed).
I have call manager 8.6.2 and i also have same issue with 6921 IP Phone. I have upload the DST cop file also but still issue is persist. kindly help me for this.