Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

7970 display wrong time

Unanswered Question


i have a CCM 4.1(3) and only the ip phones 7970 and IP Communicator shows an incorrect time in screen, i've tried to change the time zone in windows in both (pub/subs), and reset the devices but nothing happens. The rest of the phones (7912/7940/7960) shows the right time.

Anyone could help me? could be some kind of bug? i need a new firmware?

Thanx in advance


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gogasca Thu, 05/18/2006 - 14:02
User Badges:
  • Green, 3000 points or more

Can you set up a specific Date/Group and Device Pool that Just the 7970 uses, so that the 7970's have a specific Device Pool that uses a specific

Date/Time group and then does the 7970 display the correct time ?

I would upgrade to latest firmware and IPC 2.0.1

(Try one if that helps)

Actualy WE DO have open a DDTS for this one, but dont have it handy.

gpulos Thu, 05/18/2006 - 14:45
User Badges:
  • Blue, 1500 points or more

i've seen this behavior in load 7.2(2) and 7.2(3).

i've upgraded to 8.0(2) SR1 and problem is fixed! :)

try this load if you can.

jbarcena Fri, 05/19/2006 - 11:54
User Badges:
  • Red, 2250 points or more

Gogasca is right, there are several bugs about this issue, some of them are CSCec75767:



The time on the IP Communicator phone is incorrect. The time displayed is GMT instead of local time zone.



If the CM Date/Time group uses 'local time zone of CallManger' instead of explicit time zone setting, the IP Communicator will display the time in GMT.



Explictily set the time zone setting to the local time zone




When Mountain Time Zone (US & Canada) was selected , 7970 phone, shows

7 hours ahead of the actual time that should be. If Eastern time or central time is selected on

7970 phone, it show the correct time.


When Mountain Time zone is used.




Pretty much all of them are fixed in the latest firmwares, so follow Gonzalo's suggestions.


This Discussion