Re: Cisco Call Manager 7.1.3 Incorrect time on Phones

Unanswered Question
Apr 7th, 2010
User Badges:


I have a call manager cluster configured and it is configured to use time via ntp server.

The time that was displayed on the phones during the initial setup of the system was correct however when since last week I have noticed that the time displayed on the phones are incorrect.

The phones are displaying the UTC time instead current time for the timzezone, how do i correct this?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Edwards Fuenmayor Fri, 04/09/2010 - 14:11
User Badges:

hi M-laing

updating the device pack verifies the call manager.

then updated the phone firmware to version 9.

Installing Firmware Release 9.0(2)SR1 for SCCP

This section describes how to install firmware release 9.0(2)SR1 for SCCP, and includes these topics:

Firmware Upgrade Issues for SCCP

Firmware Installation Procedure for SCCP


Edwards L. Fuenmayor

mezcalito Sat, 04/10/2010 - 06:32
User Badges:

Hi bro,

Did u fix the issue? I have the same problem, it looks like this:

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

     remote           refid      st t when poll reach   delay   offset  jitter
*     LOCAL(0)        10 l   26   64  377    0.000    0.000   0.004

synchronised to local net at stratum 11
    time correct to within 12 ms
    polling server every 1024 s

Current time in UTC is : Sat Apr 10 00:37:48 UTC 2010
Current time in America/Monterrey is : Fri Apr  9 19:37:48 CDT 2010

The phones show the UTC time instead of the America/Monterrey time, I had restarted the server but it still shows the wrong time.

Did u install the Device Pack that Edwards L. Fuenmayor talked about?


htluo Sat, 04/10/2010 - 08:57
User Badges:
  • Red, 2250 points or more

On CUCM 7.1.3, new timezone structure was introduced.

Because of this, the phones need to be on firmware version 9 or above to recongnize the timezone settings.

For backward compatiblity (phones has firmware lower than 9), you may choose the timezone with a star (*) on CUCM 7.1.3


Edwards Fuenmayor Sat, 04/10/2010 - 14:08
User Badges:

hi brother

that is correct unless you have the firmware version higher than 9 in the phone does not work the time zones that do not have the (*) try to update the version and if it lets you update the firmware as happened to me have to update the comment you pack device.


Edwards L.

mezcalito Sat, 04/10/2010 - 23:06
User Badges:

Allright, I'm gonna select the (*) in the timezone then, I'll do that next monday, I need a quick fix cause I have around 600 Ip Phones and some are in remote locations within my City, I have tons of work and dont have the time to manually reset the phone if some fail (I had that problem when I moved to a newer version, actually this one). Eventually I'll install the Device Pack and tell you if that fixs my problem.

By the way... why Cisco released some changes in the Timezone and the loads of the phones that come with the CCM 7.1.3 don't support it? oohh nevermind... they may have their reasons.

Thanks so much Edward and Michael!!


Amit Divekar Tue, 10/26/2010 - 10:35
User Badges:
  • Cisco Employee,

Hello M-laing,

                    I believe this is been classified as a bug, the following are the bug details

Here is the update about the DST issue.
Bug Details:
DST: Update CM for Olson TZ ver 2010i
Internally found enhancement (Sev6) bug: V-Verified
The following versions are affected:
* 7.1.3: all CM versions below 007.001(003.33031.001)
* 7.1.5: all CM versions below 007.001(005.12008.001)
* 8.0.2: all CM versions below 008.000(002.41007.001), 8.0.3 shouldn't be affected.
We already have COP files for the 3 branches mentioned above:
* COP for 7.1.3 ->

* COP for 7.1.5 -> Can be found on already:

* COP for 8.0.2 ->

Please bear in mind the following suggestions when installing the COP files:
- Installation to all machines in the cluster is required
- As with any installation or upgrade, it is recommended that you apply this Update during off peak hours.
- When applying this Package be advised that a clusterwide reboot is required.
- It is also recommended that this update be installed on all  machines in the cluster before the cluster is rebooted.
I hope it helps!

Do feel free to let me know if there is any clarifications that you need here

Amit Divekar.

Hi Amit,

Not sure that this bug applies to the orignal poster as this was back in April, however your post has hit the nail right on the head for the problems we are experiencing, so thanks! Not sure if we will apply these fixes or not though as we could just wait 3 working days now, but that won't be my decision.

Thanks again


Amit Divekar Wed, 10/27/2010 - 02:16
User Badges:
  • Cisco Employee,

Hello Gareth,

                   I hope it helps, just wanted to clarify things as well as the solution for it as things are sometimes serious when it comes to such issues.

Hope it helped you.


Amit Divekar


This Discussion