Avaya Communication Manager Administrator's Manual page 1727

SNTP compliant software is available on Windows 2000. This software runs a system service that can be
started up at system boot time. Windows 2000 uses Registry entries to set SNTP parameters. Avaya will
not support the optional use of a Microsoft network domain controller as the primary time server.
Use of Time of Day information by
Communication Manager
Communication Manager features use the time of day information for a variety of reasons.
•
Time stamp data elements (CDR records, error logs, Message Sequence Trace data, MCT records,
BCMS, and CMS data)
•
Set time-out intervals (Automatic wakeup messages, Do no disturb intervals)
•
Schedule tasks (scheduled maintenance, moving CDR data to the output file)
•
Synchronize time of day information with other processors (periodic TOD messages sent to the
860 processor on the S8100 Media Server processor circuit pack)
The time of day value used for the Communication Manager server's time is essentially local time with or
without daylight savings time adjustments.
S8100 Media Server uses the Windows 2000 and S8700 Multi-Connect uses LINUX as the platform
operating system. The use of the system clock from the platform OS is transparent. Both Windows and
LINUX use UTC for the system (software) clock. Library functions and APIs are used to express the time
in local time. Communication Manager code still uses local time. However, the daylight savings rule for
system time is controlled by the OS. This is accounted for by using the time adjustments from the OS for
Daylight Savings Rule 1. The display of this rule on the System Access Terminal Daylight Savings Rules
screen is display-only. The values displayed for the time adjustments are read from the operating system.
In legacy DEFINITY when a change is made to the system time because of a manual change on the Set
Time SAT screen or because of an adjustment for daylight savings time, certain DEFINITY applications
that need to know about the change are notified before the change is made to the system clock.
If you do not have Internet access, you can continue to manually set the time of day.
CAUTION:
Avoid setting the time manually while the TOD clock sync feature is enabled. Manually
setting the time, while NTP/SNTP is running, defeats the purpose of synching the UTC
time and could cause problems depending on the difference between the system time and
UTC.
Setting time of day clock synchronization
The recommended configuration for ASA PC and time synchronization:
1
The PC clock is to be set to the local time including applying the local daylight savings time
(DST) rule.
2
The offset for each server is to be set based on the difference between the local ASA PC standard
time and the server's standard time (for example, use offset of "plus 1 hour" if ASA PC standard
time is 02:00 when the server's standard time is 03:00 per existing operation.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Time of Day Clock Synchronization
1727