McDewey

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

Page 313

↗ View in doc context
page
313
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::372

• Hunt Pilot 2000 is associated with a hunt list. • Phone 1000 calls hunt pilot 2000; call is offered at 3001 and abandoned. When the Show Line Group Member DN in finalCalledPartyNumber CDR field service parameter is set to True, the following values from the table display in the CDR: CDR Field Names 1000 callingPartyNumber callingPartyNumberPartition 2000 originalCalledPartyNumber originalCalledPartyNumberPartition 2000 finalCalledPartyNumber finalCalledPartyNumberPartition Phone 1000 origDeviceName Phone 3001 destDeviceName huntPilotDN huntPilotPartition 7 calledPartyPatternUsage If the call is not answered by any of the hunt group members, the finalCalledPartyNumber field shows the hunt pilot DN. The number shows a line group member DN only when one of the line group member answers the call. Note Because the call does not get answered, the huntPilotDN is not available in the CDR. The PatternUsage (7 = PATTERN_HUNT_PILOT) field gets set to 7 to indicate that the call was made to a hunt pilot. When the service parameter is enabled, the finalCalledPartyNumber field denotes the member hunt DN and the originalCalledPartyNumber field denotes the huntPilot DN. When the Show Line Group Member DN in the finalCalledPartyNumber CDR field service parameter is set to False, the following values in the table display in the CDR: CDR Field Names 1000 callingPartyNumber callingPartyNumberPartition 2000 originalCalledPartyNumber originalCalledPartyNumberPartition Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 301 CDR Records Hunt List Support

Image 1 from page 313

Page 313 diagram