I have two deployments of 7921 phones running 1.3.2 and in both locations the phones did not change the time for Daylight Savings Time. Both are CallManager 18.104.22.16800-2 deployments. All the other corded phones (7960, 7961, etc.) at both locations changed correctly. Both deployments are single locations where the device pool has a Date/Time Group of CMLocal which is set to "Eastern Standard/Daylight Time - (GMT-05:00) Eastern Time (U".
Anyone know of any issues with the 7921s and Daylight savings time? I have rebooted the phone thinking they would refresh the time from CallManager but that had no affect and the 7921 phones are still 1 hour behind.
Yes, the Callmanager service would need to be restarted after the patch install :(
This patch is a temporary workaround for the March 2009 DST issue.
You must upgrade before November 1, 2009 to a Unified Communications Manager version containing the fix for CSCsy25150 (CUCM is not sending Daylight Saving Time updates):
Installation Instructions for Unified Communications Manager Daylight Savings Time (DST) patch file:
File Name: ciscocm.dst_march_2009.cop.sgn
MD5 Sum: d4:f5:e2:56:29:82:f9:fd:af:44:46:be:2a:e0:8d:f1
Ensure that Database Replication is working correctly before installing this file, you can check this from RTMT or Cisco Unified Reporting.
Install this file only on the Publisher from the "Install/Upgrade" option under "Cisco Unified Communications Operating System Administration."
Wait for 60 seconds.
Ensure that Database Replication is working correctly after the installation is complete.
Restart Cisco CallManager service on all the nodes in the cluster that are running this service.
***NOTE: If you apply a device pack or other update after applying this patch and before March 15, this patch will need to be re-installed.
When a permanent fix is available for November time change a Field Notice will appear here:
From these ReadMe notes;
**It is not the version of phone that impacts the TODR it is the fact that CUCM itself did not change time for the DST properly.
The fact that CUCM didn't update also impacts the older phone models that pick up their time from CUCM (unlike newer Java based 3rd Gen phones :)
Hope this helps!