7960 Phone Time

Unanswered Question
Apr 2nd, 2007
User Badges:

It appears as if our 7960 phones have adjusted themselves one hour ahead, based on the old DST date (2am 1st Sunday in April). My CMs display the correct time in Windows so I am not sure why my phones would have changed or what the source would be?

Any help is appreciated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
mchandak Mon, 04/02/2007 - 04:11
User Badges:
  • Gold, 750 points or more

Was CM DST Patch installed on the box ?? If not, this is expected behaviour. CM DB is configured to force the phones to update time on 1st Sunday or April

mparella Mon, 04/02/2007 - 04:31
User Badges:

Even if we manually changed the Windows Time? The CM windows time is correct and this is teh time source, correct?

Will issue rating.

mchandak Mon, 04/02/2007 - 12:42
User Badges:
  • Gold, 750 points or more

the most simple immd fix for this issue would be to set the timezone under CallManager to the right timezone. On CCM Admin Page go to System ---> Date/Time Group and then select the timezone ur phones are in from the drop-down box for the Date/Time being used by the device pool which has all IP Phones

jbarcena Mon, 04/02/2007 - 07:35
User Badges:
  • Red, 2250 points or more

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


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.


This Discussion