cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
827
Views
0
Helpful
2
Replies

CDR Fields Missing in Exported CDR File

jasonshaw1984
Level 1
Level 1

Recently I've noticed that the exported CDR file from CUCM 7.1.5 is now missing fields that it had before. As far as I know, no changes have be made.

Previously, CDR files contained the following fields:

cdrRecordType

globalCallID_callManagerId
globalCallID_callId
origLegCallIdentifier
dateTimeOrigination
origNodeId
origSpan
origIpAddr
callingPartyNumber
callingPartyUnicodeLoginUserID
origCause_location
origCause_value
origPrecedenceLevel
origMediaTransportAddress_IP
origMediaTransportAddress_Port
origMediaCap_payloadCapability
origMediaCap_maxFramesPerPacket
origMediaCap_g723BitRate
origVideoCap_Codec
origVideoCap_Bandwidth
origVideoCap_Resolution
origVideoTransportAddress_IP
origVideoTransportAddress_Port
origRSVPAudioStat
origRSVPVideoStat
destLegIdentifier
destNodeId
destSpan
destIpAddr
originalCalledPartyNumber
finalCalledPartyNumber
finalCalledPartyUnicodeLoginUserID
destCause_location
destCause_value
destPrecedenceLevel
destMediaTransportAddress_IP
destMediaTransportAddress_Port
destMediaCap_payloadCapability
destMediaCap_maxFramesPerPacket
destMediaCap_g723BitRate
destVideoCap_Codec
destVideoCap_Bandwidth
destVideoCap_Resolution
destVideoTransportAddress_IP
destVideoTransportAddress_Port
destRSVPAudioStat
destRSVPVideoStat
dateTimeConnect
dateTimeDisconnect
lastRedirectDn
pkid
originalCalledPartyNumberPartition
callingPartyNumberPartition
finalCalledPartyNumberPartition
lastRedirectDnPartition
duration
origDeviceName
destDeviceName
origCallTerminationOnBehalfOf
destCallTerminationOnBehalfOf
origCalledPartyRedirectOnBehalfOf
lastRedirectRedirectOnBehalfOf
origCalledPartyRedirectReason
lastRedirectRedirectReason
destConversationId
globalCallId_ClusterID
joinOnBehalfOf
comment
authCodeDescription
authorizationLevel
clientMatterCode
origDTMFMethod
destDTMFMethod
callSecuredStatus
origConversationId
origMediaCap_Bandwidth
destMediaCap_Bandwidth
authorizationCodeValue
outpulsedCallingPartyNumber
outpulsedCalledPartyNumber
origIpv4v6Addr
destIpv4v6Addr
origVideoCap_Codec_Channel2
origVideoCap_Bandwidth_Channel2
origVideoCap_Resolution_Channel2
origVideoTransportAddress_IP_Channel2
origVideoTransportAddress_Port_Channel2
origVideoChannel_Role_Channel2
destVideoCap_Codec_Channel2
destVideoCap_Bandwidth_Channel2
destVideoCap_Resolution_Channel2
destVideoTransportAddress_IP_Channel2
destVideoTransportAddress_Port_Channel2
destVideoChannel_Role_Channel2

CDR Files now only contain the following fields:

cdrRecordType
globalCallID_callManagerId
globalCallID_callId
orignodeId
destnodeId
origlegcallIdentifier
destlegidentifier
orignumberPacketsSent
orignumberOctetsSent
orignumberPacketsReceived
orignumberOctetsReceived
orignumberPacketsLost
destnumberPacketsSent
destnumberOctetsSent
destnumberPacketsReceived
destnumberOctetsReceived
destnumberPacketsLost
origjitter
destjitter
origlatency
destlatency
pkid
origdeviceName
destdeviceName
origvarVQMetrics
destvarVQMetrics
globalCallId_ClusterID
callingPartyNumber
finalCalledPartyNumber
callingPartyNumberPartition
finalCalledPartyNumberPartition

Does anyone know what may have happened and how to correct this issue?

Thanks!

2 Replies 2

Manish Gogna
Cisco Employee
Cisco Employee

Comparing the two tables it is quite clear that cdr data for video related calls is missing. Were there any changes on the system related to video endpoints or applications?

HTH

MAnish

jasonshaw1984
Level 1
Level 1

I've resolved this issue. It appears that the CMR records were being returned. When selected CDR only, the proper report was generated.