McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 181

↗ View in doc context
page
181
source
cucm/v15/reporting-billing-admin-guide/cucm-15-reporting-billing-admin-guide.md
chunk_id
cucm::v15::reporting-billing-admin-guide::cucm-15-reporting-billing-admin-guide::250

Description Field Hunt Pilot Directory number (DN) Called Party Directory Number where the call landed in the end. If the call is landed in Hunt Pilot, then it will show its member DN. Suppose the call forward is set from member DN to some other DN, it will show that DN where the call got forwarded. The number of the hunt member is displayed only when the Show Line Group Member DN in finalCalledPartyNumber CDR Field is set to true. If the value is set to false, the Hunt Pilot DN is displayed in this field. For details on setting this parameter see, Service Parameters Configuration in Cisco Unified CM Administration Guide. Final Called Party Number Device identifier of the device that answered the call. Dest. Device Name Indicates if the call was answered or not. Values could be Yes or No. Call Answered Indicates if the call was abandoned. Values could be Yes or No. Call Abandoned Indicates if the call was forwarded due to no reply. Values could be Yes or No. Call Forwarded Due to No Answer (FONA) Indicates if the call was forwarded since the answering end was busy. Values could be Yes or No. Call Forwarded Due to Busy (FOB) Indicates if the call failed to get through. Values could be Yes or No. Call Failed Identification number to trace the call. This is the globalcallid_callid value in the CDR database. Call Reference Figure 33: Hunt Pilot Details Report, on page 169 displays sample output of the Hunt Pilot Details report in the PDF format. Figure 33: Hunt Pilot Details Report Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 169 CDR Analysis and Reporting Hunt Pilot Detail Report Results

Image 1 from page 181

Page 181 diagram