|
|
|
|
Joined: Mar 2006
Posts: 1,596
Member
|
OP
Member
Joined: Mar 2006
Posts: 1,596 |
The systems were 2.01 and 2.03. This past sunday, the systems set themselves back an hour. It wasn't much to fix (they're configured for remote access), but some time ago, NEC told me that all system were compliant with the new DST.
I wonder if the problem was with the Time Server...
Any ideas?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Mar 2006
Posts: 1,596
Member
|
|
OP
Member
Joined: Mar 2006
Posts: 1,596 |
Just on a hunch...I did a test...
I think the problem is with the time server...
|
|
|
|
|
Joined: Dec 2004
Posts: 5,722
Member
|
|
Member
Joined: Dec 2004
Posts: 5,722 |
Same here....2.03. Not compliant with the new DST.
Ken
---------
|
|
|
|
|
Joined: Aug 2006
Posts: 201
Member
|
|
Member
Joined: Aug 2006
Posts: 201 |
You're correct. There's a problem with the time server software. It's not using the new DST dates. Please upgrade to version 2.06, which is on necdsx.com today. Sorry for any inconvenience.
|
|
|
|
Forums84
Topics94,284
Posts638,771
Members49,765
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
144
guests, and
347
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
