UC module date defaults to 2/15/15... 1

[AdvilJunkie]

I have installed a UC module running version 9.0.1.0 bld 12 and twice over the course of roughly 3 months, the internal date of the UC module has defaulted to 2/15/15. The time stays correct and all functionality remains but the time stamp is incorrect. The first time I assumed it was nothing, it just happened again and it defaulted to the same exact date as last time.

Has anyone seen this or something similar?

Thanks in Advance
Brian

 

[holdmusic34]

These are the settings from a Linux release 6.4 (Final) 9.0.5.0 build 3
Also check your IP Office and NTP time settings.

I'm a Spanish lumberjack and I'm ole'.

 

[AdvilJunkie]

Thanks I'll do a stare and compare next time I'm onsite, with the NTP IP 169, is it looking to the UC or the IPO settings? If it's the IPO then I'm using a Public NTP server. If that could be the cause I will find an alternate reliable internal source for NTP.

Thanks for the reply,
Brian

 

[derfloh]

169.254.0.1 is the IP of IP Office the UCM communicator with.

 

[AdvilJunkie]

So does it make more sense to point the UC module at a unique NTP address or leave it at the 169 address and let the IPO handle the NTP?

Thanks,
Brian

 

[derfloh]

IPO is a good choice. But you have to make sure that IPO has the correct time as well for example provided by another NTP server.

 

[AdvilJunkie]

Will do, I haven't noticed the date/time change on the IPO but perhaps I can change the NTP source regardless and see if it corrects the issue.
Thanks for the clarity,
Brian