cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5322
Views
30
Helpful
16
Replies

Wrong Time on Cisco 7940 & 7925 in CUCM 10.5(1)

david.vanherck
Level 1
Level 1

Hi,

I'm situated in Belgium where we will go to wintertime coming weekend, but the IP phone models 7940 & 7925 are showing now already the new (wrong) time. I see that only a timezone patch for 2014 is available in download center: we are running CUCM 10.5(1). (10.5(1-2014f) on download center).

Anybody has a fix to share?

Thanks!

Greets,

David

16 Replies 16

The bug CSCuv07349 contain the next zone

-America/Montevideo falls back an hour and ends DST on 8th March
-Asia/Istanbul falls back an hour and ends DST on 8th Nov
-Asia/Pyongyang falls back half an hour on 14th Aug
-Europe/Chisinau falls back an hour and ends DST on 25th Oct
-Europe/Istanbul and Turkey has same changes as that of Asia/Istanbul
-Pacific/Norfolk falls back half an hour on 4th Oct.
-America/Caymen starts DST on 13th Match and ends DST on 6th Nov.(+1hour)
-Africa/Cairo no longer follows DST
-America/Montreal is replaced with America/Toronto now
-America/Grand_Turk no longer follows DST
-America/Mexico_city starts DST on 3rd April and ends on 30th October

Fix the previous zones with ciscocm.dst-updater.2016d-el6-00.10.5.2.cop.sgn

https://software.cisco.com/download/release.html?mdfid=285963825&flowid=77896&softwareid=282074298&release=10.5(2-2016d)&relind=AVAILABLE&rellifecycle=&reltype=latest

I hope I can help them.

Last night I checked my CUCM 11.5 lab with a 7940, timezone Europe/Amsterdam. The phone showed the correct time. I noticed CUCM 11.5 runs timezone 2016d without installing additional copfiles. Attaching the same phone to a CUCM 10.5 that runs either timezone 2014f or 2015a (tested both), causes the phone to show time an hour early.

I updated one of the CUCM 10.5's to timezone 2016d and after rebooting the node (lab so single node), the 7940 showed the correct time. So this 2016d patch does seem to fix the timezone issue in Central Europe, but I cannot find any fixes related  to this timezone in the bug reports/change logs. Can anyone confirm my findings before we start rolling out this patch at live customers?

Also, I noticed this timezone is only available for CUCM 9.1 and up. I guess because CUCM 8.6 is EoL?

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: