Technical information

45
Cisco Unified CallManager 4.2(3) Call Detail Record Definition
OL-10659-01
Call Types
Conference Calls
Three major operational factors exist for Conference CDRs:
1. When the conference decreases to two parties, the two parties connect directly and release the
conference resource. This change generates an additional CDR for the call between the last two
parties in the conference call. In previous releases, the last two parties remained connected to the
conference bridge until the call ended.
For example, if four people are connected in a conference call (Amy, Dustin, Spencer, Ethan), when
Ethan hangs up three people remain in the conference call that is connected to the conference bridge
(Amy, Dustin, Spencer). When Spencer hangs up, there only two people remain in the conference
call (Amy and Dustin). The system joins Amy and Dustin directly and the conference resource gets
released. Directly joining Amy and Dustin creates an additional CDR between the last two parties
in the conference.
2. The conference controller information gets added to the comment field in the CDR. This information
identifies the conference controller. No need now exists to examine the consultation call to
determine who is the conference controller. The following example shows this information:
Comment field = “ConfControllerDn=1000;ConfControllerDeviceName=SEP0003E333FEBD”
• The conference controller DN + conference controller device name uniquely identifies the
conference controller. A need for the device name exists in the case of shared lines.
• If the call is involved in multiple conference calls, the comment field contains multiple conference
controller information. This may occur when the conference goes down to two parties, and one of
these parties starts another conference. If this is the case, the last conference controller information
in the comment field identifies the conference controller.
3. The party that added the participant, known as the requestor party, appears in the CDR comment
field. The tags for the requestor information are ConfRequestorDn and ConfRequestorDeviceName.
The party that requested to remove a participant, known as the drop requestor, appears in the CDR
comment field. The tags for the drop requestor information are DropConfRequestorDn and
DropConfRequestorDeviceName.
Calls that are part of a conference have multiple records that are logged for them. The number of CDR
records that are generated depends on the number of parties in the conference. One CDR record exists
for each party in the conference, one CDR record for the original placed call, and one CDR for each setup
call that is used to join other parties to the conference. Therefore, for a three-party ad hoc conference,
six CDR records exist:
Calling
Party
Calling
Partition
Original
Called
Party
Original
Called
Partition
Final
Called
Party
Final
Called
Partition
Last
Redirect
Party
Last
Redirect
Partition Duration
A 02920262227 2001 ACNTS 2309 MKTG 2001 ACNTS 120
B 02920262227 2001 ACNTS 6000 VMAIL 2309 MKTG 60
OrigCalledParty Redirected OnBehalfOf Last Redirect Redirect OnBehalfOf
55
55