Field Notice: FN - 70394 - Unified Communications Platforms, Time Zones Not Updated in Database Correctly - Software Upgrade Recommended

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	Publish Date	Comments
1.0	14-Mar-19	Initial Release

Products Affected

Affected OS Type	Affected Software Product	Affected Release	Affected Release Number	Comments
NON-IOS	Unified Communications Manager / Cisco Unity Connection Updates	UCM v10	10.5(1), 10.5(1)SU1, 10.5(1)SU1a, 10.5(2), 10.5(2)SU1, 10.5(2)SU2, 10.5(2)SU2a, 10.5(2)SU3, 10.5(2)SU3a, 10.5(2)SU4, 10.5(2)SU4a, 10.5(2)SU5, 10.5(2)SU6, 10.5(2)SU6a, 10.5(2)SU7, 10.5(2)SU8	Affected products include Cisco Unified Communications Manager, Cisco Unity Connection, and Unified Communications Manager Session Management Edition
NON-IOS	Unified Communications Manager / Cisco Unity Connection Updates	UCM v11	11.0(1), 11.0(1a), 11.0(1a)SU1, 11.0(1a)SU2, 11.0(1a)SU3, 11.0(1a)SU3a, 11.0(1a)SU4	Affected products include Cisco Unified Communications Manager, Cisco Unity Connection, and Unified Communications Manager Session Management Edition
NON-IOS	Unified Communications Manager / Cisco Unity Connection Updates	UCM	11.5(1), 11.5(1)SU1, 11.5(1)SU2, 11.5(1)SU3, 11.5(1)SU3a, 11.5(1)SU3b, 11.5(1)SU4, 11.5(1)SU5, 11.5(2)	Affected products include Cisco Unified Communications Manager, Cisco Unity Connection, and Unified Communications Manager Session Management Edition
NON-IOS	Unified Communications Manager / Cisco Unity Connection Updates	UCM	12.0(1), 12.0(2)	Affected products include Cisco Unified Communications Manager, Cisco Unity Connection, and Unified Communications Manager Session Management Edition

Defect Information

Defect ID	Headline
CSCvo62469	SELinux Denials May Prevent DST Updates
CSCvo26979	DST updater doesn't consistently update TzDataCSV.csv file
CSCvo72807	CUC Time Zone Does'nt Get Updated when cron is scehduled for performing DST changes

Problem Description

Some geographic locations have a local time zone rule where the Daylight Savings Time (DST) start date is on the fifth Sunday of the month in which DST occurs. The issue described in this field notice impacts products in time zones where DST starts in any month that has five Sundays. In 2019, because there are five Sundays in March and September, affected products’ DST time zone rules are not updated to account for five Sundays. The result is that some features start or end DST a week earlier than expected.

Background

Cisco has identified an issue where SELinux blocks a script that automatically runs on January 10th each year at midnight. Due to this issue, the script does not update the TzDataCSV.csv file in the TFTP directory and the typetimezone database table with the correct value for the start of DST. The time zones impacted are those where the time zone rules state that the time change happens on the last Sunday of the month. In some years a month will have four Sundays and other years the same month will have five Sundays.

For example, the Europe/Brussels time zone starts DST on the last Sunday of March. In 2018 that was the fourth Sunday and in 2019 that is the fifth Sunday. The script was designed to make these types of updates, but it does not execute properly.

Problem Symptom

For Cisco Unified Communications Manager (CUCM) and Session Management Edition (SME), the issues are:

• Devices registered in certain time zones will display the incorrect time on the LCD.
• Time of Day Routing, Call Park, Call Pickup and Single Number Reach (SNR)/Mobility will not follow the configured schedule times.

For Cisco Unity Connection (CUC), the issues are:

• Schedules used by different features might have the incorrect time.
• Notification schedules configured for user devices might not be properly followed.

Workaround/Solution

For Cisco customers that have any devices registered in time zones where the local rule is that DST changes on the last day of any month in calendar year 2019, it is recommended that you follow the instructions in the How To Identify Affected Products section in order to verify your current time zone data.

After you have determined whether you are affected by this issue, Cisco recommends that you install the COP file(s) listed in the Workaround section on all server nodes in the cluster. See the ReadMe file for installation instructions.

CUCM and SME

Workaround

In order to address this issue for the rest of 2019, install the ciscocm.CSCvo62469-CSCvo26979-Workaround_C0002-1.cop.sgn file:

CUCM / SME Version 10.5(X) Software Download page

CUCM / SME Version 11.5(X) Software Download page

CUCM / SME Version 12.0(X) Software Download page

Note: CUCM and SME Version 11.0(X) have reached end of software maintenance. Customers with CUCM or SME Version 11.0(X) must upgrade to the latest version of 11.5(X). See the CUCM upgrade procedures for more information.

End-of-Sale and End-of-Life Announcement for the Cisco Unified Communications Manager and Session Management Edition Software 11.0

Solution

The fix for this issue is under development and will be posted to the Cisco Software Download site at a future date. Check the Known Fixed Releases field of Cisco bug ID CSCvo62469 for updates.

 

CUC

Workaround

In order to address this issue for the rest of 2019:

For Version 10.5(X), use this 2018g-1 COP file or any later TZ COP file from the CUCM / SME Version 10.5(X) Software Download page.

ciscocm.dst-updater.2018g-1-el6-00.10.5.2.cop.sgn

For Version 11.5.X, use this 2018g-1 COP file or any later TZ COP file from the CUCM / SME Version 11.5(X) Software Download page.

ciscocm.dst-updater.2018g-1-el6-00.11.5.1.cop.sgn

For Version 12.0.X, use this 2018g-1 COP file or any later TZ COP file from the CUCM / SME Version 12.0(X) Software Download page.

ciscocm.dst-updater.2018g-1-el6-00.12.0.1.cop.sgn

Note: CUC Version 11.0(X) has reached end of software maintenance. Customers with CUC Version 11.0(X) must upgrade to the latest version of 11.5(X). See the CUC upgrade procedures for more information.

End-of-Life Announcement for the Cisco Unity Connection 11.0 Software

Solution

The fix for this issue is under development and will be posted to the Cisco Software Download site at a future date. Check the Known Fixed Releases field of Cisco bug ID CSCvo72807 for updates.

How To Identify Affected Products

CUCM and SME

Use these admin CLI commands in order to determine if the TzDataCSV.csv file and the typetimezone database entries are correct for the Brussels time zone for 2019. (Brussels is shown as a specific example. If Brussels is correct, all other time zones will be correct.)

An example of an incorrect time zone entry in the TzDataCSV.csv file is shown here. The correct entry for calendar year 2019 is "0/3/0/5,02:00:00:00". If it returns "0/3/0/4,02:00:00:00", then you must install the COP file mentioned in the Workaround section.

admin:file search tftp TzDataCSV.csv Brussels

"TIMEZONE_EUROPE_BRUSSELS","Europe/Brussels","60","0/3/0/4,02:00:00:00","0/10/0/4,03:00:00:00","60","Europe/Brussels"

An example of an incorrect time zone entry in the typetimezone database table is shown here. The correct entry for calendar year 2019 is 0/3/0/5,02:00:00:00. If it returns 0/3/0/4,02:00:00:00, then you must install the COP file mentioned in the Workaround section.

admin:run sql select dstdate from typetimezone where enum='27'

dstdate

===================

0/3/0/4,02:00:00:00

 

CUC

Use this admin CLI command in order to determine if the tbl_timezone database entries are correct for the Brussels time zone for 2019. (Brussels is shown as a specific example. If Brussels is correct, all other time zones will be correct.)

An example of an incorrect time zone entry in the tbl_timezone database table is shown here. The correct entry for calendar year 2019 is 5. If it returns 4, then you need to install the COP file mentioned in the Workaround section.

daylightstartweek

admin:run cuc dbquery unitydirdb select daylightstartweek from tbl_timezone where tzname='Europe/Brussels'

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

4

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:

• Open a service request on Cisco.com
• By email
• By telephone

Receive Email Notification For New Field Notices

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