NTP time fault occurred in CTI Server

Publication Date:  2014-05-30 Views:  194 Downloads:  0
Issue Description
The customer respond us that the telephone system shuts earlier. It should be shut automatically at 5:30pm everyday but now it is shutting down earlier. I checked the system time of the server and there is no problem but the personal terminal’s time is faster than normal. I think maybe this is the problem.
Alarm Information
No Alarm.
Handling Process
1. Stop CTI service manually and change the time on the Suse Linux CTI server
• Log in to the server where the components are located as the user who installs the CTI platform.
• Run the mdscmd command to start the mdscmd management program.
• Select 9). Stop All Process
• Then run: Run the date --set "5/30/2014 09:12:35" command to set the time
• Run the hwclock --systohc command to write the time to the system hardware clock.
• Run the chkconfig ntp on command to enable automatic start of the NTP service during system startup.

2. Sync all devices to the same NTP server, for example the Suse Linux CTI server time

3. Start CTI service and restart NTP services => Success.

Root Cause
1. Check Suse Linux CTI server time and check IP Phone time

2. Try to modify Suse Linux CTI server time manually – failed, system time resets.

3. Check NTP running status
• Run the ps -ef |grep -i ntp command to check if the NTP service is started.

4. Check NTP server configured in the IP phone, Suse linux CTI and U2980.
• For IP Phone: On the web admin page go to System/Date and Time
• For U2980: LST NTPCFG:;
• For Suse: ntpdc -c sysinfo
If you have different NTP servers set for different devices, in such environment this could cause minor but important time differences and thus leading to unwanted behavior of the whole system.