Do holiday tables take account of daylight savings rules?

[nickd87]

We are running CM 3.1.2 and would like to know if CM takes account of the daylight savings rule for a location when considering times listed in a holiday table?

Thanks

NIck

 

[Tolson]

Yes they do. They look at the system time which has already been adjusted for DST.

 

[nickd87]

That's interesting because what I'm seeing happen means it isn't adjusting the time.

Eg VDN 1234 with daylight savings rule 2 set, no offset on the VDN. Daylight savings rule 2 offsets the time by one hour from the system time.

Holiday table 1 set up with a holiday from 03/21 10:00 - 03/21 11:00.

Example: System time is 10:05, so VDN time should be 11:05. Call comes into VDN 1234 and there is a step in the vector "goto step 3 if holiday in table 1". The call then skips to step 3, even though it shouldn't.

 

[definityandcmuk]

Try setting the VDN offset to +1hr and not using the daylight savings rule 2 see if this works

sounds like something isn't configured correctly in the daylight savings

 

[nickd87]

Thanks, I just tried that and it still isn't taking account of the offset set on the VDN.

 

[nickd87]

I've just had a look at the "Call Vectoring and EAS Guide" for Call Center Release 3.1, and it had this to say about Holiday Tables:

"The date and time match is done at the time that the call is in vector processing. It is done just like time-of-day routing. This means that it is checking the system date and time on the Processor Port Network (PPN), rather than the local port network time on the Expansion Port Network (EPN). "

What does this mean? I thought that it means it would use the time for the port network that the call is in, which should still be the offset time?

 

[nickd87]

Just confirmed with Avaya - holiday tables do NOT take account of daylight savings rules or time offsets on VDNs. They use whatever the system time is.