CDR Problem

Answered Question
Feb 19th, 2007

I have CCM 4.1(2). My CCM stopped making the call detail records all of a sudden. All CDR services are up, SQL running fine, no issue, nothing in the event logs but its not working. Any clue how to diagnose the problem?? Thanks in advance.

Sheeraz

I have this problem too.
0 votes
Correct Answer by jbarcena about 9 years 7 months ago

>>>Verify that "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler" services are running ONLY in the Publisher Call Manager:

in your publisher callmanager server, go to start > programs > administration tools > services > verify the status for services "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler". If they are not "started", please restart them (just right-click on the service and select "restart").

If "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler" are running also in the subscriber servers, please stop them.

-------------------

>>>Verify service parameters in callmanager servers (publisher and subscriber).

--go to ccm admin > service > service parameters > select a callmanager server from the drop-down list > at "service" please select "Cisco CallManager" > click on "advanced" > verify that the following parameters are set to the correct values:

CDR Enabled Flag = True

CDR Log Calls with Zero Duration Flag = True

Call Diagnostics Enabled = True

***Repeat the same procedure for all callmanager servers in your cluster***

--Now go to ccm admin > service > service parameters > select a callmanager server from the drop-down list > at "service" please select "Cisco Data Base Layer Monitor" > verify that the following parameter is set to the correct value:

Max CDR Records = 1500000

***Repeat the same procedure for all callmanager servers in your cluster***

--Now go to ccm admin > system > enterprise parameters > verify that the following parameters are set to the correct values:

CDR File Time Interval (min) = 1

CDR Format = CDRs will be inserted into database

CDR UNC Path = \\\CDR

Local CDR Path = C:\Program Files\Cisco\CallDetail

***Repeat the same procedure for all callmanager servers in your cluster***

-------------------

>>>Please go to start > programs > administration tools > services and restart the following services after hours:

1) Restart service "Cisco database Layer Monitor" on publisher and subscriber servers.

2) Restart service "Cisco CDR Insert" on the publisher server.

3) Restart service "Cisco CDR Analysis and Reporting Scheduler" on the publisher server.

-------------------

>>>Run SQL querys:

In your publisher server, go to start > programs > SQL Server > Query Analyzer > SQL Server: (local) ; Select "windows authentication"; click on "OK" > select the "ART" database from the drop-down menu. Run the following queries (just copy and paste the following in the main window, then click on the "execute query" icon):

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

-------------------

Login into the CAR tool > go to the "system" menu > scheduler > CDR Load > Load CDR & CMR > by default, Time will be set at 00 Hr, 00 Min; Loading Interval = Every 24 hours; please change the "Duration" parameter to 120 min.

---------------------

Restart the services again.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
daljeetsingh1_2 Mon, 02/19/2007 - 03:46

Hi Sheeraz,

I am hoping you have already checked

1) CDR Schedular service up and running.

2) CDR repository service up and running?

3) What is the load time and load duration?

Did we try to reboot the Above service by any chance?

If we have already done all this. Please let me know we need to goto the database to see if the flat files are getting stored.

And please collect the CDR details logs and restart the service and see in logs if we are getting any error message.

Regds,

Daljeet

sheerazkhatri Mon, 02/19/2007 - 21:07

Hi Daljeet

CDR schdular is up and running.

CDR repository is up and running

Load time is 1AM and duration is 4 hours.

I rebooted the service multiple times, restarted the CDR insert service as well but nothing happened. Any further suggestion Please ?

Correct Answer
jbarcena Mon, 02/19/2007 - 05:32

>>>Verify that "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler" services are running ONLY in the Publisher Call Manager:

in your publisher callmanager server, go to start > programs > administration tools > services > verify the status for services "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler". If they are not "started", please restart them (just right-click on the service and select "restart").

If "Cisco CDR Insert" and "Cisco CDR Analysis and Reporting Scheduler" are running also in the subscriber servers, please stop them.

-------------------

>>>Verify service parameters in callmanager servers (publisher and subscriber).

--go to ccm admin > service > service parameters > select a callmanager server from the drop-down list > at "service" please select "Cisco CallManager" > click on "advanced" > verify that the following parameters are set to the correct values:

CDR Enabled Flag = True

CDR Log Calls with Zero Duration Flag = True

Call Diagnostics Enabled = True

***Repeat the same procedure for all callmanager servers in your cluster***

--Now go to ccm admin > service > service parameters > select a callmanager server from the drop-down list > at "service" please select "Cisco Data Base Layer Monitor" > verify that the following parameter is set to the correct value:

Max CDR Records = 1500000

***Repeat the same procedure for all callmanager servers in your cluster***

--Now go to ccm admin > system > enterprise parameters > verify that the following parameters are set to the correct values:

CDR File Time Interval (min) = 1

CDR Format = CDRs will be inserted into database

CDR UNC Path = \\\CDR

Local CDR Path = C:\Program Files\Cisco\CallDetail

***Repeat the same procedure for all callmanager servers in your cluster***

-------------------

>>>Please go to start > programs > administration tools > services and restart the following services after hours:

1) Restart service "Cisco database Layer Monitor" on publisher and subscriber servers.

2) Restart service "Cisco CDR Insert" on the publisher server.

3) Restart service "Cisco CDR Analysis and Reporting Scheduler" on the publisher server.

-------------------

>>>Run SQL querys:

In your publisher server, go to start > programs > SQL Server > Query Analyzer > SQL Server: (local) ; Select "windows authentication"; click on "OK" > select the "ART" database from the drop-down menu. Run the following queries (just copy and paste the following in the main window, then click on the "execute query" icon):

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

-------------------

Login into the CAR tool > go to the "system" menu > scheduler > CDR Load > Load CDR & CMR > by default, Time will be set at 00 Hr, 00 Min; Loading Interval = Every 24 hours; please change the "Duration" parameter to 120 min.

---------------------

Restart the services again.

daljeetsingh1_2 Mon, 02/19/2007 - 23:36

First check in the TBL_Billing_data what is the date and time of the last record.

We need to see what we are seeing in this Table which is very important. If the last record is not the latest than data is not being pushed to CDR for reporting.

Please see the results and let us know and Enable CDR insert Debugs and pls make sure you collect the traces after the loading time specified on ccm.

There are few bugs as wel, if the results of your queries show fine than prob we need to see any matching bug.

sheerazkhatri Tue, 02/20/2007 - 00:48

Dear Daljeet

Thank you for your support. Actually the link that you posted earlier on helped me in debugging the root cause. Although I lost few CDR records but its working now. Thank you.

Sheeraz

Actions

This Discussion