Has anyone else found a problem with the time shifting an hour forward on the first generation Cisco 7940's this morning. We are running CUCM 220.127.116.11000-1 and all of our SCCP 7940's are running firmware load 'P00308010200' with CUCM date/time groups set to the '(GMT) Europe/London*' timezone. It is as if the last Sunday in October daylight savings have kicked in a week early.
All CUCM nodes have the correct date/time and all of the newer java based Cisco 7942s ('SCCP42.8-5-3S') and 7941's ('SCCP41.8-5-3S') are fine showing the correct date/time.
Sounds like we could have a phone load or CUCM bug, just about to get this logged with Cisco. Not causing major issues at this time apart for generating calls to our support desk!
Solved! Go to Solution.
Final answer would be:
For those running already a CUCM 7.1.5 there is a CCO file already posted under:
I have this problem with 2 of my customers today (so far but it's early!). One is on CUCM 7.1.3a with 8.0.4 Loads on the 7940's 7960's and another on 7.1.3bSU2 with 8.1.2 loads. The 7941's and 7942's etc are showing the correct time, it's only the 2nd Gen Phones having the issue.
It may be a new bug, as the last sunday of the month of october is also the last day of the month. So the 2nd Gen phones seem to have jumped early.
If I get anywhere else on this, I'll post an update.
we have the same problem today with 6941 phone at SCCP 8.5.3 in CUCM 18.104.22.168011-1. Upgrade SCCP to 9.0.3a for 6941 doesn't fix it. 7970 and 7975 works well.
it is being tracked already in TAC.
So far affected versions are:
Only 7940/7960 series are affected.
3rd Gen phones looks to be not affected.
7.1.5 and 7.0.X versions apparently are not affected after my tests in the lab.
Will keep posting more information about it.
Same issue with CUCM 22.214.171.124000-2.
Our 7941's and 7961's running firmware SCCP41.8-5-2SR1S are all showing the correct time. Our 7940's and 7960's running firmware P00308010100 are all 1 hour behind.
Problem doesn't seem to be server, NTP time reference or call manager group related. Just looks like they have switched to GMT a week early.
On the bright side, I can stick the 7940 under my boses nose and claim I wasn't late this morning and substitute it for a 7961 at knocking off time. Result!
CUCM sends using SKINNY protocol a message to establish the date and time on the phone.
It sends 2 things:
Time and Date information explicitly:
CUCM is sending the right UNIX time stamp but the wrong time/date info.
BU is engaged to analyze the problem.
Thanks Fernado. Have a TAC case open but this seems to be the best source of information.
Anyone know how this is likely to effect CDRs (if at all), are these going to come over with the incorrect time? Have yet to test as I don't have an original 7940 to hand.
I don't think that CDR is affected but just to be sure I've carried out a rough and ready test from a 7940 to a 7961 (internal to internal) and then looked at the detail for the orginating extension (the 7940) in CAR. The originating time logged there is correct. Only the time listed under "placed calls" on the 7940 is incorrect, it is right everywhere else.
Hope this helps.
You are right, the CDR infomation contains UTC timestamps so it is not affected.
Only as you said the info displayed locally on the phones.
My customer is running 7940s on CUCM Cluster 126.96.36.199900-4
They ARE suffering from this issue.
Is there a TAC case reference number or BUG ID that I can quote regarding the issue.