24 hour time setting on 8945

[rowdygardner]

How do you configure on a Cisco 8945 handset whether it displays the time at the top in 12 or 24 hour format?

[Jaime Valencia]

That is configured in the call control agent, not on the device itself, what are you using??

[rowdygardner]

We are running CUCM 8.6

We have around 150 x Cisco 8945 handsets at the one site each running active load sccp 9-3-2-11.

Some handsets are showing the time in 24 hour mode e.g. 15:15 while others are showing it in 12 hour mode e.g. 3:15 pm.

This has only recently occurred. Previously all handsets were showing in 12 hour mode.

Note: We currently have 1 x CUCM subscriber down, with 1 still available. I believe this may be the cause of the issue but we're not sure why running on 1 subscriber would cause this.

[Sreekanth Narayanan]

Are all of the handsets in the same Device Pool? Under Device pool, you can set the Date/Time Group (This can be configured under System). In the Date/Time Group you can set the timezones and the time-format for the phones belonging to that particular DT Group. Please check if all of these devices belong to the same DT group and no changes were made recently.

You can also download the configuration files for the phone which is showing 24 hour time and the one that's showing 12 hour time and see if there is any difference there.

Thanks

[rowdygardner]

All the handsets are in the same Device Pool.

The Device Pool has a Date/Time Group with Time Format of 12-hour. But some handsets are displaying the time in 24 hour format.

We also have Date Format set to D/M/Y but some handsets are showing as M/D/Y.

It's like the system has set them back to default.

Does this occur if a CUCM subscriber cannot be contacted?

[Sreekanth Narayanan]

Perhaps dbreplication did not make sure that the 'datetimesetting' tables are matched on the 2 subscribers.

admin: run sql select * from datetimesetting

will give you the output for all entries in that table. I would compare the entries from sub1 and sub2. But since sub1 is not reachable you can't compare. There is an entry in that table called 'datetemplate'. This determines the format.

Can you check this?

Once sub1 comes back up I suggest a utils dbreplication repair all to make sure all the tables are matched on all the servers. Mismatches can often cause unexpected behavior in the devices.

[Aman Soi]

[+5] to Sree for sharing the SQL query.

regds,

aman

[rowdygardner]

We have rebooted the phones that we in the 24-hour format and they now display in 12 hour format.

No setting changes were made in CUCM.

Looks like it may be a CUCM 8.6 bug where the time displays incorrectly if a CUCM Subscriber fails. Those devices that were previously registered to the failed subscriber did not switch properly to the remaining subscriber and a reboot or reset seems to be required.