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

 

[Nortel4Ever]

Oh, nevermind I got it figured out.

 

[Westi]

I am glad, I was on the road and just came back into the office so missed your post until now.

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[BFG9K]

Just going to post this cleaned up version of Westi's global TimeZoneInfo.xml file, there were a few missing tags etc.

To apply to an IPO500:
[ul]
[li]Upload this file to \SYSTEM\PRIMARY\WebMgmtEE\TEST\XML\ on the IPO500 SD Card (backup and replace the existing TimeZoneInfo.xml file already there)[/li]
[li]Reboot the IPO500[/li]
[li]Close and re-open Manager and log into the IPO500 after the reboot[/li]
[li]The updated time zone data should now display under System > Time Zone, if it doesn't, select another random time zone and then back to your one, it should then update.[/li]
[/ul]

To apply to your local Manager to work on offline configs:
[ul]
[li]Close Manager if it is open[/li]
[li]Copy this file to C:\Program Files (x86)\Avaya\IP Office Admin Suite\Manager\ (backup and replace the existing TimeZoneInfo.xml file already there)[/li]
[li]Reopen Manager and open a config[/li]
[li]The updated time zone data should now display under System > Time Zone, if it doesn't, select another random time zone and then back to your one, it should update.[/li]
[/ul]

Thank you Westi for doing the hard work for us

Cheers,
BFG9K
Avaya IPO/ACCS Technician
Melbourne, Australia

 

[Westi]

You are the man

I did the initial work in a hurry and completely forgot to get back and fix it.
If you see pink it is from another star not a forest fire in the distance.

Joe
FHandw, ACSS, ACIS

 

[Nortel4Ever]

...and again I have to wonder why Avaya couldn't have kept this updated with each software release. I guess because they were too busy fixing their screw-ups from every previous release...

 

[Westi]

I guess that Avaya has laid off the guy that was responsible for this years ago and they forgot to have a new person in charge of that.
The same with their certificates and the fact that they did not keep that up to date either.
Probably the same person, HAHAHA

Joe
FHandw, ACSS, ACIS

 

[sizbut]

I've already given a star and would give another if I could. So not knocking, this is excellent work and thanks for sharing, but for a few locales a few warnings are needed:

[ul]
[li]Brazil: Stopped DST in 2019.[/li]
[li]Eygpt: Started DST in 2023.[/li]
[li]Morocco: Switched to permanent DST (UTC+1) in 2018.[/li]
[li]Russia: Stopped DST in 2014.[/li]
[li]Turkey: Switched to permanent DST (UTC+3) in 2016[/li]
[/ul]

Today is busy but if time allows Monday I'll try to post a corrected version for those odd locales.

...and then there's those pesky Americans, who've half-passed a law to stop DST, but only half! Strange people.

Stuck in a never ending cycle of file copying.

 

[sizbut]

 

[sizbut]

Okay, that took long than expected (finding both the time to do it and doing it).

Changes:
[ul]
[li]Made the file a bit more human readable (though sadly Manager doesn't like comments in the file).[/li]
[li]Removed 2022 - it's happened.[/li]
[li]Fixed the missing 2026 DSTOffset value for the nlb,frb,dan,fra,esp locales.[/li]
[li]Removed all the DST settings for unsupported locales (would anyone ever see them?).[/li]
[li]Removed the DST settings for Brazil and Mexico. They stopped DST in 2019 and 2022 respectively.[/li]
[li]Added DST for Egypt (they started this year).[/li]
[li]Moved Turkey and Morocco forward an hour. They have effectively switched to permanent DST since 2016 and 2018 respectively.[/li]
[/ul]

File link below:

 

[Westi]

Nice job sizbut, I already have replaced my North America only file with yours.
pink for you.

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[Nortel4Ever]

@sizbut,I'm wondering if there is a way you could monitize this DST file for yourself and sell it to Avaya for wider distribution.

 

[sizbut]

I still have some contacts inside the ever shrinking development team, so to repay favours its heading that way anyway.

Stuck in a never ending cycle of file copying.

 

[JMC1]

Guys, I've followed these steps (I think?) And put in the modified xml file but the drop down list hasn't changed.

Ive rebooted, closed config, opened config, to no avail.

Can someone point me to where I might be going wrong?

 

[Richard10d]

I only post to say what I did using what was said above in the hopes it makes it as simple as possible for someone else.

I used BFG9K's solution at first. I found that if I use that XML file and fixed my manager, I could connect to all my customers systems and simply re-choose the TZ and save it. My steps were:

1. With Manager closed, copy the excellent TZ file from BFG9K into c:\blah\Avaya\blah\manager\ to replace the original.
2. Connect to the PBX using Manager
3. On the system tab, drop down the list of TZs and choose the correct one (even if it's already highlight, you have to CLICK IT). You will see the DST ranges update from 2014 to 2022.
4. Save.

I simply repeated 2-4 for all the systems.

I had one customer where their phones on SE were using the wrong DST. I finally realized it was the location settings. I did the same thing for the location for that customers TZ/DST settings on one of the locations. That seemed to fix all of the other locations. (Probably because it uploaded the new XML file).

Hope that helps someone. AND THANK YOU EVERYONE who contributed to this very useful thread.

FYI, I chose to try and simplify based on this Avaya solution, but their XML sucks as it only adds 2 years. BFG9Ks is good through 2033:

https://support.avaya.com/ext/index?page=content&id=SOLN378136&viewlocale=en_US

 

[JMC1]

Ok. I was just putting the modified xml onto the SD card. When I put the modified xml file into manager, I get the drop down as described. That's great.

I wonder: because my computer is one of many that may connect to the ip office, what happens when a computer with a manager program that doesn't have the modified xml installed changes some programming and saves it? Does it revert back because that config will have the old DST entries in it? I feel like it will.

What if we put that same modified xml in the proper spot on the sd card? Will that prevent it from reverting back?

I will have to test.

 

[tac84]

Well done for raising this, @Jamie77.


Thanks, Tim
Adelaide, Australia

 

[tac84]

Not sure what I'm doing wrong at my end. I've uploaded the new file and the new dates are all listed.

I attempt to change the clock forward/back settings to the correct year, select it and press OK, but it just reverts back to the first option on the list and the time doesn't move forward 1:00 (+9:30 to +10:30)

Any ideas?

Thanks, Tim
Adelaide, Australia

 

[lleeNC]

@tac84

That is normal, it isn't going by the first one on the list but it's going through the entire list... if that makes sense. Also why do you have different years in a single entry?

I would also go into system status and look to see if the time server is resolving.

 

[Bolinious]

I've saved the XML in the manager directory as well as updated it on the SD card. restarted the IPO and manager, yet I still can't get it to show me the new dates in the DST offset.

I've manually changed the time offset to -4 for now. but I really need to find the fix so I can get this working automatically.

I've attempted this with both my own XML file as well as one downloaded from above. I'm not physically at the location of the IPO, so manually grabbing the SD card to put the file there is not an option at this time. but at least you can still browse it on the manager. What am I doing wrong?

 

[lleeNC]

@Bolinious

Did you try swapping between time zones? You have to swap between time zones in IPO -> System for it to update from my experience.

Let me know if you still need help and maybe we can remote with each other