Time-change on SCCS-server

[Skaret]

When you do a time-change on M1 the time is updated on the SCCS-server automaticly.

Recently the M1 changed automaticly the time by one hour (summer-time). The problem was that the SCCS-server was not updated automaticly from M1.

Any idea what this problem is related to?

 

[Sympology]

Can't think of a reason why, should flick over, but may take a few minutes to do so. One possible thing is Summer time set on the server? It is on ours, maybe if it's not set it screws it somehow. Just a thought.

2 decades from retirement, 2 minutes from a breakdown

 

[rory1]

We had automatic daylight saving on the SCCS and it was not good. It switched over before the M1 was changed (as the M1 was not set to do so automatically) and then never really resynched afterwards.

Apparently the SCCS server should not have automatic clock changes set, but the SWCS should have it set.

R

 

[sandyml]

The SCCS takes its time update from the PBX; so the Daylight Savings Time box should not be checked. The SWCS doesn't have an ELAN connection and takes it time in the normal way.

 

[ErwinStevanus]

SKaret,

Apparently you need to restart you server after the daylight saving change.

This is what I get from NTP - Installation & Maintenance Guide

Managing the date & time - page 473

The server makes adjustments to stay synchronized with the switch time. If you attempt to change the date and time on the server, the server automatically adjusts the time back to stay synchronized with the switch. As a result, only the switch administrator can change the date and time.

During a time change from standard time to daylight saving time or from daylight saving time to standard time, the following events occur:
- Windows on the server automatically adjusts the time.
- Within 10 minutes, the server changes the time back to ensure that it is synchronized with the switch time.

Notes:
- After a change to or from daylight saving time, you must restart the server.
- During the interval between the automatic time changes, the time on realtime displays and in reports is incorrect (for example, the end times of calls in progress may be earlier than their start times).


Also during SCCS Installation, please make sure the following:

Date & Time Setting Window - page 76

Complete this window as required for your site. Make sure the correct time zone is set for the server.

For the check box Automatically adjust clock for daylight saving changes, do one of the following:
- If you are using a Meridian 1/CSE 1000 switch, ensure that Automatically adjust clock for daylight saving changes is unchecked.
- If you are using a DMS/MSL-100 switch, ensure that Automatically adjust clock for daylight saving changes is checked for regions using daylight saving time.
- If you have purchased the Network Skill-Based Routing feature and are setting the time zone for the Network Control Center server, ensure that Automatically adjust clock for daylight saving changes is checked.

 

[Skaret]

ErwinStevanus,

I have also read this information. We have several SCCS/SECC connected to different Meridian 1. Just one of them had this problem.

I can't then see the purpose of restarting the server, because the SCCS time is syncronized with the M1. If we change the time on M1 by a minute, within 10 minutes the time on SCCS is adjusted automaticly - why should we then restart the server when changed by one hour???

A question to all of you out there running M1 + SCCS and doing daylight saving changes - do you reboot the server after daylight saving changes on the M1?

 

[sandyml]

The issue with Daylight Savings time has largely been taken care of by the Service Updates. Keep in mind, though that other time changes can be detrimental. Statistics are saved to the database every 15 minutes. Potentially you can create a problem if information is already saved to one 15 minute timeframe in the database, and the server attempts to save new information to that timeframe.

Here is what the SU11 readme has to say about the DST adjustment:

A.3 Changes for Daylight Savings.

The included fixes to the CRs below remove the need to restart
HDC, RDC, SDP and IS services during a daylight saving change.
This eliminates potential problems with restarting those
services.

Q00389867 RDC,SDP,IS failure after DST set clock ahead 1 hr
Q00388427 HDC stuck at Timeout after DST set clock ahead 1 hr

Agents that are in the Idle or Not Ready state prior to the time
change will maintain this state after the change. The same
applies for calls that are not directly handled by SCCS, e.g. DN
Calls.

However it is important to note that the following exceptions for
calls that are live during the moment of time change are not
addressed by this PEP;

- An agent that was shown as being Active on Skillset X on the
Agent RTD prior to the time change,will be shown as Busy
following the time change.
- The Skillset RTD does not reflect the active state of agents
having that skillset following a time change; so if Skillset
X has 1 Agent logged in and is processing a call prior to
the time change (with the Skillset RTD consequently showing
1 Active agent for that skillset), after the time change
Skillset X will show that there is 0 Active agents.
- If a call is queued to a skillset during the time change
and then presented and answered by an agent after the
time-change, the Agent RTD will show the Agent as Idle
rather than Active as expected.

Subsequent calls after the time change will be pegged correctly.
This is expected to have minimal impact at most sites because the
Day-light savings change occurs at 2:00 am when most Call Centers
are closed or have minimal activity.

 

[ErwinStevanus]

Skaret,

First of all, I don't have any practical experience with Daylight Savings because my country does not have any

Anyway, it's pretty strange that it happened only to one SCCS Server.

A few questions:
1. Is there any difference on the setup of the Servers especially the one having problem?
2. When the problem happened, Is there any error message on the symposium or windows event viewer?

I notice that the Time Synchronization between SCCS and PABX is actually managed by MAS Time Service. You might need to check the event viewer whether there is any error message on the MAS Time Service prior/after the Daylight Savings