I could be wrong, but I always assumed NTP servers don't consider time zones when providing time information to NTP clients. I would assume it would be up to the client to adjust the time for the proper time zone.
Nabeel > -----Original Message----- > From: Dave Donovan [mailto:[EMAIL PROTECTED] > Sent: February 13, 2007 12:37 AM > To: asterisk > Subject: [on-asterisk] Discuss: Asterisk and DST change > > This Daylight Saving Time change coming up in a month isn't > anything on the scale of Y2K but it makes me think the many > places where little calculations are made with timestamps. > Our Blackberries are going to be a pain. > > I'm just curious to see what people are thinking about this. > It seems like there hasn't been much buzz and many people > I've asked haven't given it much thought. I think it's > almost like there will be 3 timezones. EST, EDT and Energy > Saving EDT. > > Has anyone run into issues with Asterisk? > > Obviously, any custom scripts that depend on remote servers > are a concern but, other than VM timestamps, and maybe some > least cost routing, are there obvious applications/features > that you can think need careful consideration? > > Do you trust your upstream NTP server? Imagine if you > patched your system and they didn't patch theirs. > > How often do your phones poll for NTP sync? Is it often > enough that it'll get synced up before your users come in or > do you have to check to make sure your firmware is going to > handle the change itself. > > Tell us what you think. > > Dave > >
