/mcpFor Hold and Resume calls on SCCP devices, multiple CMR Records are generated based on the number of times the call is put on hold. Note The 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. Filename Format 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 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: • cmr_Cluster1_02_200404061011_6125 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. • Line 3—Data in comma separated format. • Line 4—Data in comma separated format. The following example shows a flat file: Line1-“cmrRecordType”,“globalCallID_callManagerId”,“globalCallID_callId”,“origLegCallIdentifier”,... Line2-INTEGER,INTEGER,INTEGER,INTEGER,... Line3-1,1,388289,17586046,... Line4-1,1,388293,17586054,... CMRs for SIP Trunks Unified Communications Manager stores end-of-call video and audio information and metrics in Call Management Records (CMRs) for incoming and outgoing SIP trunk calls through Cisco Unified Border Element (CUBE) or SIP IOS gateways. CUBE sends the call statistics in a P-RTP-Stat header either in a BYE message or a 200 OK response to BYE message to update the CMRs in Unified Communications Manager. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 366 CMR Records CMRs for SIP Trunks