/mcpCorresponding Sample Call Management Records "cdrRecordType","globalCallID_callManagerId","globalCallID_callId","nodeId","directoryNum", "callIdentifier","dateTimeStamp","numberPacketsSent","numberOctetsSent","numberPacketsReceived" "numberOctetsReceived","numberPacketsLost","jitter","latency","pkid","directoryNumPartition", "globalCallId_ClusterID","deviceName","varVQMetrics","duration","videoContentType","videoDuration", "numberVideoPacketsSent","numberVideoOctetsSent","numberVideoPacketsReceived","numberVideoOctetsReceived", "numberVideoPacketsLost","videoAverageJitter","videoRoundTripTime","videoOneWayDelay","videoReceptionMetrics", "videoTransmissionMetrics","videoContentType_channel2","videoDuration_channel2","numberVideoPacketsSent_channel2", "numberVideoOctetsSent_channel2","numberVideoPacketsReceived_channel2","numberVideoOctetsReceived_channel2", "numberVideoPacketsLost_channel2","videoAverageJitter_channel2","videoRoundTripTime_channel2","videoOneWayDelay_channel2", "videoReceptionMetrics_channel2","videoTransmissionMetrics_channel2" INTEGER,INTEGER,INTEGER,INTEGER,VARCHAR(50), INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,UNIQUEIDENTIFIER,VARCHAR(50),VARCHAR(50), VARCHAR(129),VARCHAR(600),INTEGER,VARCHAR(10),INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER, INTEGER,VARCHAR(600),VARCHAR(600),VARCHAR(10),INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER,INTEGER, VARCHAR(600),VARCHAR(600) 2,1,48553,1,"",29258891,1515145049,3775,649300,3775,604000,0,0,4,"50870a6d-193d-478f-8971-0dc641a6058a", "","StandAloneCluster","sip_trunk3_to_camserv_2_DO","",98,"",,,,,,,,,,"","","",,,,,,,,,,"","" 2,1,48553,1,"11011",29258890,1515145049,8900,7676700,8998,7676767,0,2,0,"7526cf73-ae78-48b1-9640-7ea19b546321","", "StandAloneCluster","SEPCD1111000011","",98,"main",0,0,0,0,0,0,0,0,0,"","TxFrameRate=0","",,,,,,,,,,"","" In the preceding example, Unified Communications Manager inserts the call statistics into the CMRs per the communicated information in the P-RTP-Stat header. If a P-RTP-Stat header comprises partial field values or any field is absent, Unified Communications Manager generates CMRs with available field values. Some of the fields in the CMRs are not populated due to fields unrelated to SIP trunk or if no call statistics are received from CUBE. Note In the following scenarios, there are no CMRs written for the SIP trunk: • P-RTP-Stat header is present without any fields in an incoming BYE message or 200 OK response to BYE message from CUBE. • P-RTP-Stat header is not present in an incoming BYE message or 200 OK response to BYE message from CUBE. • P-RTP-Stat header and fields are present in an incoming BYE message or 200 OK response to BYE message from CUBE but corresponding field values are empty. CMRs for Headsets Unified Communications Manager stores the call diagnostics details for Headsets. The details include call quality, packets lost, packets received, jitter, delay, and so on. Whenever there is a call between two phones using headsets, the diagnostics records for both the headsets populates separately in a column ‘Headset-Stat’. You can view the Serial Number and Metrics of the particular Headset used. Example The following example shows the sample BYE message for Headsets: BYE sip:1@10.77.29.46:5060;transport=tcp SIP/2.0 RTP-TxStat: Dur=13,Pkt=658,Oct=105280 Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 368 CMR Records CMRs for Headsets