Technical information

12
Cisco Unified CallManager 4.2(3) Call Detail Record Definition
OL-10659-01
Working with CDRs
Note You need access to both the configuration database and CDR database to properly resolve
the CDR information.
The machine that serves the primary CCM0300 database serves as the machine that is the central
collector of the CDR information.
You can find the primary database (machine and name) that the cluster currently is using by opening
Cisco Unified CallManager Administration, choosing Help > About Cisco Unified CallManager, and
clicking the Details button. You can also check the registry on machines that host a database. Look at
the registry key, \\HKEY_LOCAL_MACHINE\Software\Cisco Systems Inc.\DBL, for DBConnection0.
This string item contains a connection string that includes the machine name and database name of the
primary database.
The following table specifies the user ID and password that you should use when you access the Cisco
Unified CallManager database.
Removing Records
Because the Cisco Unified CallManager relies on third-party packages to process the CDR data, you
should remove the CDR data after all packages finish with the data. Use the CiscoCCMCDR user to
remove the records. The CiscoCCMCDR user designates the Microsoft SQL Server account that can be
used to read/write to the CDR and CMR tables.
If CDRs accumulate to a configured maximum, the system removes the oldest CDRs along with related
CMR records once a day. The default maximum specifies 1,500,000 CDRs.
When removing CDR data after analysis, be sure to remove all related CMR records also.
Tips You should remove records more often than once a day or week in large systems. Queries
to remove records consume CPU time and transaction log space relative to the size of the
table: the smaller the table, the quicker your query.
Database Tables SQL User ID Password Capability
CDR CallDetailRecord,
CallDetailRecordDiagnostic
CiscoCCMCDR dipsy Read/Write
CCM0300 All CiscoCCMCDR dipsy Read only