Troubleshooting Cisco Callmanager CDR's

From NippAero

Here are a few things to look at when troubleshooting the CDR's.

Contents 1 Troubleshooting: 1.1 Make sure you have the following parameters in the PUB and the SUB: 1.2 Make sure these services are up and running: 1.3 Please check if you hava data available in the following databases: 1.4 Then here are the steps you have to follow. We are going to force ART to get all the CDR data into ART/CAR during the next scheduled loading time. 1.5 ADDITIONAL PROBLEMS: 2 NOTES:

Troubleshooting:

Make sure you have the following parameters in the PUB and the SUB:

Service -->Service Parameters: 

1. CDR Enabled Flag -->True

2. CDR Log Calls with zero duration flag-->True

3. Call Diagnostics Enabled -->True

System-->Enterprise Parameters-->CDR Parameters 

1. CDR File Time Interval: 1

2. CDR format: CDRs will be inserted into DB

3. CDR UNC Path: \\<ccmpub>\CDR

4. Cluster ID: StandAloneCluster or the name of the pub, when there is more than one server in the cluster.

5. Local CDR Path: C:\ProgramFiles\Cisco\CallDetail

6. Off Cluster CDR connection string: leave it blank!

Make sure these services are up and running:

• Cisco Database Layer Monitor
• Cisco CDR Analysis and Reporting Scheduler
• Cisco CDR Insert in PUB, if it is running in the SUB, there will be errors in the app logs.

Please check if you hava data available in the following databases:

Go to Start>Programs>MS SQL server>Enterprise Manager> Expand on MS SQL servers>SQL server group> Local> Databases There are 2 DB's we must check:

CDR>Call Detail Record>Right click>return all rows What is the DateTimeOrigination value for the last record you have there?

ART>Tbl_Billing_Data>Right click>return all rows Do you have data there?

Then here are the steps you have to follow. We are going to force ART to get all the CDR data into ART/CAR during the next scheduled loading time.

The scheduled loading time is under CAR-->System>CDR load

1. Go to programs > SQL Server > Query Analyzer

2. Login and select ART database

3. Run the following queries(2 times):

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

NOTE: Make sure you select art DB in the dropdown menu in the query analyzer. If not you will see this error:

ERROR 
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'Tbl_Load_History'

Then, please restart the Cisco CDR Analysis and Reporting (CAR) scheduler service. It should start loading CDRs as per your CDR load setting.

If you have selected art and still get this error:

Check the Load History table and check if there are entries. If there are no entries that's because the CDR parameters are not correctly setup.

ADDITIONAL PROBLEMS:

The Database Layer Monitor service on the Subscriber relies on having access to a Windows share on the Publisher, as defined in the CDR UNC Path in the enterprise parameters.

Go to the SUB and check that you can see the CDR folder of the publisher:

Start--> Run enter the CDR UNC Path as defined in the enterprise parameters such as \\CALLMANAGERPUB\CDR

You should see an Explorer window appear with the CDR folder on the publisher. If you get an error such as "invalid login" or "nonexisten path", verify that your passwords are synchronized (DB helper) and check that the C:\ProgramFiles\Cisco\CallDetail folder is still shared in teh Publisher. (Share name set to CDR)

NOTES:

When using CDR Search from the administrative CAR login, the search queries the realtime CDR database in SQL. In contrast, when doing any kind of reporting (like running Billing or "Top N by charge" reports), these reports are run against the ART database in SQL.

The ART database has more limitations than the CDR db has. For example, the ART db is updated from the realtime CDR db only once every 24 hours. Further, if there is more than one user associated with a device, the report will give results only for the "first" user associated with that device. For example, if there are two users associated with same device (MAC address), depending on which user the database sees as "first," the reports for all other associated users will always be empty. These are just some considerations to keep in mind when contrasting these two types of database query within CAR/ART.

If you want to run Billing or other reports instead of CDR searches on these users who are currently coming up "empty," you need to query SQL to find out all users associated with the device in question, and then remove all associations from that device except for the one you want.

I've included instructions below on how to query SQL for this info. I hope this helps. Please let me know if this resolves your issue, or if I can be of further assistance.

SQL QUERY INSTRUCTIONS:

---

To find which user(s) is associated with which mac address for ART/CAR purposes, we need to check the SQL database (this needs to be done on the PUBLISHER):

Start--->Programs--->Microsoft SQL Server--->Query Analyzer

Then enter in the following string:

-------------------------------------------
use art select User_Id, origDeviceName, destDeviceName from Tbl_Billing_Data
where origDeviceName = 'MAC_ADDRESS' or destDeviceName = 'MAC_ADDRESS' or
User_Id = 'USER_ID' 
-------------------------------------------

where "MAC_ADDRESS" is the MAC entry as seen on CCM (for ex: SEP000A41F97688)
where "USER_ID" is the actual userID as seen in global directoy (for ex: brshort)

Then highlight the entire search string and click on the green triangle in the menu bar at the top to execute the command/search.

You should then get some values returned below with the user_IDs associated to that MAC address. What you're concerned about are instances of MORE THAN ONE userID associated with a SINGLE mac address. Multiple mac addresses per user isn't a problem for CAR/ART, just the reverse.