Time on IP phones 2 minutes off

[one234]

Hello All,

Has any of you ever come across the following problem?

The time on all the phones is 2 minutes off, but all core components time is ok.

So the Call Server, Linux Base, Contact Center, etc, etc have the correct time (NTP sync) but even though everything has the correct time the phones are 2 minutes behind.

It's a release 6 co-res geo redundant system, all latest deplists, firmware, etc is loaded.

Best regards,



Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[Firebird Scrambler]

This might help you below?.

Call Server (CS) system time drifts on Release 6.00 Co-resident ( Co-Res ) System

Problem Description
On Co-RES systems, Linux Base provides system time for all elements including CS.
Linux Base time is the SW ( Software ) time, while it gets initial time from HW ( Hardware) clock (BIOS battery) on startup, then it continues to update system time according to its SW clock. The issue reported is, thatSW clock keeps drifting 30 seconds per day.

Problem Resolution
If internal clock type is used as it is configured now in the system, system time is synchronized with BIOS time initially and then updated continously according to SW clock.
If machine type is CPPM ,system time could be corrected by setting an appropriate offset on Ld (Load.) 117 in case of a drift on system time.

In Co-Res systems, Linux Base time provides the system time and overlay commands on Ld 117 to modify system time could not be used.
Thus, in case of drift in Linux Base time, Network Time Protocol needs to be used ( NTP ). Rather than using Linux Base time as an internal clock, an NTP server ( which could simply be a PC ) would provide correct time as an external time source. NTP could be configured via Base Manager > Date and time > NTP edit > Add a reliable external clock source IP address from edit page. After editing , when <Sync Now> button is pressed , time is received from NTP server and it is updated periodicallyafter that.

Though there is no available command on Linux Base to keep time accurate by setting an appropriate offset in case of drift,commands below could be used to display SW clock time,HW clock time ; synch SW clock to HW clock or HW clock to SW clock manually.
[spalav@cores ~]$ su
Password:
[root@cores spalav]#
[root@cores /] # find / -iname hwclock*
/usr/share/man/man8/hwclock.8.gz
/usr/sbin/hwclock
[root@cores /] # /usr/sbin/hwclock --------->prints HW clock time
18 Jun 2010 05:37:28 PM EEST -0.977187 seconds
[root@cores /] # date ---------> prints Linux Base (SW) clock time
Fri Jun 18 17:37:30 EEST 2010
[root@cores /] # /usr/sbin/hwclock --hctosys ---------> retrieves HW clock time and sets it to SW clock time
[root@cores /] # /usr/sbin/hwclock --systohc ---------> retrieves SW clock time and sets it to HW clock time

Date can be set with the command 'date MMDDhhmm' or 'date MMDDhhmmYYYY.ss'


All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[one234]

Hi,

Thank you for the reply. But hw time and sw are in sync. When I do TTAD, DATE, check UCM, EM, etc, etc they all show the correct time (Primary and secondary site)... Except the phones...


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[Tman45]

We had an issue where the acutal NTP time was off. We tried everything we could think of on the PBX side to correct it.
BUT, the PBX and phone time was right it waas the desktop time was about 2 minutes fast or slow. It's funny because you would think it would be correct/accurate via NTP. Have your SystemAdministrators double-check with the national NTP time reference.

 

[one234]

Hi,

Thank you for your reply. But as stated in my previous posts. All components are in sync with the NTP server, except for the phones. They are 2 minutes behind. And the NTP is correct too.

Desktops, Servers, Linux Base, Call Server, etc are all fine. Just the phones are off by 2 minutes... So i.e. every single component I can think of is showing 10:34, but all IP phones show 10:32...



Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[janaya]

have you tried resetting one phone to see if the time syncs?

 

[one234]

Yep tried that, didn't work.

Also checked lamp audit (Not sure if that's applicable to IP sets though).

1 thing I could check is to see what happens when I change the primary and secondary node IP addresses. The IP sets now register at the secondary site and get redirected to the main.


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...