Wrong Time on 7940/7960 Phones HELP

Unanswered Question
Oct 28th, 2007
User Badges:

Was today the original day the time was to fall back? We have applied all the necessary patches... The server times are all correct, but my 7940 and 7960 phones are an hour behind. The 7971 and 7941 times appear correct. Time on servers are correct, its just the time on the phones. We are in eastern time zone. CM 4.2

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Rob Huffman Sun, 10/28/2007 - 06:13
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Chris,


This was the "old" DST Sunday fallback date. I am not on site right now to see if our phones are doing the same thing :( sorry. Have you opened a TAC case? Have you tried resetting any of the 7940 or 7960 sets?


I might try changing the server time back 1 hour. This should not affect the 41's and 71's as they seem to operate independantly due to being Java based.


Let us know,

Rob

ischarcm Sun, 10/28/2007 - 06:18
User Badges:

Hi Rob... I had in the back of my head this was going to happen. I have not opened a case yet.. probably will attack it first thing tomorrow. I have done a reset on the phone that I have connected here at my house (thats how I discovered it).. but it didn't change anything. The time on the server is correct as it should be... (SO O.S.) is good. Its just the phones except the java based sets.

mstubbers Sun, 10/28/2007 - 09:44
User Badges:

My are doing the same thing. I had applied the tzedit fix. I'm in the middle of a planned upgrade anyway and can let you know if any of that fixes it. I'm upgrading my OS from 4.4a to 4.5b SR4. Servers have the correct time, but not phones.

Rob Huffman Sun, 10/28/2007 - 10:33
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Guys,


I'm guessing that you are hitting this new Bug;


However, for the Fall time changes you MUST update the MCS OS versions due to the following defect:


CSCsh20360: Looping in System Date & Time due to Daylight saving correction:


The four software items that were required in March.


The Windows 2000 Patches that were recommend are as follows


2000.4.2(sr15) or higher


2000.4.3a(sr8) or higher


2000.4.4a(sr3a) or higher


2000.4.5a 2000.4.5a or higher


2003.1.1 2003.1.1(sr1) or higher


2003.1.2a 2003.1.2a or higher


However, you may experience this vulnerability - CSCsh20360 - in the following MCS OS versions:


2000.4.2(sr15) or lower


2000.4.3a(sr8) or lower


2000.4.4a(sr3a) or lower


From this doc;


http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_field_notice09186a00807e02b1.shtml


Hope this helps!

Rob

mstubbers Sun, 10/28/2007 - 11:12
User Badges:

Yes, the OS updates did the trick and a reset of the phones.

ischarcm Sun, 10/28/2007 - 14:04
User Badges:

Is it just an os update or a CM update as well?

I have not been able to check our OS version yet but the server time remains correct I never had to modify that...it was only the phone times that went wrong. Was your OS (windows) time correct? Just wondering


Thank you

mstubbers Sun, 10/28/2007 - 14:12
User Badges:

Yes, I'm fairly certain the OS updates corrected it. Also, Rob's message indicates the same. In my case I went from 4.4b to 4.5 since 4.4 will be end of support as of November anyway.


Good luck!

ischarcm Sun, 10/28/2007 - 14:23
User Badges:

Ok I just got in remotely to see my OS and here is what it says. I'm not all that familiar with doing the OS updates so any pointers I would appreciate..


My level:

OS image 2000.4.4

OS serv release 2000.4.4aSR5


What is the download I should be looking for exactly? Do we just download the file and execute to publisher? I'm guessing we should do Publisher and all Subs one at a time? Approx how long does it take?


Thanks so much!!!!!


mstubbers Sun, 10/28/2007 - 15:04
User Badges:

May be a good idea to contact TAC just to verify your situation, but you are in a similar position to where I was. I had 2000.4.4aSR9 applied from previous updates. Otherwise here are the patches I applied and in this order. Bad news is the 4.5 update is 950MB to download from Cisco and took 45-50 minutes to apply to my server. Each server was about 1.5 hrs to upgrade. You need to do the PUB first, than all of your SUBs. Again I recommend you check out upgrade documentation starting at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/osbios.htm

and downloads at

http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des


!!!!! RUN BACKUP !!!!!!!!!!!!

win-OS-Upgrade-K9.2000-4-5a.exe

win-OS-Upgrade-K9.2000-4-5b-sr4.exe

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

You should also check on SQL updates.


I chose the 4.5 route since 4.4 support ends Nov 07.

Rob Huffman Sun, 10/28/2007 - 15:38
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Chris,


According to this your OS should be OK because you have 4-4a(sr5)?? I would open a TAC case here for sure. Why don't you look at the Manual workaround in this doc for the short term.


However, you may experience this vulnerability - CSCsh20360 - in the following MCS OS versions:


2000.4.2(sr15) or lower


2000.4.3a(sr8) or lower


2000.4.4a(sr3a) or lower


From this doc;


http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_field_notice09186a00807e02b1.shtml


Hope this helps!

Rob


ischarcm Sun, 10/28/2007 - 15:44
User Badges:

Many thanks for everyones help!!! We will get with TAC tomorrow... I'd rather not go through pains of OS updates if we don't have to.... Its hard to get the maint time in the hospital!!!


mstubbers Mon, 10/29/2007 - 07:59
User Badges:

Rob,


I believe this document is not worded well, but my interpetation of it is that even if you applied steps 1-4 which include the 4.4a(sr3a) patch you still need to apply patches


"Please Note:

If you applied the four software items which were required to make a Cisco Unified CallManager system Daylight Saving Time compliant in March 2007 you will be DST compliant with Cisco Unified CallManager Database, Phone load / Device packs and JRE version listed below.


However, for the Fall time changes you MUST update the MCS OS versions due to the following defect:


CSCsh20360: Looping in System Date & Time due to Daylight saving correction:"


The upgrade I applied did resolve my DST issue for the fall.


Cheers!

davidturner Mon, 10/29/2007 - 09:01
User Badges:

I am having the opposite problem. My Server time is correct and my 7940's and 7960's are correct but my 7941's and 7961's are an hour behind. Any ideas? Did I miss a patch for the phone loads or something?


Thanks


mciarfello Mon, 10/29/2007 - 09:50
User Badges:
  • Silver, 250 points or more

The 79x1 (and 7970) phones need at least 8.2(2)SR1 or above. Curious what your phone firmware is.



marcuscastellanos Mon, 10/29/2007 - 10:03
User Badges:

Well...


I'm currently on OS Image 2000.2.4

OS release 2000.2.7sr6

OS Upgrade 2000.2.7


Time was off... Currently I have my time on my servers set an hour behind to get the time to display correctly on phone...


Which patch do I need?


FYI here is the manual workaround that I performed...


CCM OS Manual Workaround 3.x and 4.x


On the new US DST date, Logon with sufficient privileges to CCM Windows Server (starting with Publisher)


Click Start, Settings, Control Panel, Date and Time


Adjust the time accordingly


Click on TimeZone tab


Uncheck the Automatically adjust clock for daylight savings changes


Click Apply or Ok


Repeat steps for all servers in the cluster.


Then on April 1, after 3:00 A.M., revert the changes back. This manual clock adjustment can be done by using the same method described in steps 1-4, check the automatically adjust clock for daylight savings changes and then steps 6-7 above. Note, however, that manually adjusting the clock on CallManager servers could result in a conflict in time which may produce time synchronization issues. For instance, adjusting the clock during any active call would result in incorrect call duration records. Therefore, adjusting the clock is best to be done when fewest active calls are present.


There are some workaround for this:


A) Manual DB change:


1. Using SQL, enterprise manager, access the CCM database.


Find the database named "CCM03XX" that has the hand (like share hand) on it. Go into that

CCM Database's table "TypeTimeZone" and find the time zone(s) your phones use. For each

time zone you use, update the following fields:

"stddate" to "0/11/0/1,2:0:0:0"

"dstdate" to "0/3/0/2,2:0:0:0"


2. Restart the CCM service ("Cisco CallManager").

3. If you use an NTP service, restart it as well.

4. Check your phones, the time should be correct now.


NOTE: If you have CCM failover configured you'll need to reset the phones for the changes

to take affect, the best way to do it is by resetting them from the device pool.






Rob Huffman Mon, 10/29/2007 - 11:23
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi David,


You may have the originally listed Firmware that was recommended for the Spring DST change 8.2(1) or 8.0(4)(I beleive). Of course this turned out not to work and the 7941 and 7961 phones need to be reset via ccmadmin to pickup the new time. This is until a new Firmware can be loaded.


Hope this helps!

Rob

davidturner Mon, 10/29/2007 - 13:15
User Badges:

yes i believe that you are correct. I am going to load the new firmware this evening.


Thanks


Actions

This Discussion