Cisco IP phones not getting correct time

[Jahangir Tahirov]

Hello cisco IP phone which is provisioned through CUCM gets incorrect time.

The time looks like adding 4 hours to standard time, for instance, our local time must be 18:00 PM but phones showing 18:00 + 4 hours.

[Jaime Valencia]

Is the date time group the right one, have you tried changing it? Have you tried a different FW? 

[Jahangir Tahirov]

Yes, time group is the right one. I tagged some pictures from CUCM.

[George Sotiropoulos]

Hello,

On a specific phone, under Device Information you may change the "Device Mobility Mode" to "Off" and then press "Save" and "Reset" the phone

Let us know if this works for you,

George

[Jahangir Tahirov]

I changed "Device Mobility Mode"  to off and the restarted phone but again time is incorrect, it differs only 4 hours.

Alson from phone configuration menu I clicked "reset" and then "restart" but not affecting the phone. I restarted the phone manually.

[Jahangir Tahirov]

I also tried to change the time group settins but not affecting phones. 

[George Sotiropoulos]

From the OS Admistration Page, you may need to confirm that the NTP Settings and the Time of your CUCM is correct. Other than that, a good idea is to update the firmware on the phone(s) to avoid the possibility of "hitting" a bug.

George

[Jahangir Tahirov]

I checked from the OS administration page for the NTP setting but its okay.

We have 4 model phones and all of then are incorrect time this should not be a bug.

[Jahangir Tahirov]

I fixed the problem just restarting services in SUBscriber . Then phones got the correct time from PUblisher.

So the problem you can saw from pictures I tagged in our subscriber which does not have the correct time.

I tried to add NTP setting to SUB but not permitting me. How I provide Sub get syncretized from the pub ?

[Roger Kallberg]

Subscribers get their time from the publisher.

[Jahangir Tahirov]

@Roger Kallberg okay subscriber gets their time from the publisher. what can be a problem source for sub not getting NTP setting from the pub?

PUB ::::::

utils ntp status
ntpd (pid 27143) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
*172.18.101.11 194.192.112.20 3 u 232 256 377 1.130 4.813 6.137
+172.18.101.12 172.18.101.11 4 u 219 256 377 1.017 -6.472 7.239

synchronised to NTP server (172.18.101.11) at stratum 4
time correct to within 173 ms
polling server every 256 s

Current time in UTC is : Sun Feb 9 17:20:43 UTC 2020
Current time in Asia/Baku is : Sun Feb 9 21:20:43 +04 2020

SUB::::

admin:utils ntp status
ntpd (pid 15767) is running...

No association ID's returned

unsynchronised
polling server every 8 s

Current time in UTC is : Sun Feb 9 21:20:23 UTC 2020
Current time in Asia/Baku is : Mon Feb 10 01:20:23 +04 2020

[Jaime Valencia]

Restart NTP in the SUB, give it a few minutes and check status again.

[Jahangir Tahirov]

@Jaime Valencia  I did it but no difference. Why UTC time is different in SUB?

[Roger Kallberg]

Something is not correct with your subscriber. It should show the pub as the NTP server. See below from a system I've got access to.

SUB

admin:utils ntp status
ntpd (pid 2845) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
*10.192.31.5 10.192.4.210 2 u 340 1024 377 0.619 -0.161 0.070

synchronised to NTP server (10.192.31.5) at stratum 3
time correct to within 58 ms
polling server every 1024 s

Current time in UTC is : Mon Feb 10 11:46:14 UTC 2020
Current time in America/Chicago is : Mon Feb 10 05:46:14 CST 2020

PUB

admin:utils ntp status
ntpd (pid 1672) is running...

remote refid st t when poll reach delay offset jitter
==============================================================================
*10.192.4.210 .GNSS. 1 u 715 1024 377 0.219 -0.031 0.086
+10.67.1.250 .GNSS. 1 u 552 1024 377 127.645 -0.018 0.114
+10.138.1.12 .GNSS. 1 u 402 1024 377 216.269 -0.137 0.194

synchronised to NTP server (10.192.4.210) at stratum 2
time correct to within 26 ms
polling server every 1024 s

Current time in UTC is : Mon Feb 10 11:46:03 UTC 2020
Current time in America/Chicago is : Mon Feb 10 05:46:03 CST 2020

I would recommend you to verify that the CM nodes have communication with each other and that database replication is in a good state. Check these commands on all nodes.

• show tech network hosts
• show status
• utils dbreplication runtimestate
• show network cluster
• utils diagnose test
• utils core active list

And check in RTMT if there are any alerts.

[Jahangir Tahirov · Accepted solution]

We contacted the TAC and they report us this is a BUG. Then they fixed it.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux50133/?rfs=iqvred