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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Time Synchronization on 3300ICP

Status
Not open for further replies.

blackberry1980

Technical User
Jan 22, 2009
98
GB
I have a problem with a 3300 whereby every morning when the customer checks their handsets, the time is approx 20min off. The 3300 is a node on ops/ent and is not scheduled to do any time synch. Mitel have recommended changing out the entire box, but Im not confident that this might work and think it might have more to do with the ops/ent manager. Can anybody explain how time settings work within the 3300ICP. Is there an internal clock ?
 
The time on the 3300 depends on the time on the server that has ops manager installed. Correct the clock on the ops manager server hook it to a NTP server so it stays in sync) run a sync job and the phones should then have the correct time
 
Be caseful, NTP is a new feature, what software rev are you running? Outside of NTP, the system clock is generated off of an internal clock off the mainboard.
 
Are you sure that OPS is not setting the time?

The facts seem to indicate otherwise.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Should have been more clear. Even if the software on the 3300 does not support NTP if you have ops man synchronizing with the 3300 it will take it's time from ops man.

If the server that ops man is running on has the wrong time so will the 3300.

So if this is the case set the ops man server as I stated in my first post
 
I have a 3300 9.0 with a load of DNIC 4025s and the time on them have always been within seconds of the OPSMAN computer after a sync. Now I have been getting into IP. So I also have a 5224 on my desk and noticed that its' time is 45 seconds behind the 4025. If I set the OPSMAN PC clock to any time, then do a sync, the 5224IP is always 45 seconds slow compared to the OPSMAN PC clock and the DNIC sets. Not a big deal, but it makes you wonder where the IP sets are getting their clock data and where the DNIC sets are getting theirs. Go figure.
 
Thanks for the responses fella's, Ive managed to sort it. There was the old and new opsman server running on the network at the same time. Somebody forgot to remove the old server from the network. Verrrrry silly!
 
You could also try an upgrade to MCD 4.0 where the mitel has its own NTP server configuration
 
northportphoneguy: The reason it's behind is there is a disconnect between the sync and the updates to the phones. It's polled at the 3300, not pushed to the sets. I think you'd find if you reset your 3300 the offset would be different, but again consistent between Ops Man updates.
 
Thank you for your response. That makes sense. I have t.38 licenses going in and I know I have to do a hard reboot for them to be effective. It will be interesting to see if my delay gets any better than 45sec.
Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top