Cisco Ip Phones displaying wrong time

You won't see 4.x represented because its not supported, but it applies.

CSCsy25150 Bug Details CUCM is not sending Daylight Saving Time updates Symptom:
Certain models of Cisco IP Phones (first generation) fail to get the time
information from the Cisco Unified Communications Manager server component. Cisco IP Phone Models: 7905, 7910, 7912, 7920, 7921, 7935, 7936, 7937, 7940, 7960, 7985.

Time of Day routing (ToD) in CUCM is also affected.

Conditions:
Any second generation IP Phone registered to Cisco Unified Communication Manager 5.X-7.X where Daylight Savings Time changes are in affect.


Workarounds:
Workaround #1:
Do nothing and wait for time to automatically correct on March 15.
--------------------------


Workaround #2:
Apply a temporary configuration workaround. Note this workaround will have to be removed when system is patched or after March 15, whichever comes first.
a. Using CUCM Admin go to: System---Date / Time Group
b. Create new Date / Time group with one hour extra of local time.
c. Go to System --- Device pool
d. Create a New Device pool and assign the (one hour extra Date time group) to this device pool.
e. Assign the new Device pool to and Cisco IP Phones that are displaying the incorrect time.
f. use BAT or BPS to apply to specific groups based on (devicemodel,currentdevicepool).
This change will have to be backed out after patching the system or after March 15, whichever comes first.

Make similar changes for Time of Day call routing repeat schedules.
--------------------------



Workaround #3:
Apply a patch from Cisco.com. This patch works on all Versions of CUCM 5.x-7.x

Software Download Center path:
Voice and Unified Communications > Cisco Unified Communications Manager Version 7.0 > Unified Communications Manager/CallManager Utilities > UCM COP Files

Hyperlink:
http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=UCM+COP+Files&mdfid=281941895&sftType=Unified+Communications+Manager%2FCallManager+Utilities&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Unified+Communications+Manager+Version+7.0&treeMdfId=278875240&treeName=Voice+and+Unified+Communications&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y

The same patch file is used for all versions of CUCM Versions 5.x-7.x



Further Information:
The workaround is only a patch to correct time issues for the week of March 8 - March 15, 2009. After that time will be correct until DST ends in November. Additional permanent fixes will be released later this year to correct DST fallback in November and to remove changes for this specific patch so that DST will begin and end correctly correctly in 2010.

Further permanent fixes are forthcoming Status
Open
(More)
Severity
2 - severe


Product
Cisco Unified Communications Manager (CallManager)

Technology


1st Found-In
5.1(3)
6.0(1)
6.1(3)
7.0(1)
7.0(2)
6.0(1a)
The status of this bug is More. The problem described in the bug report is fixed and tested in some but not all versions in which the problem exists, but development engineering work is held up pending information from an outside source, for example, waiting for the customer to verify the intended fix is actually fixed. Placing a bug report into this state allows the fixed code to be integrated into some releases. The engineer moves the bug report into the 'Resolved' state when the problem is "fixed-in" all versions. Bugs with this status may lack documentation but are often updated throughout the life of the bug. Bug Toolkit has no information on when a fix will be implemented OR when the fixed-in software will be made available to you. Any "workaround" listed in the bug details section is generally provided as a way to circumvent the bug until the code fix has been completed; often in lieu of downgrading to a non-affected version of code. You may select "Save Bug" and setup an alert to be notified when the bug gets updated in the future. Regression bugs are usually caused during the fix of another bug and the bug is usually introduced to the code at this version. Older versions are not usually affected by regression bugs. This bug has a Severe severity level 2 designation. Important functions are unusable but the router's other functions and the rest of the network is operating normally. Severity levels are designated by the engineering teams working on the bug. Severity is not an indication of customer priority which is another value used by engineering teams to determine overall customer impact. Bug documentation often assumes intermediate to advanced troubleshooting and diagnosis knowledge. Novice users are encouraged to seek fully documented support documents and/or utilize other support options available.