CDR Timestamp 1 Hour Behind--DST Issue

Unanswered Question
Mar 12th, 2007

When going through CDR Analysis and Reporting, timestamps are still 1 hour behind when searching by extension.

By doing SQL searches on the CDR database, it looks like the CDR data is timestamped correctly. The server time, and times on all the phones are correct. I assume something in the actual CAR interface. Perhaps java related??

Any insight is appreciated.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
oneillb Fri, 03/16/2007 - 07:40

I am having the same problem with CDR records. I have installed the DST updates and everything else is correct. We are running 4.1(3)sr4d.

jbarcena Fri, 03/16/2007 - 08:03

We have a bug opened for that issue:

CSCsh81417: CDR Analysis and Reporting does not reflect new DST changes

Symptom:

CallManager servers updated with all of the correct DST patches will report

calls in CDR Analysis and Reporting as one hour behind the actual time of the

call between March 11th and April 1st 2007 as well as between October 28th

and November 4th 2007.

The time stamp on the CDR record in the CDR table is correct but reports

generated with CDR Analysis and Reporting will be off by one hour.

Workaround:

Update the JRE component on your Publisher, from the following location:

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-utilpage

Reboot all the servers in the cluster to replicate the changes.

HTH

//Jorge

Actions

This Discussion