Solved: IP Phones displaying an hour ahead

marcuscastellanos · ‎04-02-2007

Im on ccm 4.0(2). I did the cisco manual workaround when the initial DST change was required.

It looks like on 4/1 the old time change overode and now my phones are displaying an hour ahead.

The time on my server is correct 8:30.

Anyone else running into this?

jbarcena · ‎04-02-2007

Marcus, just a reminder once you have the TypeTimeZone with the updated fields and the correct time in the server you must likely will still have the incorrect time of the phones, this is because when you made the Manual change you were required to disable the "Automatically adjust clock for daylight saving changes" box. So please enable it, hit apply and reset the phones.

View solution in original post

jbarcena · ‎04-02-2007

if you didn't apply any DST patches then that is the problem since the OS patch was

meant to change the time on the server (Windows time) and the CCM patch was meant to

change the TypeTimeZone table in SQL. The time of the phones is calculated with the

Windows time and the TypeTimeZone table. This SQL table has a field for the DST time.

There are some workaround for this:

A) Manual DB change:

1. Using SQL, enterprise manager, access the CCM database.

Find the database named "CCM03XX" that has the hand (like share hand) on it. Go into that

CCM Database's table "TypeTimeZone" and find the time zone(s) your phones use. For each

time zone you use, update the following fields:

"stddate" to "0/11/0/1,2:0:0:0"

"dstdate" to "0/3/0/2,2:0:0:0"

2. Restart the CCM service ("Cisco CallManager").

3. If you use an NTP service, restart it as well.

4. Check your phones, the time should be correct now.

NOTE: If you have CCM failover configured you'll need to reset the phones for the changes

to take affect, the best way to do it is by resetting them from the device pool.

B) Apply the appropiate standalone DST patch for your CCM version:

U.S. Daylight Savings Time Policy Changes Effective March 2007 - for Cisco CallManager

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_field_notice09

186a00807e02b1.shtml

NOTE: Patch should only be applied to the PUB, since it only makes changes in the DB.

After you apply the patch you'll need to perform a cluster reboot.

C) Change the time on the CCM server one hour behind.

After the change you'll need to reset the phones.

marcuscastellanos · ‎04-02-2007

J,

I should be able to do A fine.

The problem with B is that im on 4.0(2). That patch wont apply will it?

jbarcena · ‎04-02-2007

No, there is no individual patch for your CCM version so only the first workaround will apply.

Change the TypeTimeZone table fields manually and reset the phones (not restart). If after this the phones are still showing one hour off then go to the Windows time and ENABLE the

"Automatically adjust clock for daylight savings changes" box.

marcuscastellanos · ‎04-02-2007

J,

Im in the typetimezone table, and I see the following:

Dstdate

dstbias

Am i supposed to go in query?

Im a total newbie when it comes to sql.

jbarcena · ‎04-02-2007

Marcus, just a reminder once you have the TypeTimeZone with the updated fields and the correct time in the server you must likely will still have the incorrect time of the phones, this is because when you made the Manual change you were required to disable the "Automatically adjust clock for daylight saving changes" box. So please enable it, hit apply and reset the phones.

marcuscastellanos · ‎04-03-2007

J,

It worked.

Step 1. Go in and make the change to the sql database table.

Step 2. Correct clocks on all ccm servers (click adjust daylight time)

step 3. Restart ccm service

Step 4. Restart all phones

Thanks for all the help

~M