Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: pakman on June 24, 2013, 01:04:02 PM

Title: Time on Phone
Post by: pakman on June 24, 2013, 01:04:02 PM

Hello,

I have the PBX to use our NTP server and I am receiving the following logs.

set/poller synchronization failed as RTC-NTP server drift is more than 10 seconds.

anyone know how to fix this? The phones at this location have been anywhere from 3 to 5 minutes behind the pc.

Thanks,

Title: Re: Time on Phone
Post by: ralph on June 24, 2013, 01:15:05 PM

Is the controller actually syncing to the time server?
If it's failing then you should see a log indicating that.
What time server are you using?

You may want to review this doc for NTP server options with the Mitel 3300 (http://www.mitelforums.com/articles/3300/3300-how-to-change-time.php).

Ralph

Title: Re: Time on Phone
Post by: pakman on June 24, 2013, 03:15:24 PM

Hi Ralph,

The controller is suppose to be synching with the server that's running NTP which is our in house server. The log is below.  Now that in-house server uses it's local time it doens't go out to another NTP server.


Software
Log Number   3841
Severity   Warning
Date   2013/Jun/24
Time   13:51:19
Source   SYS_TimeCalls
Description   setPoller Synchronization failed as RTC - NTP SERVER drift is more than 10 secs
Module   Main
File Name and Line Number   SYS_TimeCalls.cpp;634

Title: Re: Time on Phone
Post by: acejavelin on June 25, 2013, 09:50:38 AM

Quote from: pakman on June 24, 2013, 01:04:02 PM

... The phones at this location have been anywhere from 3 to 5 minutes behind the pc...

I would change time servers... if you are using an internal Domain time server right now, it might actually be off (as your above quote alludes to), I ran into this at a customer site once before and the Mitel was syncing to their Domain Server but that server wasn't syncing to any outside time server. Changing the time server to "us.pool.ntp.org" fixed the issue, if you need a different zone, pool.ntp.org has lots of zones and specific country areas you can choose from to sync to.

If the end result is to get the Mitel and the PCs to have the same time, they all need to use the same source and it has to be within a certain tolerance of the public, global network clocking system.

If you still have problems after syncing to a reliable clock source, this could be a digital trunk issue where the carrier is not synced up to a public network clock and their clocking source is off significantly, this would be very odd and unusual but the theory is solid. Or the 3300's RTC is defective, also very unlikely but a possibility but if you getting this deep I would contact tech support.

Title: Re: Time on Phone
Post by: jrg0852 on June 25, 2013, 10:27:03 AM

Sometimes the system likes the IP as opposed to the name. I use one of these two, which ever works best. Thanks:

time.nist.gov (64.250.177.145) or pool.ntp.org (69.36.227.90)

Try with the IP's

Title: Re: Time on Phone
Post by: acejavelin on June 25, 2013, 11:50:41 AM

Quote from: jrg0852 on June 25, 2013, 10:27:03 AM

Sometimes the system likes the IP as opposed to the name. I use one of these two, which ever works best. Thanks:

time.nist.gov (64.250.177.145) or pool.ntp.org (69.36.227.90)

Try with the IP's

Except remember that the "pool" IP's will change all the time and be a multi-IP record. Most ISP's offer NTP service, usually just time.<isp domainname> and that might work better and be a static IP.

Title: Re: Time on Phone
Post by: pakman on June 27, 2013, 01:33:39 PM

Thanks for the feedback I will try some of the suggestions.