Guest

Cisco Unified Communications Manager (CallManager)

Field Notice: FN - 62669 - U.S. Daylight Saving Time Policy Changes for Cisco CallManager/Communications Manager


Revised November 2, 2007

February 12, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Revision History

Revision

Date

Comment

2.4

02-NOV-2007

Added DDTS CSCsl12482. Added "or higher" to Device Packs. Inside "Windows Patch:" table - Changed from "Windows Release Minimum OS Release with the Windows 200x DST patch for US DST 2000.4.5a No action required" - To "2000.4.5 or 2000.4.5a 2000.4.5b(sr3) or higher". Under "Manual Workaround for Cisco Unified Communcation Manager 5.x or later:" Added paragraph starting with "For Cisco Unified Communications Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. On November 4, 2007, after 03:01 A.M., move the clock back one hour on each Cisco Unified Communications Manager cluster node.

2.3

17-OCT-2007

Added DDTS CSCsh20360, CSCsh91735, CSCsh81417, and CSCsf07541. Added numerous updates to Workaround/Solution section.

2.2

12-OCT-2007

Updated whole field notice including Title, added DDTS CSCsh12444 and CSCsh68517.

2.1

02-APR-2007

Changed phone load item #2 from "8.2.2 standalone phone load" to "8.2.2sr1 standalone phone load" in the Workaround/Solution section.

2.0

28-MAR-2007

In the April 1, 2007 recommendation section, clarified the steps for customers who applied the Manual Clock Advance workaround on March 11, 2007 and added instructions to set the server clock to the current local time on each CallManager cluster node.

1.9

27-MAR-2007

Added bug CSCsi09102. Added April 1, 2007 workarounds, phone load update to 8.2.2, link to chart with working URLs, and "Cisco Unified CallManager with endpoints in Mexico and the United States" note to Workaround/Solution section.

1.8

13-MAR-2007

Updated table of DST fixes. Added ciscocm.4-2-3-2007-DST-Update.1-0-1.exe to DST patch list. Added ***Important Note*** section. Added a line stating that it is important to apply the DST patches in order. Added a note in the "IMPORTANT NOTE" section to reset the phone. Added a note before the table with instruction to first consult the "callmanager database table update"section.

1.7

10-MAR-2007

Updated Workaround/Solution section and replaced image with an updated version.

1.6

09-MAR-2007

Added CM Windows OS - 4.0(x) to Products Affected section. Added ciscocm.4-0-2a-2007-DST-Update.1-0-1.exe to list of patches. Added "if you are running 5.0.4.2122-1 or lower follow the Manual workaround for CCM 5.x or later" to the TOD Routing notice. Updated table of DST fixes.

1.5

07-MAR-2007

Added bug CSCsh81747 to the DDTS section.

1.4

07-MAR-2007

Updated the Workaround Solution section with the following changes: Added chart to Windows 2000 Patch section. Changed steps in the CallManager OS Manual Workaround 3.x and 4.x section. Updated wording in Step 2 of Time of Day routing section.

1.3

07-MAR-2007

Updated patch information for 5.0.4 in the table in the Workaround/Solution section.

1.2

05-MAR-2007

Added Time of Day information to Workaround/Solution section. Updated table of DST fixes in Workaround/Solution section.

1.1

01-MAR-2007

Changed wording from "CM Windows OS" to "CM Appliance OS" in Products Affected section.

1.0

12-FEB-2007

Initial Public Release

Products Affected

Products Affected

Comments

Cisco Phones - All Cisco Phones

For 7906, 7911, 7941, 7961, 7970, 7971, please note additional workaround

Cisco Unified CallManager - 3.3(x)

Includes SR's 3.3(5)SR2 and below

Cisco Unified CallManager - 4.0(X)

Cisco Unified CallManager - 4.1(x)

Includes SR's 4.1(3)SR4d and below

Cisco Unified CallManager - 4.2(x)

Includes SR's 4.2(3)SR1 and below

Cisco Unified Communications Manager - 4.3(x)

Cisco Unified Communications Manager - 5.0(4)

Cisco Unified Communications Manager - 5.1(x)

Cisco Unified Communications Manager - 6.0(x)

Problem Description

Daylight Saving Time changes have been mandated by the Energy Policy Act of 2005 (H.R.6.ENR), Section 110. These changes will go into effect in March 2007.

The Operating Systems of most Cisco products that support Daylight Saving Time have built in mechanisms to automatically change the times, based on CURRENT United States rules. Once the new Act is implemented, the time on devices that maintain time zone information will continue to change according to the OLD rules, unless changes are made.

Background

On August 8, 2005, the Energy Policy Act of 2005 (H.R.6.ENR), was signed into law. Section 110 of this Act modified the time change dates for Daylight Saving Time (DST) in the U.S.

Beginning in March of 2007, DST will begin on the second Sunday of March and end the first Sunday of November.

For 2007 and beyond, the daylight saving time period will be:

2:00 A.M. on the second Sunday in March

to

2:00 A.M. on the first Sunday in November

For more information on the Energy Policy Act of 2005 please see H.R. 6. (See Section 110)

Problem Symptoms

Impact to Networking Systems

Due to inconsistencies between time zones, US Daylight Saving Time changes may impact systems events as well as other management systems relating to problem escalation. Local time may be reflected in logs and on phone displays. Therefore, not having accurately represented local time is a very big concern for most organizations. This is especially true of systems that require accurate time and time stamping for proper operations.

Workaround/Solution

If implementing the patches listed below is not an option, manual workarounds may be implemented.

Once the appropriate patches are applied, the workaround must be undone to meet compliance with the new US DST dates.

March, 2007 recommendation:

- If the customer applied a Timezone Change workaround on March 11, 2007, such as required for Time of Day routing, that will need to be un-done on April 1, 2007.

- If the customer applied the Manual Clock Advance workaround on March 11, 2007, then:

For Cisco Unified Communications Manager 3.x or 4.x, sometime after 4:01 A.M. on April 1, 2007 it is necessary to re-check the "Automatically adjust clock for DST" box and manually set the server clock to the current local time on each Cisco Unified Communications Manager cluster node.

For Cisco Unified Communications Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. The clock should have advanced ahead by one hour at 2:01 A.M. on March 11, 2007. To correct this, after 4:00 A.M. on April 1, 2007, the customer will need to manually set the server clock to the current local time on each Cisco Unified Communications Manager cluster node.

- If the customer fully patched the system for the March 11, 2007 DST start, there's no action required on April 1, 2007.

- If the customer did nothing in terms of patching or working around issues for the March 11, 2007 DST start, there's no action required on April 1, 2007. The clock would have been off by one hour starting at 2:00 A.M. on March 11, 2007, but this will automatically correct at 2:00 A.M. on April 1, 2007.

Please Note:

If you applied the four software items which were required to make a Cisco Unified CallManager system Daylight Saving Time compliant in March 2007 you will be DST compliant with Cisco Unified CallManager Database, Phone load / Device packs and JRE version listed below.

However, for the Fall time changes you MUST update the MCS OS versions due to the following defect:

CSCsh20360: Looping in System Date & Time due to Daylight saving correction:

The four software items that were required in March.

  1. Standalone CallManager Database Table update listed here or the updated Engineering special of Cisco Unified CallManager:

    ciscocm.3-3-5-2007-DST-Update.1-0-1.exe

    ciscocm.4-0-2a-2007-DST-Update.1-0-1.exe

    ciscocm.4-1-3-2007-DST-Update.1-0-1.exe

    ciscocm.4-2-1-2007-DST-Update.1-0-1.exe

    ciscocm.4-2-3-2007-DST-Update.1-0-1.exe

    ciscocm.us_dst_epa_2005-5.0.4.cop.sgn

    OR Any of these versions of Engineering Specials:

    3.3(5)ES56 or higher

    4.1(3)ES89.1 or higher

    4.2(3)ES12 or higher

    4.3(1) or higher

    5.0.4.2123 or higher

    5.1(1) or higher

    6.0(1) or higher

  2. Phone Loads updates listed below:

    8.0.4sr2s standalone phone load

    8.2.2sr1 standalone phone load

    ciscocm.3-3-DevPack-74 or higher

    ciscocm.4-1-DevPack-36 or higher

    ciscocm.4-2-1-DevPack-06 or higher

    ciscocm.4-2-3-DevPack-08 or higher

  3. JRE Patch JRE Patch: (ciscocm-2007-JRE-DST-Update.1-0-1.exe)

  4. The Windows 2000 Patches that were recommend are as follows

    2000.4.2(sr15) or higher

    2000.4.3a(sr8) or higher

    2000.4.4a(sr3a) or higher

    2000.4.5a 2000.4.5a or higher

    2003.1.1 2003.1.1(sr1) or higher

    2003.1.2a 2003.1.2a or higher

    However, you may experience this vulnerability - CSCsh20360 - in the following MCS OS versions:

    2000.4.2(sr15) or lower

    2000.4.3a(sr8) or lower

    2000.4.4a(sr3a) or lower

You may download the standalone patch "Cisco Appliance OS Daylight Saving Time (DST) 2007 Update 1.0(1)" located below to remedy this situation or you may proceed to update the Cisco Unified Communications Manager MCS OS per the release information below.

Unified Communications Manager & Voice Apps Crypto Software Archive (registered customers only)

Please see "Readme Cisco Appliance OS Daylight Saving Time (DST) 2007 Update 1.0(1)" for information regarding this patch.

If you applied the standalone DST patches in March 2007 and THEN applied another Cisco Unified Communications Manager upgrade which is is lower than the versions listed above, or any Device Package, you could nullify #1 above, the "Standalone CallManager Database Table update" patch. Please follow the recommended upgrade DST path below to permanently resolve this.

October 28, 2007 recommendation:

- If the customer applies a Timezone Change workaround on or before October 28, 2007, such as required for Time of Day routing, that will need to be un-done on November 4, 2007.

- If the customer applied the Manual Clock workaround on October 28, 2007, then:

For Cisco Unified Communications Manager 3.x or 4.x, sometime after 3:01 A.M October 28, 2007 it is necessary to re-check the "Automatically adjust clock for DST" box and manually set the server clock to the current local time on each Cisco Unified Communications Manager cluster node.

For Cisco Unified Communications Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. The clock should have fell back by one hour at 3:01 A.M. on October 28, 2007. To correct this, after 3:01 A.M. on November 4, 2007, the customer will need to manually set the server clock to the current local time on each Cisco Unified Communications Manager cluster node.

- If the customer fully patched the system for the October 28, 2007 DST end, there's no action required on November 4, 2007.

- If the customer did nothing in terms of patching or working around issues for the October 28, 2007 DST event (old enddate) or after that date, there's no action required on November 4, 2007. The clock would have been off by one hour starting at 3:00 A.M. on October 28, 2007, but this will automatically correct at 3:00 A.M. on November 4, 2007 and would have been behind one hour between October 28, 2007 3:00 A.M. and November 4, 2007.

Daylight Saving Time Solution Overview

Depending on the configuration, there are up to three software items which may be required to make a Cisco Unified Communications Manager system Daylight Saving Time compliant.

  1. Cisco Unified Communications Manager Releases

  2. Cisco Unified IP Phone firmware loads

  3. Windows 200x SR Patch

Cisco Unified Communications Manager service release (SR) update:

If any of these service releases or Engineering Special releases (ESs) are installed, then it is required that all nodes in the cluster are upgraded to the same service release or ESs version.

Current release

Recommended release

3.3(5)sr2a or lower

3.3(5)sr2c or higher

3.3(5)es36 or lower

3.3(5)sr2c or higher

3.3(5)es37 or higher

3.3(5)es56 or higher

4.1(3)sr4d and lower

4.1(3)sr5 or higher

4.1(3)es106 and lower

4.1(3)sr5 or higher

4.1(3)es107 and higher

No action required

4.2(3)sr2a or higher

No action required

4.2(3)es16 or lower

4.2(3)sr2a or higher

4.2(3)es17 to 4.2(3)es29

4.2(3)es30 or higher

4.3(1)

No action required

5.0(4) or lower

5.1(2b) or higher

5.1(1)

No action required

5.1(2a)

No action required

6.0(x)

No action required

Please go to the following link for Cisco Unified Communications Manager software downloads:

Voice Software download (registered customers only)

Cisco Unified IP Phone firmware loads:

The 7906, 7911, 7921, 7941, 7961, 7970, 7971 phones require a new phone load that incorporates the Daylight Saving Time changes. The necessary phone resolution for 2007 and higher US Daylight Saving Time is present in the following phone loads or Device Packages.

Cisco Unified IP Phone firmware load

8.2(2)sr1 standalone phone load or higher

Please go to the following link to download Cisco IP Phone Firmware:

Cisco IP Phone Firmware (registered customers only)

Device Packs:

  1. 3.3(5)DevPack 83 or higher

  2. 4.1(3)DevPack 57.1 or higher

  3. 4.2(3)DevPack 31 or higher

  4. 4.3(1)DevPack 14 or higher

The Cisco Unified Communications Manager device packs downloads are available in the Voice Software Download section under the particular Cisco Unified Communications Manager version you are running. Please go to the following link for Cisco Unified Communications Manager software downloads:

Voice Software download (registered customers only)

Windows Patch:

The Windows 2000 Daylight Saving Time patch is installed if any of these versions of MCS OSs are installed. All nodes are required to be on the same version. This patch affects Cisco Unified Communications Manager trace files timestamps and the time display on the server's console.

Windows Release

Minimum OS Release with the Windows 200x DST patch for US DST

2000.4.2

2000.4.2(sr16) or higher

2000.4.3 or 2000.4.3a

2000.4.3a(sr9) or higher

2000.4.4 or 2000.4.4a

2000.4.4a(sr4) or higher

2000.4.5 or 2000.4.5a

2000.4.5b(sr3) or higher

2003.1.1

2003.1.1(sr1) or higher

2003.1.2a

No action required

Please go to the following link to download Unified Communications Manager & Voice Apps Crypto Software releases:

Unified Communications Manager & Voice Apps Crypto Software (registered customers only)

OR

You may download the following releases from the link below:

2000.4.2(sr16)

2000.4.3a(sr9)

2000.4.4a(sr4)

Unified Communications Manager & Voice Apps Crypto Software Archive (registered customers only)

Cisco Unified Communications Manager OS Manual Workaround 3.x and 4.x

  1. On the new US Daylight Saving Time date, Logon with administrator privileges to Cisco Unified Communications Manager Windows Server (starting with Publisher).

  2. Click Start, Settings, Control Panel, Date and Time.

  3. Click on Time Zone tab.

  4. Uncheck the Automatically adjust clock for daylight saving changes check box.

  5. Click on Date and Time tab.

  6. Adjust (if needed) the time to the actual time.

  7. Click Apply or OK.

  8. Repeat steps for all servers in the cluster.

Note:

  1. If the OS has not been updated prior to Sunday October 28, 2007, uncheck Automatically adjust clock for Daylight Saving changes prior to that date.

  2. On November 4, 2007, after 03:01 A.M., move the clock back one hour and after 03:01 A.M. occurs again, check Automatically Adjust clock for Daylight Saving changes.

Please note, however, that manually adjusting the clock on Cisco Unified Communciation Manager servers could result in a conflict in time which may produce time synchronization issues. For instance, adjusting the clock during any active call would result in incorrect call duration records. Therefore, adjusting the clock is best to be done when fewest active calls are present.

Manual Workaround for Cisco Unified Communcation Manager 5.x or later

For Cisco Unified Communications Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. The clock should have fallen back by one hour at 3:01 A.M. on October 28, 2007. To correct this, after 3:01 A.M. on October 28, 2007, the customer will need to manually set the server clock (ahead by one hour) to the current local time on each Cisco Unified Communications Manager cluster node.

On November 4, 2007, after 03:01 A.M., move the clock back one hour on each Cisco Unified Communications Manager cluster node.

To manually configure the time, see

Cisco Unified Communications Operating System Administration Guide, Release 5.0(4)

Time of Day (TOD) Routing:

The following workaround shall be applied for specific configurations of Time of Day Routing.

Notice:

  1. If you are using Time of Day routing that uses type Originating Device (found under the Class of Control menu), and no time zones selected, you DO NOT need to apply this workaround.

  2. If you are using Time of Day routing that uses partitions with specific time zones, YOU MUST IMPLEMENT THE manual workaround below.

Time of Day Workaround:

  1. Under the Class of Control menu, choose the Time of Day setting.

  2. Change the time zone setting to the next western-most time zone for an decrement of one hour.

  3. You will need to keep this setting until November 4, 2007 where you will then be required to change the time zone back to the original settings.

For more information on Time of Daylight Routing, please go to the following link.

Time of Day Routing

Cisco Unified CallManager / Communications Manager with endpoints in Mexico and the United States

Note: Any customer with a cluster that supports endpoints in both Mexico and the United States running any version of CallManager/Communications Manager (where the US and Mexico DST stand-alone patches are available for download) must choose the most desired time zone adjustment and apply one of the two DST stand-alone patches, but not both. If both patches are applied, the last patch installed will take precedence.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsh39509 (registered customers only)

DST for Mexico Timezones (PST and MST)

CSCsf07523 (registered customers only)

DST for N America

CSCsg85605 (registered customers only)

Daylight Saving Time for Western Australian

CSCsh44003 (registered customers only)

DST change does not take effect for Timezone Atlantic Time (Canada)

CSCsh81747 (registered customers only)

Callmanager Time of Day routing not updated with Daylight Saving Time patches

CSCsh12444 (registered customers only)

Time zone rules do not update correctly on 3rd-gen phones

CSCsi09102 (registered customers only)

7941/61 TNP time displays 1 hour early if power cycle

CSCsh68517 (registered customers only)

RTMT JVM needs new timezone data to support 2007 DST changes

CSCsh20360 (registered customers only)

Looping in System Date & Time due to Daylight saving correction.

CSCsh91735 (registered customers only)

February 2007 cumulative time zone update for Microsoft Windows operating systems

CSCsh81417 (registered customers only)

CDR Analysis and Reporting does not reflect new DST changes

CSCsf07541 (registered customers only)

MCS-OS Update needed for N America DST changes in 2007

CSCsl12482 (registered customers only)

2000 4.5a does not apply MS KB931836 for DST updates

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.