The Time Server is a MAS Service that synchronizes the Switch time with the Server Time. It polls the Switch for time every 1 minute or receives an unsolicited time change from the switch through TAPI. Server time will be adjusted according to the time difference. Clock frequency adjustment will be performed if time differs by 5-60 sec. Step adjustment will be performed if time differs by more than 1 minute.
Severity Minor
Description A Windows function failed. It usually indicates an error waiting for a Semaphore.
Impact Depending on the context, the time server may continue to operate normally. This event applies to Call Center system.
Recovery Action Restart the Time Server Service. If the problem persists, please contact your Customer Support representative.
Technical Support Action This may be an indication of an overall system problem. Rebooting may clear the problem.
Severity Major
Description The time server was unable to complete an API call to TSM. This event applies to Call Center system.
Impact Time between Switch and Server may not be synchronized.
Recovery Action Check the Ethernet connection between the MAS server and the switch. It may have been disconnected. Restart Time Server Service.
Technical Support Action Follow TSM check list. Rebooting may clear the problem. Check the rc for possible root cause indication.
Severity Minor
Description The time server could not initialize at service startup. The process will exit and will be restarted by the System Manager. This event applies to Call Center system.
Impact The service starting failed, the SM will restart the time server.
Recovery Action If the problem persists, please contact your Customer Support representative.
Technical Support Action Please note any error codes/messages. Check the reported function and rc for possible root cause indication.
Severity Minor
Description The time server could not initialize at service startup. The process will exit and will be restarted by the System Manager. This event applies to Call Center system.
Impact The applications are not notified of a time change or the corresponding entries in the registry might be corrupted or missing. Check the registry in /HKEY_LOCAL_MACHINE/SOFTWARE/NBsm_RamKey/TimeServerKey for the dwPreviousTime and dwNewTime values.
Recovery Action Rebooting the Server may clear the problem. If the problem persists, please contact your Customer Support representative.
Technical Support Action Check the rc and follow the SM check list. Restarting System Manager may clear the problem.
Severity Major
Description An unexpected condition occurred in the Time Server. This event applies to Call Center system.
Impact Time between Switch and Server may not be synchronized properly.
Recovery Action Restart Time Server. If the problem persists, please contact your Customer Support representative.
Technical Support Action Please note any error codes/messages. Rebooting may clear the problem.
Severity Minor
Description The switch time differs from host time more frequently than allowed. This event applies to Call Center system.
Impact System time changing too often may cause an undesirable effect on other Software. e.g. Timestamp in report will not be accurate.
Recovery Action This alarm could indicate a clock related hardware problem on the server or the switch. It may also indicate that the time has been changed manually many times on either the server or the switch.
Technical Support Action Run hardware diagnostic on Server.
Severity Minor
Description Time difference between the Server and the Switch is greater then 60 seconds. The Server time is adjusted to match the Switch time. This event applies to TSM version of Time Server. This event applies to Call Center system.
Impact Universal and Local time on the time server is changed.
Recovery Action No action is needed if time was changed on the Switch or Server before the event is reported. Please note that it is normal for the Server time to change automatically during Daylight Savings Time Switch over. Verify time on Switch is running properly.
Technical Support Action Check time related hardware. Run hardware diagnostic.
Severity Info
Description Time difference between the Server and the Switch is between 5 to 60 seconds inclusive. The System Clock frequency on the Server is being adjusted to gradually synchronize with the Switch time over an approximately 1 minute interval. This event applies to Call Center system.
Impact The Server time will run faster if the Server is behind the Switch time or slower if the Server is ahead of the Switch time.
Recovery Action Contact the Customer Support Service Representative if problem persists. Verify time on Switch is running properly.
Technical Support Action Check time related hardware. Run hardware diagnostic
Severity Info
Description The Frequency time adjustment that was started earlier has finished. This event applies to Call Center system.
Impact The Server time will start running at the normal frequency.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description The system time on the Server has been changed either by the Administrator or Software on the system. This event applies to Call Center system.
Impact Server time is changed.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description A Windows function failed.
Impact It usually indicates a time-out waiting for a TAPI event. Depending on the context, the time server may continue to operate normally. This event applies to MCE system.
Recovery Action Restart Time Server Service. If the problem persists, please contact your Customer Support representative.
Technical Support Action This may be an indication of an overall system problem. Rebooting may clear problem.
Severity Major
Description The time server was unable to complete an API call to TAPI. This event applies to MCE system.
Impact The time server will shutdown the TAPI connection and retry to register with TAPI after 1 minute.
Recovery Action Check the Ethernet connection between the MAS server and the switch. It may have been disconnected. Restarting Time Server may clear the problem.
Technical Support Action Check the return code reported. Reboot the Server.
Severity Major
Description The time server could not initialize at service startup. The process will exit and will be restarted by the System Manager. This event applies to MCE system.
Impact The service starting failed, the SM will restart the time server.
Recovery Action Restart Time Server. If the problem persists, please contact your Customer Support representative.
Technical Support Action Please note any error codes/messages.
Severity Major
Description The time server could not initialize at service startup. The process will exit and will be restarted by the System Manager. This event applies to MCE system.
Impact The applications are not notified of a time change or the corresponding entries in the registry might be corrupted or missing. Check the registry in /HKEY_LOCAL_MACHINE/SOFTWARE/NBsm_RamKey/TimeServerKey for the dwPreviousTime and dwNewTime values.
Recovery Action If the problem persists, please contact your Customer Support representative.
Technical Support Action Please note any error codes/messages. Restart System Manager.
Severity Major
Description An unexpected condition occurred in the Time Server. This event applies to MCE system.
Impact This usually determines the TAPI connection to be shutdown.
Recovery Action Restart Time Server. If the problem persists, please contact your Customer Support representative.
Technical Support Action Please note any error codes/messages.
Severity Minor
Description The switch time differs from host time more frequently than allowed. This event applies to MCE system.
Impact No impact on the time server.
Recovery Action This alarm could indicate a hardware problem on the server or the switch. It may also indicate that the time has been changed manually many times on either the server or the switch.
Technical Support Action Run Clock related diagnostic on Server.
Severity Minor
Description Time difference between the Server and the Switch is greater then 60 seconds. The Server time is adjusted to match the Switch time. This event applies to MCE system.
Impact Universal and Local time on the time server are changed.
Recovery Action No action is needed if time was changed on the Switch or Server before the event is reported. Please note that it is normal for the Server time to change automatically during Daylight Savings Time Switch over. Verify time on Switch is running properly.
Technical Support Action Check time related hardware and run clock related diagnostic.
Severity Minor
Description Time difference between the Server and the Switch is between 5 to 60 seconds inclusive. The System Clock frequency on the Server is being adjusted to gradually synchronize with the Switch time over an approximately 1 minute interval. This event applies to MCE system.
Impact The Server time will run faster if the Server is behind the Switch time or slower if the Server is ahead of the Switch time.
Recovery Action Verify time on Switch is running properly. Contact the Customer Support Service Representative if problem persists.
Technical Support Action Check time related hardware and run clock related Diagnostic.
Severity Info
Description The Frequency time adjustment that was started earlier has finished. This event applies to MCE system.
Impact The Server time will start running at the normal frequency.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description The system time on the Server has been changed either by the Administrator or Software on the system. This event applies to MCE system.
Impact Server time is changed.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description Time Server has successfully initialized with TAPI. Time synchronization between Switch and Server will start.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Info
Description The TAPI monitoring thread has been shutdown. This could be the result of a timeout condition, or a normal service shutdown request.
Impact The CallPilot and M1 times may not be synchronized.
Recovery Action Not applicable
Technical Support Action Not applicable