Technical information

4
Cisco Unified CallManager 4.2(3) Call Detail Record Definition
OL-10659-01
New and Changed Information
Cisco Unified CallManager Release 4.0(1)
The following list provides the features or changes for CDRs in Cisco Unified CallManager release
4.0(1):
• Identifies Multilevel Precedence and Preemption (MLPP)
– Adds the new field origPrecendenceLevel for the precedence level of the originating leg of the
call
– Adds the new field destPrecedenceLvel for the precedence level of the destination leg of the call
– MLPP utilizes existing cause codes 8, 9, 46, 50, and 128
• Identifies malicious calls by adding a new Comment field
• Drop any party feature utilizes existing cause fields: origCause_value and destCause_value
• The OnBehalfOf field contains a new code (value = 14) for the Immediate Divert feature and value
= 15 for Barge.
• The following new fields support video in Cisco Unified CallManager:
– origVideoCap_Codec
– destVideoCap_Codec
– origVideoCap_Bandwidth
– destVideoCap_Bandwidth
– origVideoCap_Resolution
– destVideoCap_Resolution
– origVideoTransportAddress_IP
– origVideoTransportAddress_Port
– destVideoTransportAddress_IP
– destVideoTransportAddress_Port
• Adds user login fields (callingPartyLoginUserID and finalCalledPartyLoginUserID) to ensure that
the system associates a valid UserID with a newly created phone device and that it gets properly
reported in CDRs
• Adds examples for different call scenarios including IDivert, Barge, and cBarge
Cisco CallManager Release 3.2
The change for CDRs in Cisco CallManager release 3.2 means that CDR records get written to
comma-delimited flat files (text) on the subscriber databases. The localCDRPath service parameter
specifies the directory to which the files are written. CDR and CMR records for each subscriber
periodically pass to the publisher database, and the CiscoInsertCDR service reads the records from the
flat files and inserts the records into the centralized SQL database.