Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
© 2000 Cisco Systems, Inc. 78
The primary database (machine and name) currently in use by the cluster can be found by
clicking on the Details button of Cisco CallManager Administration (click Help to reach the
Welcome screen where the Details button is located). The registry on machines hosting a
database can also be checked. Look at the registry key:
“\\HKEY_LOCAL_MACHINE\Software\Cisco Systems Inc.\DBL” for the item called
DBConnection0. This string item contains a connection string similar to that shown above with
the machine name and database name of the primary database.
Access is controlled by use of SQL Users. The following table specifies the UserID and
password that should be used when accessing the Cisco CallManager database.
Tables SQl UserID Password Capability
CallDetailRecord,
CallDetailRecordDiagnostic CiscoCCMCDR dipsy Read/Write
(Other) CiscoCCMReader cowboys Read only
Removing Records
Since Cisco CallManager is relying on third party applications to post-process the CDR data, you
should remove the CDR data when all applications are through with the data. Since this involves
modifying the database, the CiscoCCMCDR user should be used.
If CDR records accumulate to a configured maximum (10,000,000 CDR records), then the oldest
CDR records will be removed along with related CMR records once a day.
When removing CDR data after analysis, be sure to remove all related CMR records also.
Table Schema
Detailed information about the format and use of each field in the CDR is provided later in this
appendix.
The main tables to be used are the CallDetailRecord table, which holds CDR records, and the
CallDetailRecordDiagnostic table, which holds CMR records. The CallDetailRecord table is
related to the CallDetailRecordDiagnostic table via the two GlobalCallID columns,
GlobalCallID_callManagerId and GlobalCallID_callId. There may be more than one CMR per
CDR.
The CallDetailRecord table holds information about the endpoints of the call and other call
control/routing aspects of the call. The CallDetailRecordDiagnostic table holds information
about the quality of the streamed audio of the call.