Service Hours Table Offset

[Ratman01]

Our two main servers are in central time. We have call centers in Central time and in Eastern time. I have a service hours table that has the TOD as 8:00 to 17:00 and it says use time adjustments from location 1 (our main server).

My VDN's for Central Time work fine. However, for Eastern time I have created a VDN with an offset of +01:00 and it does not adjust the value from the service hours table. If I hard code the hours, they do the offset but I would like to use the service hours table. Am I missing something?

We are on CM 5.2.
Below is my test VDN. (Production right now is hard coded because I can't get this to work.)

VECTOR DIRECTORY NUMBER

Extension: 123-4567
Name*: cjptest
Destination: Vector Number 1997
Attendant Vectoring? n
Meet-me Conferencing? n
Allow VDN Override? n
COR: 20
TN*: 1
Measured: none

Service Objective (sec): 20
VDN of Origin Annc. Extension*:
1st Skill*:
2nd Skill*:
3rd Skill*:
VECTOR DIRECTORY NUMBER

AUDIX Name:

Return Destination*:
VDN Timed ACW Interval*:
BSR Application*:
BSR Available Agent Strategy*: 1st-found
BSR Tie Strategy*: system

Observe on Agent Answer? n


Display VDN for Route-To DAC*? n
VDN Override for ASAI Messages*: no

BSR Local Treatment*? n

Reporting for PC Predictive Calls? n
Pass Prefixed CPN to VDN/Vector*? system
VECTOR DIRECTORY NUMBER

VDN VARIABLES*

Var Description Assignment
V1
V2
V3
V4
V5
V6
V7
V8
V9

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

 

[SloTCMS30]

Ratman,

Are you using time offsets in the locations table? Or the tennants?

“Do not spoil what you have by desiring what you have not; remember that what you now have was once among the things you only hoped for.”

- Epicurus

 

[Ratman01]

Location table. We do not use tennants.