IP Office DST setting 24

[jamie77]

I'll admit to never looking at this at all becuase it always 'just worked', but we have noticed that the preprogrammed dates all come to an end this year, for evrybody in the world!!

After speaking with Avaya, it seems theses dates are pulled from a file in the manager folder called timezoneinfo.xml. This file includes dates for all times zones upto 2025, but the there are too manay entries in each list emaning the IPO only loads upto 2023.

This file hasn't been updated by Avaya ever, so with a brand new IP500 installation, your DST will end this year.

I'm waiting on Avaya to tell me if they are going to update the file with a future release of Manager so we can update all our customers easily. Lets see if they do or not!

Bw warned. All your IP500 customers will run of DST dates this year, unless you have set them yourself.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[Bolinious]

I never changed between time zones and back. just did the XML file (my own manual and the downloaded one above) to try and make the auto DST work.


I only have remote access and will only be able to try more after normal business hours. does the time zone change require a reboot or will that work like when I manually changed to -4 instead of the normal -5 DST setting?

 

[lleeNC]

@Bolinious

Nope, just need to swap time zones without merging and then it should update. Once it updates, merge. No reboot required for the Manager method (putting the xml in the Manager folder).

 

[Bolinious]

thank you. i'll try changing time zone outside of business hours and back.

 

[JMC1]

agreed, definitely need to change to a different timezone, then go back to your preferred timezone to be able to see the new entries.

 

[tac84]

Thanks, @lleeNC for your reply.

Re the question why do I have different years in a single entry? - do you mean because it has it over 1/10/2023 to 7/4/2024? That's the daylight savings period here in Australia. October through to April.

Time server is resolving fine in System Status so not sure what is going on.

Thanks, Tim
Adelaide, Australia

 

[Westi]

@tac84
For me I have to always change the time zone to something else and then click OK and then go back (like lleeNC) before it takes the new schedule.
The file from BFG9K has the Adelaide entries in it so it should work. Not sure why yours is so stubborn.

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[mjroam]

Thanks Westi
Your file worked great for EDT US.

 

[CASSBusinessSystems]

Thank you, everybody. This really helped us.

 

[tac84]

Thanks @Westi
I managed to get this working, however I had to upload @BFG9K's TimeZoneInfo.xml to the following places:

- \SYSTEM\PRIMARY\WebMgmtEE\TEST\XML- \SYSTEM\PRIMARY\WebManagement\TEST\XML
Once I uploaded the file to both locations, rebooted the IPO and logged back in, everything corrected itself and started working.

Thanks again everyone for helping.

Thanks, Tim
Adelaide, Australia

 

[teletechman]

The files I have downloaded do not work for PST in the US. I just tried to update a site in California and it showed blank when I clicked on PST for the time zone? Does anyone have one that works for the PST time zone?
Mike

 

[Westi]

I had a look into the xml file and it is there so it is your system being stubborn

<TimeZone><Name>(GMT-08:00) Pacific Time (US &amp; Canada)</Name>
<Locale>esm</Locale>
<UTCOffset>28800</UTCOffset>
<DSTEntries><Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/13/2022 2:00:00 AM - 11/6/2022 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/12/2023 2:00:00 AM - 11/5/2023 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/10/2024 2:00:00 AM - 11/3/2024 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/9/2025 2:00:00 AM - 11/2/2025 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/8/2026 2:00:00 AM - 11/1/2026 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/14/2027 2:00:00 AM - 11/7/2027 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/12/2028 2:00:00 AM - 11/5/2028 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/11/2029 2:00:00 AM - 11/4/2029 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/10/2030 2:00:00 AM - 11/3/2030 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/9/2031 2:00:00 AM - 11/2/2031 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/14/2032 2:00:00 AM - 11/7/2032 2:00:00 AM</DSTPair>
</Entry>
<Entry><DSTOffset>01:00:00</DSTOffset>
<DSTPair>3/13/2033 2:00:00 AM - 11/6/2033 2:00:00 AM</DSTPair>
</Entry>
</DSTEntries>
</TimeZone>

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[jamie77]

Talk about leaving it until the last minute for Avay to do anything!!

https://ipofficekb.avaya.com/businesspartner/ipoffice/mergedProjects/bulletins/psn/PSN006269u.pdf

They knew about htis 12 months ago!!

Idiots!

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[Desmisclvlv]

With Nortel analog lines it was always an efficient way to get the current date by capturing it from the caller ID on every call. Is it possible with a via to do this or is it possible to capture the current time and date from a PRI call they both include the time and date of the incoming caller ID time stamp?

 

[aarondyck]

I saw this coming years ago and created a fix. You can follow the instructions here:

https://www.adventuresinvoip.ca/2021/03/automatic-daylight-savings-time-update.html

The TL;DR is that you download the file, extract it, then import the configuration for your time zone. The only configuration items it touches are the DST dates and times.

https://bovaird.ca/