Product Support Notice © 2014 Avaya Inc

Home , Anadyr (town)

Product Support Notice © 2014 Avaya Inc. All Rights Reserved. PSN # PSN004340u Original publication date: 21-Oct-14. This is Issue #01, published date: Severity/risk level Medium Urgency When convenient 21-Oct-14. Name of problem CS 1000 R7.6 – Time Zone Updates Products affected Communications Server 1000M and Communications Server 1000E – R7.6 Problem description Introduction

This PSN is issued to advise of Communication Server 1000 (CS 1000) R7.6 support for upcoming time zone and Daylight Saving Time (DST) changes.

Three updates are available for CS 1000 R7.6 (including Avaya Media Server 7.0 for CS 1000) - cs1000-Jboss-Quantum-7.65.16.23-3.i386.000 - cs1000-linuxbase-7.65.16.23-3.i386.000 - tzdata-2014g-1.el5.i386.000 Note that there is no update available for Avaya Media Server 7.6 on CS 1000 at this time.

More details on the changes included as follows. - Multiple time zone changes for Russia - Effective from October 26, 2014, 2 a.m., Russia returns to using the standard "winter" time. Russia will subtract an hour from most of its time zones. - Russia will now be divided into eleven time zones; the following Russia Time Zones are introduced as of October 26, 2014 - Russia Time Zone 1 (GMT+02:00) Kaliningrad (RTZ 1) - Russia Time Zone 2 (GMT+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2) - Russia Time Zone 3 (GMT+04:00) Izhevsk, Samara (RTZ 3) - Russia Time Zone 4 (GMT+05:00) Ekaterinburg (RTZ 4) - Russia Time Zone 5 (GMT+06:00) Novosibirsk (RTZ 5) - Russia Time Zone 6 (GMT+07:00) Krasnoyarsk (RTZ 6) - Russia Time Zone 7 (GMT+08:00) Irkutsk (RTZ 7) - Russia Time Zone 8 (GMT+09:00) Yakutsk (RTZ 8) - Russia Time Zone 9 (GMT+10:00) Vladivostok, Magadan (RTZ 9) - Russia Time Zone 10 (GMT+11:00) Chokurdakh (RTZ 10) - Russia Time Zone 11 (GMT+12:00) Anadyr, Petropavlovsk-Kamchatsky (RTZ 11) - The legacy TZ for "(GMT+12:00) Petropavlovsk-Kamchatsky -Old" is also removed - Additional information can be found at http://mm.icann.org/pipermail/tz-announce/2014-August/000023.html and https://rhn.redhat.com/errata/RHEA-2014-1242.html - Belarus Standard Time - Belarus shared a time zone setting with Kaliningrad which created a conflict due to Russian TZ changes. Minsk should be in GMT+03:00 and the data for Belarus is updated accordingly. - Turks and Caicos - Effective from November 02, 2014, 2 a.m., Turks and Caicos Islands are switching from US Eastern time to UTC-4 year-round, modeled as a switch from EST/EDT to AST. - Additional information can be found at http://mm.icann.org/pipermail/tz-announce/2014-August/000024.html and https://rhn.redhat.com/errata/RHEA-2014-1253.html - Jordan Standard Time - For 2014 and onward, Jordan has changed its DST Start time from the last Thursday in March at midnight to the last Friday in March at 1 A.M., and its DST End time from the last Friday in October at 1 A.M to the last Friday in October at midnight. - Paraguay Standard Time - For 2014 and onward, Paraguay has changed its DST End date from the second Sunday in April to the fourth Sunday in March.

- Line Islands Standard Time - A new time zone for Kiritimati Island (GMT+14) is added. - SA Pacific Standard Time - Starting on November 10, 2013, the display name is changed from "(GMT-05:00) Bogota, Lima, Quito" to "(GMT-05:00) Bogota, Lima, Quito, Rio Branco". - Mid-Atlantic Time - The Mid-Atlantic time zone is removed.

The recommended steps to apply the changes are as follows.

For Turks and Caicos - Disable Network Time Protocol (NTP) - Overlay 02 – Call Server (except Co-Res) – disable DST in advance of 2nd November - SDST OFF - Apply LinuxBase changes before 2nd November – note that this is Service Interrupting - Enable NTP again

For Russia a) If an UTC offset for a site is not changed after 26th October, appropriate Linux Base changes can be implemented in advance, no changes are needed on Call Server. b) If a time zone setting is changed by subtracting an hour in accordance with the table below, it is possible to apply the changes in advance as follows. - Disable NTP - Apply Linux Base changes before 26th October – note that this is Service Interrupting - Overlay 02 – Call Server (except Co-Res) – program the backward hour time change in advance of 26th October and the forward change on any day several months later, e.g. - BWTM 10 5 1 02 - FWTM 4 5 1 02 - SDST ON - Overlay 02 – Call Server (except Co-Res) – disable any further DST after 26th October - SDST OFF - Overlay 117 – Call Server (except Co-Res) – correct UTC offset in LD 117 if required with use of CHG UTCOFFSET command. - Enable NTP again c) Otherwise the changes on Call Server and Linux Base should be implemented after 26th October.

Other Countries – apply at convenience as required.

Ensure that any applications such as Avaya Aura® Contact Center are also considered as part of this update activity.

Time zone changes for Russia Old Time Zone New Time Zone

(GMT+03:00) Kaliningrad (GMT+02:00) Kaliningrad (RTZ 1)

(GMT+04:00) Moscow, St. Petersburg, (GMT+03:00) Moscow, St. Petersburg, Volgograd (RTZ 2) Volgograd - (GMT+04:00) Izhevsk, Samara (RTZ 3)

(GMT+06:00) Ekaterinburg (GMT+05:00) Ekaterinburg (RTZ 4)

(GMT+07:00) Novosibirsk (GMT+06:00) Novosibirsk (RTZ 5)

(GMT+08:00) Krasnoyarsk (GMT+07:00) Krasnoyarsk (RTZ 6)

(GMT+09:00) Irkutsk (GMT+08:00) Irkutsk (RTZ 7)

(GMT+10:00) Yakutsk (GMT+09:00) Yakutsk (RTZ 8)

- (GMT+11:00) Chokurdakh (RTZ 10)

(GMT+12:00) Petropavlovsk-Kamchatsky –Old (GMT+12:00) Anadyr, Petropavlovsk-Kamchatsky (RTZ 11)

Resolution Apply recommended Service Updates. Workaround or alternative remediation Not Applicable Remarks Not Applicable Patch Notes Backup before applying the patch Data dump as before any maintenance activity Download Service Updates can be downloaded via ESPL Patch install instructions Service-interrupting? As per standard documentation for CS 1000 Yes Verification Not Applicable Failure Not Applicable Patch uninstall instructions Not Applicable Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks n/a Avaya Security Vulnerability Classification Not Susceptible Mitigation n/a

© 2014 Avaya Inc. All Rights Reserved. Page 3 If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use.

Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED “AS IS”. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.