Avaya Communication Manager Administrator's Manual page 1728

Feature Reference
Time of Day Clock Synchronization
3
Schedule the task to occur no more often than every 24 hours at a low traffic time period based on
the local time at the server running Communication Manager and in the middle of a BCMS/CMS
interval being used at the server (for example, 11:07 PM or 3:07 AM). Also the time picked
should not be set to a time period when Communication Manager nightly maintenance is
scheduled to be run or the BCMS next day period starts. Note that the time ASA uses to decide
when to send the time change is based on the local PC time including DST when applicable.
Therefore the start time and interval entered for a serve must be based on the server's local time
converted to the PC's local time.
Running the task more frequently (for example, every 12 hours) makes it more difficult to have it
run during a low traffic period or it could cause the scheduled time to occur at different times
during the day as time goes on (for example, picking any entry other than Every 24 hours or 12
hours will make the scheduled time "creep" over the day by the selected time interval since only
the start date-time and repeat interval can be specified). The use of the Weekly or Monthly
Recurrence Patterns does not have the "creep" problem.
4
Note that ASA must be running and OSSI connectivity to the media servers or switches must be
available (via LAN or dialup) during the scheduled times for synchronizing ASA's
Communication Manager servers.
The recommended configuration for each Communication Manager server time synchronization:
1
The system clock may be set to either local time using automatic DST changes, local standard
time (without DST changes - DST Rule set to 0) or GMT time (without DST changes). In the case
where automatic DST changes is not assigned to the system clock (that is, the DST rule is set to 0
on the Date and Time screen), you can use the Multiple Locations feature to display DST (and
local time in the case where the system time is set to GMT) on the station sets homed on the local
port networks. However, all Communication Manager reports (including BCMS),
CMS/Supervisor reports, TOD routing and scheduled events will be based on the system clock
time not the location time. It is expected that in most cases the system clock will be set to local
time with DST change. In each case, the ASA- assigned offset for Communication Manager will
provide the proper conversion from PC time to the desired system clock standard time.
2
In all cases the Multiple Locations feature provides local time display on station sets based on the
local time zone and DST rule in effect at the remote port network (EPN) site. The time determined
by the location assignments also applies to do-not-disturb, Automatic Wakeup programming and
execution (however, the announced time is the system time).
3
Each of the configuration possibilities is summarized as follows:
a
System time set to local time with automatic DST changes (when observed in
that area) - Use the Date and Time screen to set the time for the local time zone and the
DST rule defined on the
manually to the local standard time during fall/winter/spring or to the local DST time in
the summer. If DST is not observed then the following configuration b would be used. All
reports and display station sets will show the local time with the DST rule applied. TOD
routing/scheduled events occur based on the system clock (which will be in the local
standard time or local DST depending on the time of the year). Use the Multiple Locations
feature to display local time on station sets at remote sites.
b
System time set to local time without DST rules - the Date and Time screen has
the standard time for the local time zone set and the DST rule field is set to 0 . All reports
and TOD routing/scheduled events are all based on local standard time regardless of
whether DST is being observed or not. Display station sets at the local PPN and remote
EPN sites can have actual local time (with DST applied) via the Multiple Locations
feature.
1728
Daylight Savings Rules
Administrator's Guide for Avaya Communication Manager
screen. The time initially can be set
November 2003