You can click the following link to enhance the reading of this article: Reading Blinds.

This just in from Cisco:

This post is regarding an issue where certain phones are not displaying the correct time after DST time change in the US over the past weekend – 3/8/2009.

This issue has been analyzed, and the root cause has been identified:

“CSCsy25150: CUCM timezone DST date corner case”

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsy25150

This issue has been observed with following CUCM versions :

• 5.0(X),5.1(X),6.0(X),6.1(X),7.0(X)
• and following IP Phone models seem to be affected:
• 7905, 7910, 7912, 7920, 7921, 7935, 7936, 7937, 7940, 7960

This also affects time-of-day routing, if utilized in your system.

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.

2) Create a workaround date/time group, as detailed below:

• 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 incorrect time.
• 8. Reset the new device pools.

3) Development is currently working on a patch and we expect it to be available later this week.

Important notes:

• 1. In case the system is not patched with the fix for this defect before 03/15/2009 and the 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 changed back to the original device pools after system is patched.

note : The original device pool is the one that was assigned before implementing this workaround.

If you enjoyed this post, make sure you subscribe to my RSS feed! You can also subscribe by Email and have new posts sent directly to your inbox. When you feel bored, follow me on Twitter and please share this article.