Synchronization with NTP Server not working

[SBang]

Having the exact time on our 3300 is extremely critical.  We match up the SMDR data with our .WAV file recordings based on the time stamp.

We have the Synchronize option in the System Date and Time part of System Configuration enabled and setup to sync with pool.ntp.org.

We have discovered that the time ONLY synchronize when we go into the System Date and Time area and click 'Change' and then 'Save'

For some reason NO time sync happend unless we manually do this.

Have anyone else seen this happen and found the reason for this?

Thanks

[Keithw]

What version are you running on the 3300

[ralph]

Time sync to an NTP server came out in MCD 4.0 (I believe).
If it's available to you, you can go System Properties-->> System Settings-->>Date and Time.

Ralph

[SBang]

Keithw - Thanks for your reply!  We are running MCD 4.0 SP2.

ralph - Thanks for your reply!  Yes - as you can see in my original post, the time sync is available to us - it's just not working.  It should work continuesly but only syncs the time if we go into the setup screen and save it again (without making any changes)

[bluewhite4]

It was my understanding that it didn't continuously sync, but only syncs once a day. Also, previously Mitel has stated that the time on the phones will not match the actual system time, due to how often the phones update themselves off of the controller. I've similarly had a customer who needed the time to be exact, since they wanted to use it for marking people late to work, and the official word from Mitel is that the phones should not be used that way, as they are not meant to be that accurate.

[bobcheese]

I had a Mitel Tech once say to me that the time on the phones is a representation of time not a clock 

[bluewhite4]

I had a Mitel Tech once say to me that the time on the phones is a representation of time not a clock 

That's pretty much what they have told us as well. I just couldn't phrase it so appropriately.

[Mitel100]

The NTP time sync will sync with the source about every 10-20 min. You should see this in the maintaince logs. Can you see any errors in there.

Let us know.

[ralph]

I had a Mitel Tech once say to me that the time on the phones is a representation of time not a clock 

That's kinda like my beard with all that gray coming on.

Ralph

Update: July-14-2012 by editor:  New How to doc is available here:  How to Set Time on Mitel 3300

[brantn]

Yes check maintenance logs for NTP errors. Time on phones can be inaccurate as time takes low priority in the processing queue.

[Beanbag]

I am having this issue as well. 7.2 SP1. Time doesn't sync unless I got into date and time and click save. I can see it hitting the NTP server when I do that and the time corrects itself.

Any word if Mitel has a fix for this?

[x-man]

Yup,me too in MCD7

[acejavelin]

I thought this was just me... I have several MCD systems that do this as well.

Sent from my XT1575 using Tapatalk

[VinceWhirlwind]

I just checked one of mine - 7.2, it logs from "SystemDateTime" at 0459hrs every morning, updating it by 4 seconds to day, 5 seconds yesterday...
 
Your NTP form just says "enabled" to activate synchronisation - you don't get to specify when or how often as far as I can see.
 
So mine is definitely working - maybe check your scheduler and make sure you haven't got something else running at that time which might be interfering?

[boycey9]

With regards to your handsets see below, you will never be able to get reliable accurate time on the handset, Not sure on frequency of the NTP sync


The phones do not use NTP, NTP is used only to maintain the time on the
controller/server.
The display on the phones gets updated with the date/time every minute during its
handshake with the controller which normally occurs every 30 seconds. The time only
gets updated to minute accuracy if a phone receives the time from the controller at
13:00:59 then the time that gets passed to the display is 13:00 so the phone display
time is 59 seconds different to the actual controller time.
Because all the phones connect and get their updates from the controller at different
times during a 60 second period it will be noticeable with phones that the time appears
different
Please note the phones are not advertised as being accurate time pieces.
Mitel phones usually get their time updated by different methods I will describe each
below.
5312,5324 type phones
The 5224 gets its time from the Call Control. The clock time is not maintained on the
phone and is updated by a refresh of the display every minute or when a call is made.
This can cause the time to appear to be different by up to 1 minute. If the call control
has the time 09:30:59. The time will get displayed on the phone for the next minute as
09:30 so there is automatically the possibility of a 1-minute difference.
5330, 5340 & 5360 type phones
The time on the 5330/40 & 60 is maintained locally by the phone. The time is updated to
the phone by a similar method to the 5312/24 so only details of the hours & minutes are
sent so there is the possibility that the time could again be 1 minute difference. Then
there is the possibility of drifting of the clock during the day as the phone is only updated
with the time once a day
To show how time can differ on phones the following example shows two phones being
updated 1 second apart
Phone 1 gets its update
System time = 09:00:59 Phone1 time - Display = 09:00 Actual = (09:00:00)
Phone 2 gets its update
System time = 09:01:00 Phone1 time - Display = 09:00 Actual = (09:00:01) Phone2
time - Display = 09:01 Actual = (09:01:00)
On top of this the 5312/24 & 5330/40/60 get their times from different clocks so there is
potentially a difference in time maintained in their source clocks
The phones are not advertise