Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Time Sync off by a minute

Status
Not open for further replies.

Mitelmatt

Vendor
Oct 3, 2007
817
GG
Hi Guys

Got a customer which has 3300 with MCD4.1. They have the time synced to an NTP and on the controller it is fine, but the handsets are a minute out still.

The customer pc's are getting time from same NTP and they notice phones are always 1 minute behind

Anyone else come accross this?
 
What happens if you go off-hook then hang up one of these instruments? (I think this may force the instrument to resynch)

I agree, for what these systems cost you might expect more accurate time display, but the time display is only accurate +/- the least significant digit.

I have a 5340 in my office, which if not used on a daily basis will show a screensaver time display that's off by several hours and sometimes off by several days (perhaps stuck) until you go offhook.

By contrast, hate them as I do, our new Cisco phones are spot-on within 10 secs of NTP

Original MUG/NAMU Charter Member
 
I had the same problem on a Mitel 5000HX using the 5340 phones.
Mitel tech support told me that's just the way it is. The system time is correct (no NTP) but yet the phones are always off by a minute.
 
Just checked my 5340. 10 seconds behind my PC.

It would be interesting to see what would happen if we added the NTP server option (42) to the DHCP scope. Wondering if the phones would sync directly or if it would ignore the option.

Dry Aquaman




 
5320,5330,5340 and 5360's will not keep the correct time with 3300 or 200ICP. However 5312 and 5324 will keep correct time. I put a trouble ticket in Mitel 2 years ago because our ACD agents were using phone time to login or out of the queue....which was off a minute. Mitel pretty much said tough crap..live with it.
 
I have both a DNIC 4025 and an IP 5224 on my desk and noticed that the IP phone was always behind the 4025 by some amount. Say it would always be 30sec slower than the DNIC phone. And the amount it was slow would change if the 3300 was rebooted. One day the service guy is here on a Mitel ticket and while the Mitel guy is on the line, the service tech asked why that was. The Mitel tech’s answer was (take it for what it is worth):

In my case the 3300 gets its time from the OPSMGR and is alsway on. The old DNIC 4025 gets all its data from the 3300 in real time so it shows the time on the 3300. The IP phone has its own clock and goes out to poll once a day. So if the poll happens at 10:00:45, the IP set will show 10:00 and be 45 sec slow. If you reboot the 3300 and now the poll just so happens at 10:00:05, the IP phone is only 5 sec slow.

Don’t know if this is true, but it is what I have observed here.
 
It is the same for us, the 3300 and 6110 real-time reporting show the correct phone system time but the handsets can be minutes off at any random time. The agents here use the phone as if it's a timeclock as well as the 6110 is heavily used in addition to the Workforce Scheduling add-on so the lack of accurate time keeping on the phones has been a sore subject for us as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top