Auth Code Description
authCodeDescriptionProvides a description of the FAC. Default - Empty string “” or null.
- Type
- text
- Source representation
- Text String
- Category
- Call details
Source: www.cisco.com page=238
133 fields from the same catalog used by the analyzer. Source descriptions retain their documented defaults and version qualifications.
authCodeDescriptionProvides a description of the FAC. Default - Empty string “” or null.
Source: www.cisco.com page=238
authorizationCodeValueDisplays the Forced Authorization Code (FAC) that is associated with the call. Default - Empty string “” or null.
Source: www.cisco.com page=239
authorizationLevelDisplays the level of the FAC. Default - 0
Source: www.cisco.com page=238
callSecuredStatusDisplays the highest security status that is reached during a call. For example, if the call is originally unsecured, and later the call changes to secured, the CDR contains 1 for “Secured” even though different portions of the call have different status values. 0 - Non-secured 1 - Authenticated (not encrypted) 2 - Secured (encrypted) Default - 0 (Non-secured)
Source: www.cisco.com page=238
calledPartyPatternUsageIndicates the pattern of the called party. Default value specifies 5 (PATTERN ROUTE). _ • If the huntPilotDN is populated, use the huntPilotDN field value as the hunt pilot. • If the huntPilotDN is not available, check the pattern usage (7 =PATTERN HUNT PILOT) in the CDR table to identify the call _ _ type. If this call is a hunt list call, use the finalCalledPartyNumber as the huntPilotDN. Possible value for the fields: • 0 CallPark PATTERN CALL PARK _ _ • 1 Conference PATTERN CONF _ • 2 Device PATTERN DEVICE _ • 3 Translation PATTERN TRANSLATION _ • 4 Call Pick Up Group PATTERN CALL PICK UP GROUP _ _ _ _ • 5 Route PATTERN ROUTE _ • 6 Message Waiting PATTERN MESSAGE WAITING _ _ • 7 Hunt Pilot PATTERN HUNT PILOT _ _ • 8 Voice Mail Port PATTERN VOICE MAIL PORT _ _ _ • 9 Domain Routing PATTERN ROUTE DOMAIN _ _ • 10 IPAddress Routing PATTERN ROUTE IPNET _ _ • 11 Device template PATTERN DEVICE TEMPLATE _ _ • 12 Directed Call Park PATTERN DIRECTED CALL PARK _ _ _ • 13 Device Intercom PATTERN DEVICE INTERCOM _ _ • 14 Translation Intercom PATTERN TRANSLATION INTERCOM _ _ • 15 Translation Calling Party Number PATTERN TRANSLATION CALLING PARTY NUMBER _ _ _ _ • 16 Mobility Handoff PATTERN MOBILITY HANDOFF _ _ • 17 Mobility DTMF PATTERN MOBILITY DTMF _ _ • 18 Mobility IVR PATTERN MOBILITY IVR _ _ • 19 Device Intercom Template PATTERN DEVICE INTERCOM TEMPLATE _ _ _
Source: www.cisco.com page=243
callingPartyNumberSpecifies a numeric string of up to 25 characters that indicates the calling party number if the calling party is identified with a directory number. If the calling party uses a blended address in the identity headers, this field contains the directory number portion of the blended address. For calls that originate at a Cisco Unified IP Phone, this field shows the extension number of the line that is used. For incoming H.323 calls, this field specifies the value that is received in the Calling Party Number field in the Setup message. This field reflects any translations that are applied to the Calling Party Number before it arrives at the Unified Communications Manager (such as translations at the gateway). For the server calls, where Unified Communications Manager originates a half call without a calling party, this field may remain empty. CallingPartyNumber could contain a SIP URI. Default - This field gets populated based on these rules.
Source: www.cisco.com page=227
callingPartyNumberPartitionIdentifies unique partition name that is associated with the CallingPartyNumber field because Unified Communications Manager supports multiple Cisco Unified IP Phones with the same extension number in different partitions. For calls that ingress through an H.323 gateway, this field remains blank. Default - Empty string “”. If the original called party does not have a partition, this field remains empty.
Source: www.cisco.com page=235
callingPartyNumber_uriSpecifies an alphanumeric string of up to 254 characters that identifies the calling party if the calling party uses a directory URI for call addressing. If the calling party uses a blended address in the identity headers, this field contains the directory URI portion of the blended address. Default - Empty string “”. If the calling party does not use a directory URI, the field stays empty.
Source: www.cisco.com page=245
callingPartyUnicodeLoginUserIDSpecifies the calling party login user ID. The format of this field specifies UTF 8. _ Default - Empty string “”. If the user ID does not exist, this field stays empty.
Source: www.cisco.com page=227
cdrRecordTypeDefines the type of record. The following valid values apply: • 0—Start call detail record (not used) • 1—End call detail record (CDR) • 2—CMR record Default - For CDRs, this field always remains1.
Source: www.cisco.com page=225
clientMatterCodeDisplays the client matter code. Before the system extends a call, the user enters a client matter code that can be used for assigning account or billing codes to calls. Default - Empty string “” or null.
Source: www.cisco.com page=238
commentAllows features to add text to the CDRs. This text can describe details about the call. For example, the following field flags malicious calls: Tag—CallFlag Value—MALICIOUS Default - Empty string “”.
Source: www.cisco.com page=237
currentRoutingReasonDisplays the reason why the call was intercepted for the active call. This field is used with the external call control feature. See topics related to routing reason values for external call control for a list of reasons. Default value is 0.
Source: www.cisco.com page=242
dateTimeConnectIdentifies the date and time that the call connects. The time gets stored as UTC. If the call is never answered, this value shows zero. Default - 0. If the call is never connected, this field stays 0.
Source: www.cisco.com page=234
dateTimeDisconnectIdentifies the date and time when the call is cleared. This field gets set even if the call never connects. The time gets stored as UTC. Default - Ensure that this field is populated.
Source: www.cisco.com page=234
dateTimeOriginationIdentifies the date and time when the user goes off the hook or the date and time that the H.323 SETUP message is received for an incoming call. The time gets stored as UTC. Default - Ensure that this field is populated.
Source: www.cisco.com page=226
destCallTerminationOnBehalfOfSpecifies code that identifies why the destination was terminated. For example, if the destination of the call hangs up the phone, the OnBehalfOf code shows “12” for Device. If the call terminates because of a transfer, the OnBehalfOf code shows “10” for Transfer. See topics related to CDR field descriptions for a list of the codes. This release added new OnBehalfOf codes. Default - 0
destCallTerminationOnBehalfOf: examples and troubleshooting
Related: Origin Call Termination On Behalf Of
Source: www.cisco.com page=236
destCause_locationFor clearing causes that are received over ISDN signaling links, the ISDN release message indicates this location field. See topics that are related to call termination cause codes for a listing of the valid values per Q.850. For clearing causes that Unified Communications Manager creates internally, this value equals zero. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Cause location
Source: www.cisco.com page=232
destCause_valueReflects the reason for the calss that the destination party cleared. See topics that are related to call termination cause codes for a listing of the valid values per Q.850. For calls that the originating party clears, this field stays zero. In addition to the standard values that are described in Q.850, when a call gets split by a feature (transfer or conference), the CDR terminates, and this field gets set to 393216. This represents a proprietary value for this field. Default - 0. If the destination cannot be reached, this field stays 0.
destCause_value: examples and troubleshooting
Related: Origin Cause value
Source: www.cisco.com page=232
destConversationIdSpecifies a unique identifier that is used to identify the parties of a conference call. For conference chaining scenarios, the origConversationID and destConversationID fields identify which conferences are chained together. Default - 0
Related: Origin Conversation Id
Source: www.cisco.com page=237
destDeviceNameSpecifies the text string that identifies the name of the destination device. Default - Empty string“”. If the original device does not have a name, this field stays empty.
Related: Origin Device Name
Source: www.cisco.com page=236
destDeviceSessionIDIndicates the call Session ID of the destination device. When the session terminates, the system generates a CDR record and the field is populated with the destination device Session ID for the particular call. The maximum length of this field is restricted to 127 characters. For example, destDeviceSessionID = 47755a9de7794ba387653f2099600ef2 Default—empty string “”.
Introduced in CUCM 12.5(1)SU1; not first introduced in 15.
Related: Origin Device Session ID
Source: www.cisco.com page=248
destDeviceTypeIndicates whether the device that was called was a Spark client that is anchored to Cisco Unified Communications Manager over the Spark Remote Device: • If yes, this field indicates "CiscoSparkRemoteDevice" • If no, this field is empty. Note If the Spark client "rings" and the CDR Log Calls with Zero Duration Flag service parameter is True, this field gets populated as 'CiscoSparkRemoteDevice' even if an enterprise number was dialed with "Ring all shared lines" configured.
Related: Origin Device Type
Source: www.cisco.com page=248
destDTMFMethodDisplays the DTMF method that the destination uses. 0 - No DTMF - Use ANY matched DTMF.1 - OOB - Use OOB if endpoints behind SIPTrunk support it.2 - 2833 - Use RFC2833 if endpoints behind SIPTrunk support it.3 - OOB and 2833 - Use both KPML and RFC2833 if endpoints behind SIPTrunk can support both.4 - Unknown. Default - 0 (No preference)
Related: Origin DTMFMethod
Source: www.cisco.com page=238
destIpAddrIdentifies the v4 IP address of the device that terminates the call signaling. For Cisco Unified IP Phones, this field specifies the v4 address of the phone. For PSTN calls, this field specifies the v4address of the H.323 gateway. For intercluster calls, this field specifies the v4address of the remote Unified Communications Manager. Default - 0. If the destination cannot be reached, this field stays 0. If the v4 address does not exist for this device, the field equals 0.
Related: Origin Ip Addr
Source: www.cisco.com page=231
destIpv4v6AddrComprises an alphanumeric string of up to 64 characters. This field identifies the IP address of the device that terminates the call signalling. The field can be either in IPv4 or IPv6 format depending upon the type of IP address that gets used for the call. For Cisco Unified IP Phones, this field is the address of the Cisco Unified IP Phone. For PSTN calls, this field is the address of the gateway. For intercluster calls, this field is the address of the remote Unified Communications Manager. The IP addressis either in dotted decimal format or in colon separated hexadecimal format. Default - Empty String “” or null. If the destination does not get reached, this field stays empty.
Related: Origin Ipv4v6 Addr
Source: www.cisco.com page=239
destLegIdentifierIdentifies the terminating leg of a call. This value remains unique within a cluster. If the leg of a call persists across several sub-calls and, consequently, several CDRs (as during a call transfer), this value remains constant. Default - 0. If the destination cannot be reached, this field stays 0.
Source: www.cisco.com page=230
destMediaCap_BandwidthDisplays the media bandwidth that is used at the destination of the call. Default - 0
Related: Origin Media Cap Bandwidth
Source: www.cisco.com page=239
destMediaCap_g723BitRateThis field is not used in the current release of Unified Communications Manager. Default - This field stays 0.
Related: Origin Media Cap g723 Bit Rate
Source: www.cisco.com page=233
destMediaCap_maxFramesPerPacketIdentifies the number of milliseconds of data per packet that the terminating party of the call sends. This field normally gets set to 10, 20, or 30 for G.729 or G.711 codecs but can store any nonzero value. This field can specify zero if the media is never established. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Media Cap max Frames Per Packet
Source: www.cisco.com page=233
destMediaCap_payloadCapabilityIdentifies the codec type that the terminating party uses to transmit media. Unified Communications Manager currently uses the following payload capability values: 0, 1-16, 18-20, 25, 32, 33, 81-86. See topics related to codec types for a listing of the valid values. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Media Cap payload Capability
Source: www.cisco.com page=232
destMediaTransportAddress_IPIdentifies the v4 IP address of the device that terminates the media for the call. For Cisco Unified IP Phones, this field designates the v4 address of the phone. For PSTN calls, this field designates the v4address of the H.323 gateway. For intercluster calls, this field shows the v4address of the remote phone. Default - 0. If the destination cannot be reached or the IP address of the destination is not v4, this field stays 0.
Related: Origin Media Transport Address IP
Source: www.cisco.com page=232
destMediaTransportAddress_PortIdentifies the IP port number that is associated with the DestMediaTransportAddress IP field. _ Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Media Transport Address Port
Source: www.cisco.com page=232
destMobileCallDurationSpecifies the call duration in the mobile network for the destination device if the destination device is a mobile device. If the destination device is not a mobile device, this field remains empty. Default - 0
Related: Origin Mobile Call Duration
Source: www.cisco.com page=247
destMobileDeviceNameSpecifies the name of the destination mobile device. If the mobile device uses a remote destination profile the device name is the mobile number and remote destination profile name. For example, mobileNumber: RDP-name. If the mobile device uses a mobile identity, the device name is the mobile identity name. If the destination device is not a mobile device, this field remains empty. Default - Empty string
Related: Origin Mobile Device Name
Source: www.cisco.com page=246
destNodeIdIdentifies the location, or node within a cluster, to which the terminating party of the call is registered at the time that the call is made. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Node Id
Source: www.cisco.com page=230
destPrecedenceLevelRepresents the destination legs precedence level. For MLPP, each call leg has a precedence level. • Precedence 0 = FLASH OVERRIDE • Precedence 1 = FLASH • Precedence 2 = IMMEDIATE • Precedence 3 = PRIORITY • Precedence 4 = ROUTINE Default - 4
Related: Origin Precedence Level
Source: www.cisco.com page=232
destRSVPAudioStatDesignates the status of the RSVP audio reservation from terminator to originator. 0 – No reservation. 1 – RSVP Reservation Failure condition at the call setup or feature invocation. 2 – RSVP Reservation Success condition at call setup or feature invocation. 3 – RSVP Reservation No Response (RSVP Agent) condition at call setup or feature invocation. 4 – RSVP Mid Call Failure Preempted condition (preempted after call setup). 5 – RSVP Mid Call Failure Lost Bandwidth condition (includes all mid call failures except MLPP preemption). Default – 0
Related: Origin RSVPAudio Stat
Source: www.cisco.com page=234
destRSVPVideoStatDesignates the status of the RSVP video reservation from terminator to originator. 0 – No reservation. 1 – RSVP Reservation Failure condition at call setup or feature invocation. 2 – RSVP Reservation Success condition at call setup or feature invocation. 3 – RSVP Reservation No Response (RSVP Agent) condition at call setup or feature invocation. 4 – RSVP Mid Call Failure Preempted condition (preempted after call setup). 5 – RSVP Mid Call Failure Lost Bandwidth condition (includes all mid call failures except MLPP preemption). Default – 0
Related: Origin RSVPVideo Stat
Source: www.cisco.com page=234
destSpanFor calls that are received at a gateway, this field indicates the B channel number of the T1, PRI, or BRI trunk where the call is received, or a zero value for FXS or FXO trunks. For H.323 gateways, the span number remains unknown, and this field contains the call leg ID of the destination. For calls not terminating at a gateway, the value specifies zero. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Span
Source: www.cisco.com page=231
destVideoCap_BandwidthIdentifies the bandwidth, and is measured in units of kbps. Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Video Cap Bandwidth
Source: www.cisco.com page=233
destVideoCap_Bandwidth_Channel2Identifies the bandwidth measured in units of kbps for the second video channel. Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Origin Video Cap Bandwidth Channel2
Source: www.cisco.com page=241
destVideoCap_CodecIdentifies the codec type that the terminating party uses to transmit video (H.261, H.263, or H.264). Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Video Cap Codec
Source: www.cisco.com page=233
destVideoCap_Codec_Channel2Identifies the codec type that the terminating party uses to transmit video (H.261, H.263, or H.264) for the second video channel. Default - 0. If the destination cannot be reached, this field stays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Origin Video Cap Codec Channel2
Source: www.cisco.com page=240
destVideoCap_ResolutionIndicates the transmitting resolution. In the case of H.264 codec or SIP device, this field refers to the max transmitting resolution the device can transmit for this call. Default - 0. If media is not established, this field stays 0.
Related: Origin Video Cap Resolution
Source: www.cisco.com page=233
destVideoCap_Resolution_Channel2Indicates the transmitting resolution for the second video channel. In the case of H.264 codec or SIP device, this field refers to the maximum transmitting resolution the device can transmit for this call. Default - 0. If media is not established, this field stays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Origin Video Cap Resolution Channel2
Source: www.cisco.com page=241
destVideoChannel_Role_Channel2Identifies the H.239 video channel role of the device that receives the call. Default - 0. If media does not get established, this field displays 0. Also, if H.239 is not supported, this field displays 0.
Related: Origin Video Channel Role Channel2
Source: www.cisco.com page=241
destVideoTransportAddress_IPIdentifies the v4 IP address of the device that receives the call. Default - 0. If the destination cannot be reached or the IP address of the destination is not v4, this field stays 0.
Related: Origin Video Transport Address IP
Source: www.cisco.com page=233
destVideoTransportAddress_IP_Channel2Identifies the v4 IP address of the device that receives the call. Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Origin Video Transport Address IP Channel2
Source: www.cisco.com page=241
destVideoTransportAddress_PortIdentifies the video RTP port that is associated with the destVideoTransportAddress IP field. _ Default - 0. If the destination cannot be reached, this field stays 0.
Related: Origin Video Transport Address Port
Source: www.cisco.com page=233
destVideoTransportAddress_Port_Channel2Identifies the video RTP port associated with the destH239VideoTransportAddress IP field. _ Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Origin Video Transport Address Port Channel2
Source: www.cisco.com page=241
durationIdentifies the difference between the Connect Time and Disconnect Time. This field specifies the time that the call remains connected, in seconds. This field remains zero if the call never connects or if it connects for less than 1 second. Default - 0
Source: www.cisco.com page=236
finalCalledPartyNumberSpecifies the phone number to which the call finally gets presented, until it is answered or rings out. If no forwarding occurs, this number shows the same number as the originalCalledPartyNumber. If the call finally gets presented to a directory URI, the field remains empty. If a blended address is used, this field specifies the directory number portion of the blended address. For calls to a conference bridge, this field contains the actual identifier of the conference bridge, which is an alphanumeric string (for example, b0019901001). This field represents an alphanumeric string that can be either digits or a SIP URL. Default - Empty string “”. If destination cannot be reached, this field stays empty.
Source: www.cisco.com page=231
finalCalledPartyNumberPartitionIdentifies unique partition name that is associated with the FinalCalledPartyNumber field because Unified Communications Manager supports multiple Cisco Unified IP Phones with the same extension number in different partitions. For calls that egress through an H.323 gateway, this field uniquely specifies the partition name that is associated with the route pattern that points to the gateway. Default - Empty string “”. If the final called party does not have a partition, this field remains empty.
Source: www.cisco.com page=235
finalCalledPartyNumber_uriSpecifies an alphanumeric string of up to 254 characters that indicate the directory URI address to which the call finally gets presented, if the final address is a directory URI. If no forwarding occurs, this field shows the same directory URI as the originalCalledPartyNumber uri field. _ If a blended address is used for the called number, this field specifies the directory URI portion of the blended address. For calls to a conference bridge, this field contains the actual identifier of the conference bridge, which is an alphanumeric string (for example, b0019901001). Default - Empty string “”. If destination cannot be reached, or if a directory number is used for called addressing, this field stays empty.
Source: www.cisco.com page=245
finalCalledPartyPatternSpecifies numeric string (with special characters) string up to 50 characters. The pattern of the final called party to which the call is presented until that call is answered or ringing has ended. If no forwarding occurred, this pattern is the same as originalCalledPartyPattern. This field indicates the pattern before any configured translation rules are applied. This value is the same as the finalCalledPartyNumber if the number is a direct match without any translation Default—empty string “”.
Source: www.cisco.com page=247
finalCalledPartyUnicodeLoginUserIDSpecifies the login user ID. The format of this field specifies UTF 8. _ Default - Empty string “”. If the user ID does not exist, this field stays empty.
Source: www.cisco.com page=231
finalMobileCalledPartyNumberSpecifies the mobile called party if the final called device is a mobile device. If the final called device is not a mobile device, this field remains empty. Default - Empty string
Source: www.cisco.com page=246
globalCallID_callIdDesignates a unique call identity value that is assigned to each call. The system allocates this identifier independently on each call server. Values get chosen sequentially when a call begins. A value gets assigned for each call, successful or unsuccessful. When Unified Communications Manager restarts, it checks the file for the current globalCallID callId _ number and assigns the next 1000th number to the next GlobalCallID callId. _ The Global Call ID consists of two fields: globalCallID callId _ globalCallID callManagerId. _ All records that are associated with a standard call have the same Global Call ID in them. Note For Unified Communications Manager Release 5.x and later releases, the value in the GlobalCallId CDR field survives over Unified Communications Manager restarts. In Release 4.x and earlier releases, although the GlobalCallId field is time-based, the field gets reused under conditions of heavy traffic. Because of this behavior, problems can occur with customer billing applications and the ability of CAR to correlate CMRs with CDRs and to correlate conference call CDRs. For Release 5.x and later releases, GlobalCallId redesign ensures that the field retains a unique value, at least for a certain number of days. Now, the last used globalCallId callId value gets written to disk periodically (for every x _ number of calls). The value gets retrieved after a Unified Communications Manager restart, and the new globalCallId callId value _ begins with this number plus x. Default - Ensure that this field is populated.
Source: www.cisco.com page=226
globalCallID_callManagerIdDesignates a unique Unified Communications Manager identity. The Global Call ID comprises two fields: globalCallID callId _ globalCallID callManagerId. _ All records that are associated with a standard call have the same Global Call ID in them. Default - Ensure that this field is populated.
Source: www.cisco.com page=225
globalCallId_ClusterIDSpecifies a unique ID that identifies a cluster of Unified Communications Managers. The field is generated at installation and is not used by Unified Communications Manager. The fields globalCallId ClusterId + _ globalCallId CMId + globalCallId CallId make up this unique key. _ _ Default - This field should always be populated.
Source: www.cisco.com page=237
huntPilotDNIndicates the hunt pilot DN through which the call is routed. Default - Empty string.
Source: www.cisco.com page=242
huntPilotPartitionIndicates the partition for the hunt pilot DN. Default - Empty string.
Source: www.cisco.com page=242
huntPilotPatternSpecifies numeric string (with special characters) string up to 50 characters. The huntPilot pattern as configured in the database. This field is populated only when the HuntPilot member answers the call which is placed either directly or due to redirection to the huntPilot. Default - empty string "". If no huntPilot member answers, this field is empty.
Source: www.cisco.com page=247
incomingICIDSpecifies alphanumeric string up to 50 characters. This field is populated with the IMS Identifier(ICID) from the P-Charging Vector at the incoming call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Outgoing ICID
Source: www.cisco.com page=244
incomingOrigIOISpecifies alphanumeric string up to 50 characters. This field is populated with the originating Interoperator Identifier(IOI) from the P-Charging Vector at the incoming call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Outgoing Orig IOI
Source: www.cisco.com page=244
incomingProtocolCallRefIdentifies the globally unique call reference identification for the protocol. The value is received from the upstream voice product. The value is alpha–numeric and truncated to 32 characters.
Related: Outgoing Protocol Call Ref
Source: www.cisco.com page=241
incomingProtocolIDIdentifies the protocol (SIP, H.323, CTI/JTAPI, or Q.931) used between Cisco Unified CM and the upstream voice product in the call path.
Related: Outgoing Protocol ID
Source: www.cisco.com page=241
incomingTermIOISpecifies alphanumeric string up to 50 characters. This field is populated with the terminating Interoperator Identifier(IOI) from the P-Charging Vector at the incoming call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Outgoing Term IOI
Source: www.cisco.com page=244
joinOnBehalfOfSpecifies code that identifies the reason for a join. For example, if the join takes place on behalf of a transfer, the OnBehalfOf code specifies “10.” See topics related to CDR field descriptions for a list of the codes. Default - 0
Source: www.cisco.com page=237
lastRedirectDnSpecifies a numeric string of up to 25 characters. The numeric string can contain digits or a SIP URL. For forwarded calls, this field specifies the phone number of the next to last hop before the call reaches its final destination. If only one hop occurs, this number matches the OriginalCalledPartyNumber. If a blended address is used for call addressing, this field contains only the directory number portion of the blended address. For calls that are not forwarded, this field matches the OriginalCalledPartyNumber and the FinalCalledPartyNumber. For calls to a conference bridge, this field contains the actual identifier of the conference bridge, which is an alphanumeric string (for example, b0019901001). Default - Empty string “”. If the call is never redirected, or if the next to last hop address is a directory URI, this field remains empty.
Source: www.cisco.com page=235
lastRedirectDnPartitionIdentifies unique partition name that is associated with the LastRedirectDn field because Unified Communications Manager supports multiple Cisco Unified IP Phones with the same extension number in different partitions. For calls that egress through an H.323 gateway, this field specifies the partition name that is associated with the route pattern that points to the gateway. Default - Empty string “”. If the last redirecting Party does not have a partition or the call was never redirected, this field stays empty.
Source: www.cisco.com page=236
lastRedirectDn_uriSpecifies an alphanumeric string of up to 254 characters. For forwarded calls that use a directory URI for addressing, this field specifies the directory URI of the next to last hop before the call reaches its final destination. If only one hop occurs, this number matches the originalCalledPartyNumber uri. _ If a blended address is used, this field contains only the directory URI portion of the blended address. For calls that are not forwarded, this field matches the originalCalledPartyNumber uri and the finalCalledPartyNumber uri. _ _ For calls to a conference bridge, this field contains the actual identifier of the conference bridge, which is an alphanumeric string (for example, b0019901001). Default - Empty string “”. If the call is never redirected, or if the address is a directory number, this field remains empty.
Source: www.cisco.com page=246
lastRedirectRedirectOnBehalfOfSpecifies code that identifies the reason for redirection of the last redirected party. For example, if the last redirected party was redirected on behalf of a conference, the OnBehalfOf code specifies “4.” See topics related to CDR field descriptions for a list of the codes. This release added new OnBehalfOf codes. Default - 0
Source: www.cisco.com page=237
lastRedirectRedirectReasonIdentifies the last redirect reason for redirection. See topics related to redirect reason codes for a complete list of the codes. Default - 0
Source: www.cisco.com page=237
lastRedirectingPartyPatternSpecifies numeric string (with special characters) string up to 50 characters. The pattern of the last party which redirected the call to the current called party. If there is no redirection, the field has the same value as the originalCalledPartyPattern. Default—empty string “”.
Source: www.cisco.com page=247
lastRedirectingRoutingReasonDisplays why the call was intercepted for the last time. This field is used with the external call control feature. See topics related to routing reason values for external call control for a list of reasons. Default - Empty string.
Source: www.cisco.com page=242
mobileCallTypeSpecifies the mobility feature that is invoked for this mobile call. Default - 0
Source: www.cisco.com page=247
mobileCallingPartyNumberSpecifies the mobile cellular number if the original calling device is a mobile device. If the original calling device is not a mobile device, this field remains empty. Default - Empty string
Source: www.cisco.com page=246
origCallTerminationOnBehalfOfSpecifies code that identifies why the originator was terminated. For example, if the originator of the call hangs up the phone, the OnBehalfOf code shows “12” for Device. If the call terminates because of a transfer, the OnBehalfOf code shows “10” for Transfer. See topics related to CDR field descriptions for a list of the codes. This release added new OnBehalfOf codes. Default - 0
origCallTerminationOnBehalfOf: examples and troubleshooting
Related: Destination Call Termination On Behalf Of
Source: www.cisco.com page=236
origCalledPartyRedirectOnBehalfOfSpecifies code that identifies the reason for redirection of the original called party. For example, if the original called party was redirected because of a conference, the OnBehalfOf code specifies “4.” See topics related to CDR field descriptions for a list of the codes. This release added new OnBehalfOf codes. Default - 0
Source: www.cisco.com page=236
origCalledPartyRedirectReasonIdentifies the reason for a redirect of the original called party. See topics related to redirect reason codes for a complete list of the codes. Default - 0
Source: www.cisco.com page=237
origCause_locationSpecifies the Location field that is indicated in the ISDN release message for clearing causes that are received over ISDN signaling links. See topics that are related to call termination cause codes for a list of the valid values per Q.850. For clearing causes that are created internally by the Unified Communications Manager, this value specifies zero. Default - 0
Related: Destination Cause location
Source: www.cisco.com page=227
origCause_valueReflects the reason for clearance for the calls that are cleared by the originating party. Unified Communications Managercurrently uses the Q.850 codes and some Unified Communications Managerdefined codes. See topics that are related to call termination cause codes for a listing. For calls that are cleared by the terminating party, this field specifies zero. In addition to the standard values that are described in Q.850, when a call is split by a feature (transfer or conference), the CDR terminates, and this field gets set to 393216. This represents a proprietary value for this field. Default - 0
origCause_value: examples and troubleshooting
Related: Destination Cause value
Source: www.cisco.com page=228
origConversationIdIdentifies the conference ID that is associated with the originating leg of the call. In most cases, this field equals 0. For conference chaining scenarios, the origConversationID and destConversationID fields identify which conferences are chained together. Default - 0
Related: Destination Conversation Id
Source: www.cisco.com page=238
origDeviceNameSpecifies the text string that identifies the name of the originating device. Default - Ensure that this field is populated.
Related: Destination Device Name
Source: www.cisco.com page=236
origDeviceSessionIDIndicates the call Session ID of the originating device. When the session terminates, the system generates a CDR record and the field is populated with the originating device Session ID for the particular call. Note If the CDR service parameter 'CDR Log Calls with Zero Duration Flag' is set to 'True', this field is populated even though the call is not answered. The maximum length of this field is restricted to 127 characters. For example, origDeviceSessionID = ab30317fla784dc48fl824d0d3715d86 Default—empty string “”.
Introduced in CUCM 12.5(1)SU1; not first introduced in 15.
Related: Destination Device Session ID
Source: www.cisco.com page=248
origDeviceTypeIndicates whether the device that initiated the call was a Spark client that is anchored to Cisco Unified Communications Manager over the Spark Remote Device: • If yes, this field indicates "CiscoSparkRemoteDevice" • If no, this field is empty.
Related: Destination Device Type
Source: www.cisco.com page=248
origDTMFMethodDisplays the DTMF method that the originator uses. 0 - No DTMF - Use ANY matched DTMF. 1 - OOB - Use OOB if endpoints behind SIPTrunk support it. 2 - 2833 - Use RFC2833 if endpoints behind SIPTrunk support it. 3 - OOB and 2833 - Use both KPML and RFC2833 if endpoints behind SIPTrunk can support both. 4 - Unknown Default - 0 (No preference)
Related: Destination DTMFMethod
Source: www.cisco.com page=238
origIpAddrIdentifies the v4 IP address of the device that originates the call signaling. For Cisco Unified IP Phones, this field specifies the v4 address of the phone. For PSTN calls, this field specifies the v4address of the H.323 gateway. For intercluster calls, this field specifies the v4address of the remote Unified Communications Manager. Default - 0. If the v4 address does not exist for the originating device, this field equals 0. This field gets populated based on these rules.
Related: Destination Ip Addr
Source: www.cisco.com page=227
origIpv4v6AddrComprises an alphanumeric string of up to 64 characters. This field identifies the IP address of the device that originates the call signalling. The field can be either IPv4 or IPv6 format depending on the type of IP address that gets used for the call. For Cisco Unified IP Phones, this field is the address of the Cisco Unified IP Phone. For PSTN calls, this field is the address of the gateway. For intercluster calls, this field is the address of the remote Unified Communications Manager. The IP addressis either in dotted decimal format or in colon separated hexadecimal format. Default - TheIP address of the originating device as reported by the device or used for the call after media negotiation.
Related: Destination Ipv4v6 Addr
Source: www.cisco.com page=239
origLegCallIdentifierIdentifies the originating leg of a call. Be aware that this value is unique within a cluster. If the leg of a call persists across several subcalls and CDRs (as during a call transfer), this value remains constant. Default - Ensure that this field is populated.
Source: www.cisco.com page=226
origMediaCap_BandwidthDisplays the media bandwidth that is used at the origination of the call. Default - 0
Related: Destination Media Cap Bandwidth
Source: www.cisco.com page=238
origMediaCap_g723BitRateThis field is not used in the current release of Unified Communications Manager. Default - This field will remain 0.
Related: Destination Media Cap g723 Bit Rate
Source: www.cisco.com page=229
origMediaCap_maxFramesPerPacketIdentifies the number of milliseconds of data per packet that the originating party sends. This field normally gets set to 10, 20, or 30 for G.729 or G.711 codecs, but the field can store any nonzero value. Default - 0. If media is not established, this field stays 0.
Related: Destination Media Cap max Frames Per Packet
Source: www.cisco.com page=229
origMediaCap_payloadCapabilityIdentifies the codec type that the originator uses to transmit media. Unified Communications Manager currently uses the following payload capability values: 0, 1-16, 18-20, 25, 32, 33, 81-86. See topics related to codec types for a listing of the valid values. Default - 0. If media is not established, this field stays 0.
Related: Destination Media Cap payload Capability
Source: www.cisco.com page=228
origMediaTransportAddress_IPIdentifies the v4 IP address of the device that originates the media for the call. For Cisco Unified IP Phones, this field specifies the v4 address of the phone. For PSTN calls, this field specifies the v4address of the H.323 gateway. For intercluster calls, this field specifies the v4address of the remote phone. Default - 0. If media is not established or the address is not v4, this field equals 0.
Related: Destination Media Transport Address IP
Source: www.cisco.com page=228
origMediaTransportAddress_PortIdentifies the IP port number that is associated with the OrigMediaTransportAddress IP field. _ Default - 0. If media is not established, this field stays 0.
Related: Destination Media Transport Address Port
Source: www.cisco.com page=228
origMobileCallDurationSpecifies the call duration in the mobile network of the originating device if the calling party is a mobile device. If the calling party is not a mobile device, this field remains empty. Default - 0
Related: Destination Mobile Call Duration
Source: www.cisco.com page=247
origMobileDeviceNameSpecifies the device name of the calling party if the call is placed from a mobile device. If the mobile call uses a remote destination profile, the device name is the mobile number and remote destination profile name. For example, mobileNumber: RDP-name. If the mobile device uses a mobile identity, the device name is the mobile identity name. If the original device is not a mobile device, this field remains empty. Default - Empty string
Related: Destination Mobile Device Name
Source: www.cisco.com page=246
origNodeIdIdentifies the server, or node within a cluster, to which the originator of the call is registered at the time that the call is made. Default - Ensure that this field is populated.
Related: Destination Node Id
Source: www.cisco.com page=226
origPrecedenceLevelRepresents the precedence level of the original leg. For MLPP, each call leg includes a precedence level. • Precedence 0 = FLASH OVERRIDE/ EXECUTIVE OVERRIDE • Precedence 1 = FLASH • Precedence 2 = IMMEDIATE • Precedence 3 = PRIORITY • Precedence 4 = ROUTINE Default - 4
Related: Destination Precedence Level
Source: www.cisco.com page=228
origRoutingReasonDisplays the reason why the call was intercepted for the first time. This field is used with the external call control feature, See topics related to routing reason values for external call control for a list of reasons. Default value is 0.
Source: www.cisco.com page=242
origRSVPAudioStatProvides the status of the RSVP audio reservation from originator to terminator. 0 – No reservation. 1 – RSVP Reservation Failure condition at call setup or feature invocation. 2 – RSVP Reservation Success condition at the call setup or feature invocation. 3 – RSVP Reservation No Response (RSVP Agent) condition at the call setup or feature invocation. 4 – RSVP Mid Call Failure Preempted condition (preempted after the call setup). 5 – RSVP Mid Call Failure Lost Bandwidth condition (includes all mid-call failures except MLPP preemption). Default – 0
Related: Destination RSVPAudio Stat
Source: www.cisco.com page=230
origRSVPVideoStatProvides the status of the RSVP video reservation from originator to terminator. 0 – No reservation. 1 – RSVP Reservation Failure condition at call setup or feature invocation. 2 – RSVP Reservation Success condition at call setup or feature invocation. 3 – RSVP Reservation No Response (RSVP Agent) condition at call setup or feature invocation. 4 – RSVP MID Call Failure Preempted condition (preempted after call setup). 5 – RSVP MID Call Failure Lost Bandwidth condition (includes all mid-call failures except MLPP preemption). Default – 0
Related: Destination RSVPVideo Stat
Source: www.cisco.com page=230
origSpanFor calls that originate at a gateway, this field indicates the B-channel number of the T1, PRI, or BRI trunk where the call originates, or a zero value for FXS or FXO trunks. For H.323 gateways, the span number remains unknown, and this field contains the call leg ID of the originator. For calls that did not originate at a gateway, the value specifies zero. Default - This field gets populated based on these rules.
Related: Destination Span
Source: www.cisco.com page=226
origVideoCap_BandwidthIdentifies the bandwidth that is measured in units of kbps. Default - 0. If media is not established, this field stays 0.
Related: Destination Video Cap Bandwidth
Source: www.cisco.com page=229
origVideoCap_Bandwidth_Channel2Identifies the bandwidth measured in units of kbps for the second video channel. Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Destination Video Cap Bandwidth Channel2
Source: www.cisco.com page=240
origVideoCap_CodecIdentifies the codec type that the originator uses to transmit video (H.261, H.263, or H.264.) Default - 0. If media is not established, this field stays 0.
Related: Destination Video Cap Codec
Source: www.cisco.com page=229
origVideoCap_Codec_Channel2Identifies the codec type that the originator uses to transmit video (H.261, H.263, or H.264) for the second video channel. Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Destination Video Cap Codec Channel2
Source: www.cisco.com page=240
origVideoCap_ResolutionIndicates the transmitting resolution. In the case of H.264 codec or SIP device, this field refers to the max transmitting resolution the device can transmit for this call. Default - 0. If media is not established, this field stays 0.
Related: Destination Video Cap Resolution
Source: www.cisco.com page=229
origVideoCap_Resolution_Channel2Indicates the transmitting resolution for the second video channel. In the case of H.264 codec or SIP device, this field refers to the maximum transmitting resolution the device can transmit for this call. Default - 0. If media is not established, this field stays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Destination Video Cap Resolution Channel2
Source: www.cisco.com page=240
origVideoChannel_Role_Channel2Identifies the H.239 video channel role of the device that originates. Default - 0. If media does not get established, this field displays 0. Also, if H.239 is not supported, this field displays 0.
Related: Destination Video Channel Role Channel2
Source: www.cisco.com page=240
origVideoTransportAddress_IPIdentifies the v4 IP address of the device that originates the call. Default - 0. If media is not established or the address is not v4, this field stays 0.
Related: Destination Video Transport Address IP
Source: www.cisco.com page=229
origVideoTransportAddress_IP_Channel2Identifies the v4 IP address of the device that originates the call for the second video channel. Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Destination Video Transport Address IP Channel2
Source: www.cisco.com page=240
origVideoTransportAddress_PortIdentifies the video RTP port that is associated with the origVideoTransportAddress IP field. _ Default - 0. If media is not established, this field stays 0.
Related: Destination Video Transport Address Port
Source: www.cisco.com page=229
origVideoTransportAddress_Port_Channel2Identifies the video RTP port associated with the origH239VideoTransportAddress IP field for the second video channel. _ Default - 0. If media does not get established, this field displays 0. Also, if H.239 and BFCP are not supported for this call, this field displays 0.
Related: Destination Video Transport Address Port Channel2
Source: www.cisco.com page=240
originalCalledPartyNumberSpecifies the number to which the original call was presented, prior to any call forwarding. If translation rules are configured, this number reflects the called number after the translations have been applied. If a blended address is used for the called party, this field specifies the directory number portion of the blended address. This field represents a numeric string of up to 48 characters that can be either digits or a SIP URL. Default - Empty string “”. If destination cannot be reached, or if the called party number is a directory URI, this field stays empty.
Source: www.cisco.com page=231
originalCalledPartyNumberPartitionIdentifies unique partition name that is associated with the OriginalCalledPartyNumber field because Unified Communications Manager supports multiple Cisco Unified IP Phones with the same extension number in different partitions. For calls that egress through an H.323 gateway, this field uniquely specifies the partition name that is associated with the route pattern that points to the gateway. Default - Empty string “”. If the original called party does not have a partition, this field remains empty.
Source: www.cisco.com page=235
originalCalledPartyNumber_uriSpecifies a string of up to 254 alphanumeric characters that specifies the directory URI to which the original call was addressed, prior to any call forwarding, provided the call was addressed to a directory URI. If a blended address is used for the called party, this field specifies the directory URI portion of the blended address. Default - Empty string “”. If destination cannot be reached, or if the called party is a directory number, this field stays empty.
Source: www.cisco.com page=245
originalCalledPartyPatternSpecifies numeric string (with special characters) up to 50 characters. This is the pattern to which the original call was placed before any configured translation is applied. Calls to Translation Pattern will always populate the pattern after applying the configured transformation on the translation pattern. Default—empty string “”.
Source: www.cisco.com page=247
outgoingICIDSpecifies alphanumeric string up to 50 characters. This field is populated with the IMS Identifier(ICID) from the P-Charging Vector at the outgoing call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Incoming ICID
Source: www.cisco.com page=244
outgoingOrigIOISpecifies alphanumeric string up to 50 characters. This field is populated with the originating Interoperator Identifier(IOI) from the P-Charging Vector at the outgoing call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Incoming Orig IOI
Source: www.cisco.com page=244
outgoingProtocolCallRefIdentifies the globally unique call reference identification for the protocol. The value is passed to the next downstream voiced product. The value is alpha–numeric and truncated to 32 characters.
Related: Incoming Protocol Call Ref
Source: www.cisco.com page=242
outgoingProtocolIDIdentifies the protocol (SIP, H.323, CTI/JTAPI, or Q.931) used between Cisco Unified CM and the downstream voice product in the call path.
Related: Incoming Protocol ID
Source: www.cisco.com page=242
outgoingTermIOISpecifies alphanumeric string up to 50 characters. This field is populated with the terminating Interoperator Identifier(IOI) from the P-Charging Vector at the outgoing call leg of the call. This field will be empty when the call leg has no IMS or SIP trunk with P-Charging-Vector enabled. Default = Empty String " "
Related: Incoming Term IOI
Source: www.cisco.com page=244
outpulsedCalledPartyNumberComprises an alphanumeric string of up to 50 characters. The called party number gets outpulsed from the device. This field gets populated only when normalization or localization takes place at the device. Default - Empty string “”or null.
Source: www.cisco.com page=239
outpulsedCallingPartyNumberComprises an alphanumeric string of up to 50 characters. The calling party number gets outpulsed from the device. This field gets populated only when normalization or localization takes place at the device. Default - Empty string “” or null.
Source: www.cisco.com page=239
outpulsedLastRedirectingNumberSpecifies alphanumeric string up to 50 characters. The Last Redirecting number outpulsed from the device. Refer to section on Redirecting Number Transformation for details. Default = Empty String " "
Source: www.cisco.com page=245
outpulsedOriginalCalledPartyNumberSpecifies alphanumeric string up to 50 characters. The Original called party number outpulsed from the device. Refer to section on Redirecting Number Transformation for details. Default = Empty String " "
Source: www.cisco.com page=245
pkidIdentifies a text string that the database uses internally to uniquely identify each row. This text string provides no meaning to the call itself. Default - A unique ID should always populate this field.
Source: www.cisco.com page=235
totalWaitTimeInQueueSpecifies how long a caller has been put into a queue. The value is specified in second. The value is 0 if the call is never put into any queue.
Source: www.cisco.com page=245
wasCallQueuedSpecifies whether the call has been put into a queue or not. A value of 0 means that the call is not put into any queue; 1 means the call has been put into a queue.
Source: www.cisco.com page=245
Load your CUCM CDR and matching CMR files to decode values, inspect related call legs and compare causes in context. Files are processed locally in your browser.