Vector using time-of-day won't account for DST

[JoeatTrends]

For our main line we have a VDN and Vector setup with a rule to forward to a "we are closed" announcment if the time of the day is outside the business hours.

With the Daylight savings finally figured out (it increments forward not backwards the way it feels for me in real life anyway) it now is not accounted for in the vector. ie. System time on the Definity 8700 is 7:30 am , daylight savings is in effect so it is really 8:30 am. The vector however says that the office is closed still though even though it is set to open at 8:30.

Is there a solution to this, or am I the only one who has experienced this? I think I may just go back to manually changing the time twice a year instead of manually changing my vector twice each year. Thanks for any help.

 

[namesrhard2pick]

I suspect your daylight savings rule might be wrong. Should be like the following:


Rule Change Day Month Date Time Increment

0: No Daylight Savings

1: Start: first Sunday on or after March 8 at 02:00 01:00
Stop: first Sunday on or after November 1 at 02:00

Also, do a display time and make sure your you have a dayligh savings rule configured.

Daylight Savings Rule: 1

 

[FSI]

newer CM loads also have a per-VDN DST setting on page 3 of the VDN form:

VECTOR DIRECTORY NUMBER

VDN VARIABLES*

Var Description Assignment
V1
V2
V3
V4
V5


VDN Time-Zone Offset*: + 00:00
Daylight Savings Rule*: system

 

[JoeatTrends]

I actually had it that way before. Please let me know if it is correct. I found that with that way the increment is actually incrementing forward. so I swapped the start and stop dates and it seemed to work perfectly.

When I do display time in site administrator it shows the rule I set in daylight savings rule (2) but the type is always standard and it won't let me change that when I do set time. The time it shows is actually the time currently minus one hour. The phones however, display the correct time with the daylight savings rule being used.

The vector however doesn't use the time the phones do. I may have to check this but I believe we have firmware version R011x.03.0.526.5 could that be an issue with that?