CDR Issues

[k6lw]

Call Manager 3.3.3 SR4a

I am trying to run some CDR reports for the current period, but I keep getting an error message that I only have data from Jun 2003 to May 18th 2004.

If I just grab raw data, it appears that the data is available.

I have CDR activated on all three of my call managers.

Any way to get the CDR to recognize that there is data available up to the present day?

Lee

[aaronw.ca]

Since CDR generation is enabled and you have verified that current CDR is physically present in the database, the issue there is likely not the CallManagers, but your reporting application (I assume you are using CAR?). You need to instruct your reporting application to get the latest CDR.

[k6lw]

I think I know (now that's a shock) what is happening as ever since I discovered that the CDR was not active or running in one of the web settings, the system has slowly been catching up. Originally when I posted the note, the latest data was stating May 9. The next time I checked it was May 11. Today it says May 20th. Therefore I believe it is managing to load a couple of days worth of data every night, and it will eventually "catch up".

Lee

[ashever]

I am having the same issues, what "web settings" are you referring to?....

Thanks Joe

[k6lw]

Joe,

Log into the serviceability and then go to the control center. Click on each of your servers and make sure the CDR Insert is activated. (Green Triangle)

Then log into the CDR Analysis and Recording page.

Go to System and then Control Center and ensure the CDR Analysis and Reporting Scheduler is configured and operating. In my case is was configured, but NOT running. It is now and every day I get closer to being able to review the latest data. It's now up to June 4th.

Lee

[kthorngr]

You will only want the CDR Insert service running on the Publisher. Running this on the subscriber will not help and will generate errors in the application event log. The CDR Insert Service just copies the CDR records from the CDR folder on the Publisher to the DB. The subscribers copy the CDR records to this folder on the Publisher.

Ashever,

If you are getting the error that records are only available before a certain date then you may need to follow this procedure. Make sure to delete the data in the tables not the tables themselves. This will cause CAR to reload all of the CDRs.

1) Go to Programs -> SQL Server -> Ent Mgr SQL Server -> SQL server Group - choose the CM server.

Choose ART database.

2) Delete all the records in the following table. To delete the records, select the table, open it

and choose Delete on the SQL menu and then run the command.

delete from Tbl_Load_History

delete from Tbl_Dump_PkID

delete from Tbl_Error_Id_Map

delete from Tbl_Billing_Data

delete from Tbl_Billing_Error

delete from Tbl_Dump_CallDetailRecord

delete from Tbl_Dump_CallDetailRecordDiagnostic

3) This will force ART to get all the CDR data in the database when it next loads data.

This procedure willonly work if the CDR DB is being properly populated.

Kev

[k6lw]

Kev;

According to page 505 of the "Cisco Call Manager Fundamentals" book, " You should configure CdrEnabled to be the same for all Call Managers Nodes in the cluster to get consistent and predictable results. If you set the configuration differently on the nodes, some CDR data is not logged."

AFAICT the CDR is back fully operational on my three server cluster.

Lee

[maharris]

Something seems to have changed since that book (which is generally really good) was written, at least they clarified where you should have this service running at some point:

Cisco CDR Insert

Reads transferred files, places contents into CDR database, removes old files

Activate on the server that contains the CDR database.

Cisco recommends that you house the CDR database on the publisher database server.

That is from the Service Activation chapter of the CM3.3(2) Serviceability Admin Guide:

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008011b4c2.html#42236

We ran across it when we were trying to find something that documented what services you needed to have running where, and this had a nice little table. I don't think it does anything terrible if you have it on when you don't need it, besides generate some errors maybe.

Mary Beth

[cisco4me]

Hi,

I recently installed CDR & Analysis Reporting tool. After I logged in, I 'delegate' admin rights to an user called huntl. But since then, I could no longer login to CDR & Analysis Reporting tool. Can anyone help?

>Then log into the CDR Analysis and Recording page.

>Go to System and then Control Center and ensure the >CDR Analysis and Reporting Scheduler

Also, I remembered that even when I logged in before, the only option I got is to assign & revoke rights. I never seen any CDR Analysis and Reporting Scheduler before.

Would need help.

Cheers,

Hunt Lee

[maharris]

Hi! You may have gotten past this already, but just in case - when you are trying to log in after you have granted admin rights to huntl, are you logging in with that account, or are you still trying to use the original login? That first one only works once, and the only thing you see there is the ability to assign admin rights. From then on, you need to log in with a user id that has been granted admin rights, and then you see all the rest of the stuff.

Mary Beth

[jgentsch]

I followed your steps as described and am still have the same problem even after the CDR loader did its thing.