There is a setting in CallManager that defines the max number of CDR records to keep in the CDR database. By default, CallManager 3.0 had a setting of 10 million, and in 3.1 and newer versions this setting is 1.5 million records. You can find the setting for your CallManager in the "Service Parameters" configuration of ccmadmin (in 3.2 it's under the "Cisco Database Layer Monitor" category).
CallManager will automatically delete older CDR records to ensure that the number of records in your CDR database stays below the specified limit, so this is not a severe error, if this is indeed what it represents.
However, having a CDR database with that many records may affect the performance of your CallManager. There are a number of ways to maintain a the CDR database.
One solution is to use CAR (CDR Analysis and Reporting), as it provides a way to automate this through a scheduled CDR database purge.
CAR is downloadable from Cisco Software Centre, and you can find CAR documentation on the Cisco website. CAR also includes several reports that you may find useful, though they are not as full-featured as a complete Call-Accounting package.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...