/mcpValues Field Names +19725001212 callingPartyNumber 5001212 outpulsedCallingPartyNumber 60 duration 1. A call gets placed from an enterprise phone to a Dallas PSTN. The extension of the enterprise phone comprises 12345; the fully qualified number comprises 9725002345. Calling party transformation checks the external phone number mask feature. The callingPartyNumber field in the CDR contains +1 972 500 2345 (global format). The new field outpulsedCallingPartyNumber contains the localized number 9725002345. Values Field Names 2 globalCallID_callId 102 origLegCallIdentifier 103 destLegIdentifier +19725002345 callingPartyNumber 9725002345 outpulsedCallingPartyNumber 60 duration Calls with Busy or Bad Destinations The system logs all these calls as normal calls, and all relevant fields contain data. The Calling or Called Party Cause fields contain a cause code that indicates why the call does not connect, and the Called Party IP and Date/Time Connect fields remain blank. The system logs all unsuccessful calls, even if zero duration calls are not being logged (CdrLogCallsWithZeroDurationFlag set at True or False, a duration of zero, and a DateTimeConnect value of zero). Examples of Unsuccessful Calls CDRs 1. Call goes to PSTN number, but party already is engaged (cause 17 = user busy) CDR Field Names 3 globalCallID_callId 300 origLegCallIdentifier 301 destLegIdentifier 2001 callingPartyNumber 9728134987 originalCalledPartyNumber Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 279 CDR Records Calls with Busy or Bad Destinations