Table 7-13 documents some common problems and errors and suggests possible solutions with regard to CDR data generation and storage. This is not an exhaustive list.
Problem |
Possible Cause |
Solution |
---|---|---|
No CDRs are written to the central data store. |
CallManager is shipped with CDR data generation disabled. The most common problem is that you have not enabled CDR data generation. |
Set the CDR Enabled Flag service parameter to True on all CallManager nodes in the cluster. If you also want CMR data, you should set the Call Diagnostics Enabled service parameter to True also. |
CDR data is logged for some calls, but not for others. |
If you enable CDR data generation by setting the CDR Enabled Flag service parameter to True on some CallManager nodes in the cluster but not on other nodes, the system logs CDR data only from the CallManager nodes where you enabled CDR data generation. |
Set the CDR Enabled Flag service parameter to True on all CallManager nodes in the cluster. |
No CMRs are written to the central data store. |
The system does not generate CMR data unless the Call Diagnostics Enabled service parameter is enabled. |
Set the Call Diagnostics Enabled service parameter to True on all CallManager nodes in the cluster. |
CMR data is logged for some IP phones and MGCP gateways, but not for others. |
The current setting of the Call Diagnostics Enabled service parameters is not the same on all CallManager nodes in the cluster. |
Set the Call Diagnostics Enabled service parameter to True on all CallManager nodes in the cluster. |
CDR flat files get copied into the "BAD" directory on the Publisher. |
The most common reasons are these: The flat file has been corrupted. There is one or more bad characters in a CDR entry in the file. The CDR Insert service does not have database access. |
The corrupted file will have to be cleaned up or repaired. If there is one or more bad characters in a CDR entry in the flat file, that CDR was not be inserted into the database but the remainder of the entries were inserted. |
Cisco CallManager Architecture
Call Routing
Station Devices
Trunk Devices
Media Processing
Manageability and Monitoring
Call Detail Records
Appendix A. Feature List
Appendix B. Cisco Integrated Solutions
Appendix C. Protocol Details
Index