Technical information

29
Cisco Unified CallManager 4.2(3) Call Detail Record Definition
OL-10659-01
Working with CDRs
joinOnBehalfOf Integer Specifies code that identifies the reason
for a join.
For example, if the join took place on
behalf of a transfer, the OnBehalfOf code
specifies “10.”
See the “OnBehalfof Codes” section for a
complete list of the codes.
Default - 0.
globalCallId_ClusterId Text String Specifies a unique ID that identifies a
cluster of Cisco Unified CallManagers.
Cisco Unified CallManager does not use
this field that generates at installation. The
following fields make up this unique key:
GlobalCallId_ClusterId +
GlobalCallId_CMId +
GlobalCallId_CallId
Default - This field should always be
populated.
Comment TextString This field allows features to add text to the
CDR records. This text can describe
details about the call.
For example, the following field flags
malicious calls:
Tag—CallFlag
Va l ue —M AL IC I OU S
Default—This empty string “” or null.
The following field flags the party that
added the participant known as the
requestor party:
Tag—ConfRequestorDN
callingPartyLoginUserID Text String Identifies the calling party user login ID.
Default: This empty string, “”, or null.
finalCalledPartyLoginUserID Text String Identifies the final called party user login
ID.
Default: This empty string, “”, or null.
authCodeDescription Text String Description of the authorization code. For
security purposes, the authorization code
does not get written to the CDR; the
authorization description and level get
written instead.
Default: This empty string, “”, or null.
Field Name
Range of
Values Description