/mcpCDR Field Names 2000 finalCalledPartyNumber finalCalledPartyNumberPartition Phone 1000 origDeviceName Phone 3001 destDeviceName huntPilotDN huntPilotPartition 7 calledPartyPatternUsage Because the call is not answered, the huntPilotDN is not available in the CDR. The PatternUsage (7 = PATTERN_HUNT_PILOT) field gets set to 7 to indicate that the call was made to a hunt pilot. When the service parameter is not enabled, the finalCalledPartyNumber field denotes the member hunt DN. H.239 Unified Communications Manager supports H.239. This feature defines the procedures for use of up to two video channels in H.320-based systems and for labeling individual channels with a role of “presentation” or “live.” This procedure indicates the requirements for processing the channel and the role of the channel content in the call. Role labels apply to both H.320 and H.245 signaling-based systems. Several new CDR fields support a second video channel for both the origination and destination devices. This CDR provides an example of these new fields. H.239 CDR Example When A and B declare H.239 capability in Terminal Capability Set (TCS) and one, or both, of the endpoints initiates the receiving channel to have an extended video channel in an H.239 mechanism for presentation or video feed, the new CDR fields display in the CDR in addition to the existing fields of a video call. Calling party 51234 calls the called party 57890. Let 103 represent H.264, 187962284 represents 172.19.52.11, 288625580 represents 172.19.52.17, and 352 represents 352K. CDR Field Names 121 globalCallID_callId 101 origLegCallIdentifier 102 destLegIdentifier 51234 callingPartyNumber 57890 originalCalledPartyNumber 57890 finalCalledPartyNumber 57890 lastRedirectDn Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 302 CDR Records H.239