Technical information

2
Cisco Unified CallManager 4.2(3) Call Detail Record Definition
OL-10659-01
New and Changed Information
New and Changed Information
This section describes any new features and or changes for CDRs that are pertinent to the specified
release of Cisco Unified CallManager.
Cisco Unified CallManager Release 4.2(3)
For this release, the origConversationID field was added to the CDR to support the Adhoc conference
enhancement. This field identifies the conference ID associated with the originating leg of the call. In
most cases, this field equals 0. Default equals 0. For conference chaining scenarios, the
origConversationID and destConversionID fields identify which conferences are chained together.
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.
Cisco Unified CallManager Release 4.2(1)
For this release, you can configure Cisco Unified CallManager to report the directory number (DN) of
the hunt group member who answered a direct call to the hunt pilot number in the final called party
number field in the CDR. Previously, Cisco Unified CallManager reported the hunt pilot DN in the final
called party number field in the CDR.
When you enable the service parameter and set Show Line Group Member DN in the
finalCalledPartyNumber CDR field parameter to True, the finalCalledPartyNumber field in the CDR will
record the DN of the member who answered the call. When you disable the service parameter and set
Show Line Group Member DN in finalCalledPartyNumber CDR field parameter to False, the
finalCalledPartyNumber field in the CDR will record the hunt pilot DN. By default, the system sets the
Show Line Group Member DN in finalCalledPartyNumber CDR field parameter to False. For example,
when a direct call to hunt pilot number of 8600 is routed and picked up by hunt group member with
extension 2037, the CDR displays the final called party number (finalCalledPartyNumber) as 2037 when
Show Line Group Member DN in finalCalledPartyNumber CDR field parameter is set to True. Whereas
the CDR displays the final called party number (finalCalledPartyNUmber) as 8600 when Show Line
Group Member DN in finalCalledPartyNumber CDR field parameter is set to False.
Cisco Unified CallManager Release 4.1(3)
For this release, the content of the CDR records changed for the new Auto Pickup feature, but no new
CDR fields or changed CDR fields were added. Enhancements to the existing Call Pickup and Group
Call Pickup features provide the Auto Pickup feature.
You can enable and disable Auto Pickup by using the new service parameter Auto Pickup Enabled. By
default, the system sets the Auto Pickup Enabled parameter to False. When the parameter is set to True,
Auto Pickup applies to all types of Call Pickup.