More time/Daylight savings problems

[rejackson]

I came in this morning and my phone had the right time here in Dallas. Then I started getting calls from locations that should not have gone on daylight savings about their phones showing time 1 hour ahead. I looked at their DST rules and they were correct. The one that is wrong is my time zone. I did not update it for this year and it still says to start the first Sunday on or after March 9th. So DST in my location has not started yet. The disp time shows the correct time but says it is standard time. The system platforms show the correct time but say it is daylight time. I do not see any settings in the system platforms related to DST.

At this point I don't want to correct my DST table because I think all the phones using the table will jump ahead 1 more hour. In another week it may do that on its own when it hits the schedule on next Sunday. I don't know if there is a setting in the CM platforms or CM itself that will correct what time the CM is using.

If anyone has any ideas I would appreciate hearing them

Richard
Lost in time.....

 

[AvayaTier3]

Hardware platform? Software version?
Your main server timezone?
output from Linux command?
Command: /usr/sbin/zdump -v /etc/localtime | grep 2015



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[rejackson]

Proliant DL360 G7
CM_Duplex 6.2.0.0.3086 (cm 06.2-02.0.823.0)
Central time
CDom and DOM 6.2.2.09001.0

[Ryan@acm-a-cdom ~]$ /usr/sbin/zdump -v /etc/localtime | grep 2015
/etc/localtime Sun Mar 8 07:59:59 2015 UTC = Sun Mar 8 01:59:59 2015 CST isdst=0 gmtoff=-21600
/etc/localtime Sun Mar 8 08:00:00 2015 UTC = Sun Mar 8 03:00:00 2015 CDT isdst=1 gmtoff=-18000
/etc/localtime Sun Nov 1 06:59:59 2015 UTC = Sun Nov 1 01:59:59 2015 CDT isdst=1 gmtoff=-18000
/etc/localtime Sun Nov 1 07:00:00 2015 UTC = Sun Nov 1 01:00:00 2015 CST isdst=0 gmtoff=-21600
[Ryan@acm-a-cdom ~]$

Thanks for the response. I can understand the platforms needing to know the correct time. I don't see how they are configure to give it to the CM hosts. This is the web display from the active CM

Server Date/Time
The Server Date/Time page displays the current date, time and timezone.
The current time is Mon Mar 9 14:04:51 CDT 2015

and this is the disp time

DATE AND TIME

DATE

Day of the Week: Monday Month: March
Day of the Month: 9 Year: 2015

TIME

Hour: 14 Minute: 7 Second: 11 Type: Standard

Daylight Saving Rule: 1

 

[AvayaTier3]

CM daylight-savings-rules needs to be change from March 9 to March 8 for the current rules to work
or

You could add a new rule using March 8 and November 1
then change locations to use the new rule number

The Linux server time and zone are correct because the activation is built into the /etc/localtime file

In earlier software versions like cm4 and earlier, DST patches had to be unpacked, activated to update the /etc/localtime files.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[mattKnight]

It seems to me that you are fighting against methods of setting daylight savings

Isn't it easier to adopt a server time of UTC (or one with DST) and then use Daylight savings time rules to apply the correct timezome on a location by location basis for the "application"?



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[rejackson]

Thanks Tier3

I corrected the entry in the first DST table last night and the time did not jump forward another hour like I thought it might. Logged a phone out and back in to make sure. The Disp Time shows DST is on now. Amsterdam and London are now reporting they have the correct time. They are on tables 2 and 3. There is something very odd about how Avaya processes those tables. When DST started but the tables did not show to start it at any of the locations yet it just added an hour to all locations. As soon as I corrected the first entry it also started to use entries 2 and 3 correctly.

 

[AvayaTier3]

# system maintenance update clocks on voice terminals is controlled by
# System Updates Time On Station Displays? y
# If set to n, they will not be updated by CM
# Maintenance updates time on stations and there is no way to predict how long it takes for
# all stations to be updated. It will vary with size of system.
# You can force update with depression of "date-time" button on phone.

display system-parameters features                              Page  10 of  17
                        FEATURE-RELATED SYSTEM PARAMETERS

                 Pull Transfer: n            Update Transferred Ring Pattern? n
         Outpulse Without Tone? y              Wait Answer Supervision Timer? n
         Misoperation Alerting? n               Repetitive Call Waiting Tone? n
    Allow Conference via Flash? y
 Vector Disconnect Timer (min):       Network Feedback During Tone Detection? y
                                     [COLOR=#CC0000]System Updates Time On Station Displays? y
[/color]

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]