02-05-2009 01:16 PM - edited 03-15-2019 04:02 PM
I have a problem on my callmanager server losing time. I can set the server to the correct time, then after a few days it'll be fast by 3 minutes then 5. how can I correct this?
Solved! Go to Solution.
02-06-2009 06:15 AM
Hi Latricia,
Good stuff!
Yes, the reference to 127.127.1.1 really tells the system to use the local/system clock instead of a true NTP reference. The internal Windows CCM clock will always lose time over time (sounds funny!) so this is why using NTP is always the recommended choice :)
Hope this helps!
Rob
02-05-2009 01:24 PM
easiest way is to configure an NTP for the network
HTH
java
if this helps, please rate
02-06-2009 05:14 AM
Hi Latricia,
Just to add a note to the good tip from Java;
How To Configure Time Synchronization for Cisco CallManager and Cisco Unity
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008009470f.shtml
Cisco IP Telephony Clock Synchronization: Best Practices
Hope this helps!
Rob
02-06-2009 05:39 AM
thanks for that information. that really help! this is what I found in the ntp file.
server 127.127.1.1
# Set Local Clock to Authoritive TimeSource
fudge 127.127.1.1 stratum 5
# Resets Stratum from default 3 to 5
does this mean it's authenticated with itself. and does the second line the reason it's 5 minutes fast.
02-06-2009 06:15 AM
Hi Latricia,
Good stuff!
Yes, the reference to 127.127.1.1 really tells the system to use the local/system clock instead of a true NTP reference. The internal Windows CCM clock will always lose time over time (sounds funny!) so this is why using NTP is always the recommended choice :)
Hope this helps!
Rob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide