You guessed it. The time on the phones is wrong!
Im set for NTP reference to hit my Domain Controller, which was patched and has the proper time on it. However the phones rae still an hour behind.
I have reset the date/time group 3 times now with no luck.
Same problem here on 6.0.
7970 phones show the correct time, but we only have two of those. All the rest of our phones are 7940/7960 phones and they are all displaying the time one hour behind after DST went into effect this weekend. All of the device pools are using CMLocal, and CMLocal is configured properly with an accurate NTP reference. Even the server shows the correct date, time, and timezone when I do "show status" from an SSH console.
I opened up a TAC case. Waiting to hear back.
I even set up a unique device pool and date/time group and cant get it to work either.
Is there a patch for the new DST times that need to be applied?
Here is the response I received from TAC:
This issue has been analyzed, root cause has been identified and defect is
"CSCsy25150: CUCM timezone DST date corner case"
This issue has been observed with following CUCM versions :
and following IP Phone models seem to be effected:
7905, 7910, 7912, 7920, 7921, 7935, 7936, 7937, 7940, 7960
While waiting for the fix to be available, you need to apply following
1. From CCMADMIN go to > System > Date / Time Group
2. Create new Date/Time group, name it 'DST-Workaround'
3. Configure a Timezone which is 1 hour ahead of your current timezone.
4. From CCMADMIN go to > System > Device pool
5. Create a New Device pool, name it 'DST-Workaround'.
6. Assign to this device pool the Date/Time group created under step 1.
7. Assign the new device pool to the IP Phones that are displaying the
8. Restart the CCM service on all nodes.
Development is currently working on a patch and we expect it to be available
later this week.
By the way, I have quite a large number of phones in quite a few device pools. It has actually been easier just to create the new date/time group and re-assign all of my device pools to the temporary date/time group and reset devices.
Also surprised by Cisco's slip on this one. Seems like a pretty largly affected audience.
This is affecting all of my 7940 devices, 7941's are working great.
I just got this from TAC too...
"...There are a few options for this issue:
1) Do nothing. The time on these phone models will be wrong the rest of this week, and will then correct themselves on Sunday Mar 15.
Important notes :
1. In case the system is not patched with the fix for this defect before 03/15/2009 and above workaround has been implemented, the device pools assigned to these phones need to be manually changed back to the original device pools on that day (03/15/2009).
2. In case the system is patched with the fix for this defect before 03/15/2009 and above workaround has been implemented, the device pools need to be manually"
What affect does restarting the CCM service have on a live production network?
Also, do I need to create a new device pool for each of my offices? Or if I throw all of my devices into one device pool..is it going to restrict calling from one office to another?
Restarting the CCM service will be disruptive. Calls will get dropped for the duration of the restart.
If you put everything into one device pool, there might be other unintended consequences. The suggested workaround of changing the Date/Time Group might be a good one if you want to minimize changes. That way you can easily revert to your original configuration once the dust settles.
Hopefully testing on the fix will be completed shortly and the fix posted.
Thanks for the advice on the easier workaround. However, if we have some devices (7940's) that are affected, and some that are not (7941's) then changing the date/time group is probably not going to work..right?