Implementing the Time of Day Clock Synchronization feature
360 Communication Manager Guide to ACD Call Centers
The table shown above demonstrates the importance of normalizing all local times to
Standard Time when calculating time offsets. The unadjusted time difference between
Denver and New York is 2 hours, and the calculated offset is minus 2 hours.
However, despite the fact that the unadjusted time difference between New York and
Phoenix is 3 hours, the calculated offset is also minus 2 hours - the same offset value that
is calculated for New York and Denver.
Determining synchronization run times
After you have calculated accurate offset values, you can determine when the
synchronization task should be scheduled to run on the Avaya Site Administration client
PC. Again, the most reliable method is to normalize all local times to Standard Time
equivalents.
The following table shows how to obtain to obtain synchronization task run times from the
switch locations used in this example. The task run times represent the values that would
be entered in the Scheduler dialog in Avaya Site Administration.
Client PC (New York)
Switch 3 (Phoenix)
Local time:
Local time:
06:00 EDST
03:00 MST
Adjusted Standard Time:
Adjusted Standard Time:
05:00 EST (New York)
03:00 MST
-2
Client PC (New York)
Switch 4 (London)
Local time:
Local time:
06:00 EDST
11:00 BST
Adjusted Standard Time:
Adjusted Standard Time:
05:00 EST
10:00 BST
+5
Example offset calculations used in Time Synchronization scheduling
(continued)
Local Time / Normalized Standard Time
Calculated
offset value
