The Cisco Unified Communications Manager system generates call management records (CMRs) . You can use this information for post-processing activities such as generating billing records and network analysis.
When you install your system, CMRs remain disabled by default. You can enable or disable CMRs at any time that the system is in operation. You do not need to restart Cisco Unified Communications Manager for the change to take effect. The system responds to all changes within a few seconds. The system enables CMR or diagnostic data separately from CDR data.
The CMR records store information about the quality of the streamed audio of the call.
When Cisco Unified Communications Manager places or receives a call, the system generates a CDR record when the call terminates. The system writes the CDR to a flat file (text file). Inside the Cisco Unified Communications Manager, the call control process generates CDR records. The system writes records when significant changes occur to a given call, such as ending the call, transferring the call, redirecting the call, splitting the call, joining a call, and so forth.
When CMR records are enabled, the number of records that are written varies by type of call and the call scenario. When Diagnostics are enabled, the device generates CMR records for each call. The system writes one CMR record for each IP phone that is involved in the call or for each Media Gateway Control Protocol (MGCP) gateway. The system sends these records to EnvProcessCdr where they get written to flat files.
The Cisco Unified Communications Manager generates CMR records but does not perform any post processing on the records. The system writes the records to comma-delimited flat files and periodically passes them to the CDR Repository. The CMR files represent a specific filename format within the flat file.
The following example shows the full format of the filename: tag_clusterId_nodeId_datetime_seqNumber
tag—Identifies the type of file, either CDR or CMR.
clusterId—Identifies the cluster or server where the Cisco Unified Communications Manager database exists.
nodeId—Identifies the node.
datetime—Specifies UTC time in yyyymmddhhmm format.
seqnumber—Specifies sequence number.
An example of the filename follows:
For Cisco Unified Communications Manager Business Edition 5000 installations, the value that is assigned to the clusterId equals 01.
Flat file format
The CMR flat files have the following format:
Line 1—List of field names in comma separated format.
Line 2—List of field types in comma separated format.
You can configure CMRs on the Service Parameters Configuration window in Cisco Unified Communications Manager Administration. To access the Service Parameters Configuration window, open Cisco Unified Communications Manager Administration and choose System > Service Parameters. Choose the Advanced button to display the complete list of Service Parameters. Select the Call Diagnostics Enabled parameter.
This parameter determines whether the system generates CMRs, also called call diagnostic records. Valid values specify Disabled (do not generate CMRs), Enabled Only When CDR Enabled Flag is True (generate CMRs only when the CDR Enabled Flag service parameter is set to True), or Enabled Regardless of CDR Enabled Flag (generates CMRs without regard to the setting in the CDR Enabled Flag service parameter). This represents a required field. The default value specifies Disabled.
Cisco has performed basic testing to measure CPU utilization when CDRs and/or CMRs are enabled. The CPU utilization testing was measured on subscribers and was not measured on the publishers. Your actual results can vary because of the CDR Loader settings and the CDR Management settings for external billing servers. The following table displays the results of these tests.
Be aware that these tests were performed with Cisco Unified Communications Manager Release 8.0(1).
Table 1 CDR and CMR CPU Utilization
CDRs and CMRs Enabled/Disabled
Average % Increase in Cisco Unified CM CPU Utilization