Three Years On & Still No Time Sync!

[zakabog]

If you're running a UCM or an application server for Voicemail Pro then you won't be able to sync time with it, change the time source to something like pool.ntp.org and be done with it, or change it to be your DC. Make sure you also change the time source on the VM Pro server itself (somewhere in the management interface, or if you know Linux well enough you can just fix the NTP config.)

[gribbb]

I realise this thread is getting a little old, but I came searching for the answer to our problem. We have digital phones (1416s) on an Avaya IP Office 500 v2. For some reason the phones were always a few minutes out from the correct time, even though an SNTP server was set in the configuration.

This was the solution for us:
1. In Manager > System, set the Time Setting Config Source to SNTP, set Time Server Address to nz.pool.ntp.org (use one relevant to your location - we're in NZ)
2. Since the LAN1 configuration has no 'Default Gateway' setting, go to IP Route on the left hand side and check for / add a default route for IP Address=0.0.0.0, IP Mask=0.0.0.0, Gateway IP Address=192.168.1.254 (use the IP address of your default gateway)
3. Save and Merge these settings...
4. Use the System Status utility to check the Alarms > Service and make sure there are no errors. We initially had one saying it failed to resolve the address nz.pool.ntp.org, so I switched it to an IP that worked, but we did have the DNS servers correctly set in System > DNS, so I suspect this was simply a timeout issue. Now that I've changed the SNTP back to nz.pool.ntp.org it's working fine

How to test if it's working (apart from checking errors)
1. Set the time on your PC to an incorrect time (eg 5 minutes slow)
2. In Manager > System, set the Time Setting Config Source to Voicemail Pro/Manager and set the Time Server Address to the IP address of your PC
3. Save and merge these settings - within a minute you should see the time on your phone change to the incorrect time
4. Now go and change the Time Setting Config Source back to SNTP and if desired, edit your SNTP server settings, then Save and Merge
5. All going well (no errors in System Status Alarms), within a minute you should see the time on the phones correct themselves.

Good luck

[havel3]

The time shown on the phone can differ from the time shown on the PCs or as shown in SSA.
That is by design as the phone displays aren't refreshed every second but only once per minute.
The IP Office does a NTP request once per minute so at worst the time on the phone can be 2 minutes off.
Read this
If the customer wants to have a reliable clock then they should buy a atomic clock and not a phone system.

PS a Microsoft Domain Controller responds on NTP requests send by DC Members only unless specific changes have been made.