7921 EDT Issue

Answered Question
Mar 9th, 2009

I have two deployments of 7921 phones running 1.3.2 and in both locations the phones did not change the time for Daylight Savings Time. Both are CallManager 5.1.3.6000-2 deployments. All the other corded phones (7960, 7961, etc.) at both locations changed correctly. Both deployments are single locations where the device pool has a Date/Time Group of CMLocal which is set to "Eastern Standard/Daylight Time - (GMT-05:00) Eastern Time (U".

Anyone know of any issues with the 7921s and Daylight savings time? I have rebooted the phone thinking they would refresh the time from CallManager but that had no affect and the 7921 phones are still 1 hour behind.

I have this problem too.
0 votes
Correct Answer by rob.huffman about 7 years 8 months ago

Hi Amir,

Yes, the Callmanager service would need to be restarted after the patch install :(

ciscocm.dst_march_2009.html

****IMPORTANT*****

This patch is a temporary workaround for the March 2009 DST issue.

You must upgrade before November 1, 2009 to a Unified Communications Manager version containing the fix for CSCsy25150 (CUCM is not sending Daylight Saving Time updates):

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

Installation Instructions for Unified Communications Manager Daylight Savings Time (DST) patch file:

File Name: ciscocm.dst_march_2009.cop.sgn

MD5 Sum: d4:f5:e2:56:29:82:f9:fd:af:44:46:be:2a:e0:8d:f1

Ensure that Database Replication is working correctly before installing this file, you can check this from RTMT or Cisco Unified Reporting.

Install this file only on the Publisher from the "Install/Upgrade" option under "Cisco Unified Communications Operating System Administration."

Wait for 60 seconds.

Ensure that Database Replication is working correctly after the installation is complete.

Restart Cisco CallManager service on all the nodes in the cluster that are running this service.

***NOTE: If you apply a device pack or other update after applying this patch and before March 15, this patch will need to be re-installed.

When a permanent fix is available for November time change a Field Notice will appear here:

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

From these ReadMe notes;

http://www.cisco.com/web/software/282204704/18582/ciscocm.dst_march_2009.html

**It is not the version of phone that impacts the TODR it is the fact that CUCM itself did not change time for the DST properly.

The fact that CUCM didn't update also impacts the older phone models that pick up their time from CUCM (unlike newer Java based 3rd Gen phones :)

Hope this helps!

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
rob.huffman Mon, 03/09/2009 - 12:46

Hi Dan,

I think you are seeing this bug (I know!!). There should be a patch out for this one pretty quick.;

The phones display wrong time because of this bug CSCsy25150 : 7960 and other phones incorrect time after DST on March 08,2009

Symptom:

----------

Certain models of Cisco IP Phones fail to get the time information from the Cisco Unified Communications Manager server component.

Cisco IP Phone Models: 7905, 7910, 7912, 7920, 7921, 7925, 7935, 7936,7937, 7940, 7960

Time of Day routing will also be an hour behind.

Conditions:

------------

Any first generation IP Phone registered to Cisco Unified Communication Manager 5.1.X and above where Daylight Savings Time changes are in affect.

-and/or-

Cisco Unified Communication Manager 5.1.X and above where Time of Day routing is being used

Workaround:

-------------

1. Using CUCM Admin go to: System---Date / Time Group

2. Create new Date / Time group with one hour extra of local time.

3. Go to System --- Device pool

4. Create a New Device pool and assign the (one hour extra Date time

group) to this device pool.

5. Assign the new Device pool to and Cisco IP Phones that are displaying

the incorrect time.

NOTE: This workaround action will need to be reversed on 03/15/2009 as the

CUCM time update will occur. Please plan to change your Device pools back

to

the original Date / Time group accordingly.

Hope this helps!

Rob

asafayan Tue, 03/10/2009 - 07:39

Hi Rob,

Is this essentially a CUCM patch and if so, is it service impacting to install it?

I don't exactly understand why a certain version of phone would impact TODR.

TIA,

Amir

Correct Answer
rob.huffman Tue, 03/10/2009 - 08:34

Hi Amir,

Yes, the Callmanager service would need to be restarted after the patch install :(

ciscocm.dst_march_2009.html

****IMPORTANT*****

This patch is a temporary workaround for the March 2009 DST issue.

You must upgrade before November 1, 2009 to a Unified Communications Manager version containing the fix for CSCsy25150 (CUCM is not sending Daylight Saving Time updates):

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

Installation Instructions for Unified Communications Manager Daylight Savings Time (DST) patch file:

File Name: ciscocm.dst_march_2009.cop.sgn

MD5 Sum: d4:f5:e2:56:29:82:f9:fd:af:44:46:be:2a:e0:8d:f1

Ensure that Database Replication is working correctly before installing this file, you can check this from RTMT or Cisco Unified Reporting.

Install this file only on the Publisher from the "Install/Upgrade" option under "Cisco Unified Communications Operating System Administration."

Wait for 60 seconds.

Ensure that Database Replication is working correctly after the installation is complete.

Restart Cisco CallManager service on all the nodes in the cluster that are running this service.

***NOTE: If you apply a device pack or other update after applying this patch and before March 15, this patch will need to be re-installed.

When a permanent fix is available for November time change a Field Notice will appear here:

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

From these ReadMe notes;

http://www.cisco.com/web/software/282204704/18582/ciscocm.dst_march_2009.html

**It is not the version of phone that impacts the TODR it is the fact that CUCM itself did not change time for the DST properly.

The fact that CUCM didn't update also impacts the older phone models that pick up their time from CUCM (unlike newer Java based 3rd Gen phones :)

Hope this helps!

Rob

asafayan Tue, 03/10/2009 - 08:45

Ok - I'm starting to follow you.

What's odd is that our CUCM did show the correct (time adjusted) clock. I found this out by SSH'ing to the server a couple of times and looking at the last login time of the "last login".

I couldn't find an actual "show clock" like CLI statement to 100% confirm the correct system clock. But the SSH last login was definitely reflecting a time adjusted correct time.

Where do 2nd/3rd gen phones get their time reference if it's not from the CUCM server itself?

rob.huffman Tue, 03/10/2009 - 10:22

Hi Amir,

Sorry, that explanation in the last line was very poor :( The 3rd Gen phones **Firmware** has the built-in capability to do the proper changes for DST (unlike the older 7940/7960's etc.) based on the time and date supplied by CUCM.

The breakdown is nicely shown in this DST doc;

Field Notice: FN - 62666 - US Daylight Savings Time Policy Change Effective March 2007 - for Cisco Unified IP Phones 7900 Series

http://www.cisco.com/en/US/ts/fn/620/fn62666.html

Hope this makes more sense,

Cheers!

Rob

asafayan Tue, 03/10/2009 - 10:25

ding ding ding...It makes sense now!

Thanks soo much.

Amir

rob.huffman Tue, 03/10/2009 - 11:00

Hi Amir,

You are most welcome my friend! Glad to help in some small way.

Cheers!

Rob

Actions

This Discussion