Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DST for Callmanager 4.0.2a

I have tested a DST fix for callmanager 4.0.2a. I made an adjustment in MS SQL >> CCM300 Database >> Tables >>TypeTimezone >> Return All Rows in the eastern time to the new dates for DST. The change took effect with a reset of the phones.


Re: DST for Callmanager 4.0.2a

Why not upgrade to 4.1(3) or 4.2(3) which have fix for this?

Why stay on 4.0(2a) which has no more updates?

4.1(3) is a upgrade you can download from CCO and run, to get up to 4.1(3). 4.2(3) is also a downloadable upgrade from CCO.

Cisco also now has a standalone DST patch available for 3.3(5), 4.1(3), and 4.2(3) on the CCO Download page for 3.3, 4.1, and 4.2 updates.

So , you need to go to 4.1(3) or 4.2(3) , and current SR , then apply the standalone DST fix if you want to address this issue and be supported.

CCO Links:

New Member

Re: DST for Callmanager 4.0.2a

I am also running CCM 4.0.2a and according to TAC an upgrade to 4.1.3 or 4.2.3 with latest SR is required to resolve the new DST change issue. Or you can manually change the clock when the time comes and uncheck the "Automatically adjust clock for daylight saving changes" box.


New Member

Re: DST for Callmanager 4.0.2a


i'm running callmanager 4.12sr1. what did you enter for 'stddate' and 'dstdate'?

old dst

stddate = 0/10/0/5,2:0:0:0 - how does this translate to october 28?

dstdate = 0/4/0/1,2:0:0:0 - how does this translate to april 1

new dst

stddate = ????

dstdate = ????


Hall of Fame Super Red

Re: DST for Callmanager 4.0.2a

Hi Shawn,

Here is the info from Mahesh @ Cisco;

However as a workaround, you could resolve it by going into the Start >> Programs >> Microsoft SQL Server >> Enterprise Manager >> CCM database >> Table >> "TypeTimeZone" >> Right Click Open Table >> Return All Rows and manually set the "stddate" and "dstdate" to "0/11/0/1,2:0:0:0" and "0/3/0/2,2:0:0:0" respectively for each US timezone.

CM Service needs to be restarted.

From this detailed thread;

Hope this helps!


Here is a guess for;

old dst

stddate = 0/10/0/5,2:0:0:0 - 10=October 5= 5th week 0=Sunday

dstdate = 0/4/0/1,2:0:0:0 - 4=April 1= 1st week 0=Sunday

CreatePlease login to create content