Call detail records (CDR) detail the called number, the number that placed the call, the date and time that the call was started, the time that it connected, and the time that it ended. Call management records (CMRs, or diagnostic records) detail the jitter, lost packets, the amount of data sent and received during the call, and latency. CDR data comprises CDRs and CMRs collectively. A single call can result in the generation of several CDRs and CMRs. Cisco CallManager records information regarding each call in CDRs and CMRs. CDRs and CMRs, known collectively as CDR data, serve as the basic information source for CAR.
You access CAR from the Tools menu of Cisco CallManager Serviceability after you install the CAR plugin as described in the "Installing the CDR Analysis and Reporting (CAR) Plugin" section in the Cisco CallManager Serviceability Administration Guide.
All CAR reports use CDR data. CAR processes CDRs at the scheduled time and frequency. By default, CDR data loads from midnight to 5 a.m. on a daily basis; however, you can set the loading time, interval, and duration as needed.
CAR retrieves information that is not only present in the CDRs and CMRs, but is required for various reports, from the Lightweight Directory Access Protocol (LDAP) and configuration information from CAR database (that CAR administrator can modify).
show call history voice - Displays the call history table for voice calls.
To specify call detail record (CDR) storage time, use the dial-control-mib command, which has two sets of keyword and argument options. The max-size number option specifies the maximum size of the CDR event table. The valid range is from 0-500, and the default is 50. Setting the value to 0 disables the CDR feature.
The retain-timer number option specifies the length of time in minutes that entries will remain in the call history table. The valid range is from 0-2147483647 minutes, and the default is 15. Setting the value to 0 prevents any call history from being retained.
The Cisco Unified CME GUI provides call history table information so that a network administrator can monitor the call history information for unknown callers and use this information to disallow calling activities based on select calling patterns. The call history log should be configured to perform forensics and accounting and allow the administrator to track down fraudulent calling patterns. Configure the following commands to log call activity and call history:
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.