McDewey

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

Page 267

↗ View in doc context
page
267
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::359

• If the call is abandoned, such as when a phone is taken off hook and placed back on hook, various fields do not contain data. In this case, the originalCalledPartyNumber, finalCalledPartyNumber, the partitions that are associated with them, the destIpAddr, and the dateTimeConnect fields all remain blank. All calls that are not connected have a duration of 0 second. When a call is abandoned, the cause code contains 0. • If the user dials a directory number and abandons the call before it connects, the FirstDest and FinalDest fields and their associated partitions contain the directory number and the partition to which the call would have been extended. The DestIp field remains blank, and the duration specifies 0 second. You must enable the CDR Log Calls With Zero Duration Flag service parameter to log calls with zero duration. This parameter enables or disables the logging of CDRs for calls which lasted less than 1 second. See Configure CDR Service Parameters, on page 24 for more information. Note Examples of Abandoned Calls 1. Extension 2001 goes off hook, then on hook. CDR Field Names 1 globalCallID_callId 100 origLegCallIdentifier 0 destLegIdentifier 2001 callingPartyNumber originalCalledPartyNumber finalCalledPartyNumber lastRedirectDn 16 origCause_Value 0 dest_CauseValue 0 duration 2. Extension 2001 calls 2309, but 2001 hangs up (abandons) the call before it is answered. CDR Field Names 2 globalCallID_callId 200 origLegCallIdentifier 201 destLegIdentifier 2001 callingPartyNumber Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 255 CDR Records Abandoned Calls

Image 1 from page 267

Page 267 diagram