McDewey

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

Page 336

↗ View in doc context
page
336
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::382

Mobility The following call detail record (CDR) fields apply specifically to Mobility calls. If the call does not invoke a mobility feature, these fields remain empty: • mobileCallingPartyNumber • finalMobileCalledPartyNumber • origMobileDeviceName • destMobileDeviceName • origMobileCallDuration • destMobileCallDuration • mobileCallType The system generates a standard CDR for every call that uses the Mobility features. When a call gets split, redirected, or joined by the Mobility feature, the corresponding OnBehalfOf code represents a new value that is designated to Mobility. If any of the following OnBehalfOf fields has the Mobility code of 24, the CDR has the Mobility call type: • origCallTerminationOnBehalfOf • destCallTerminationOnBehalfOf • origCalledPartyRedirectOnBehalfOf • lastRedirectRedirectOnBehalfOf • joinOnBehalfOf MobileCallType Values The following table displays the field values for the mobileCallType CDR field. Cisco Analysis and Reporting (CAR) uses the mobileCallType field to determine the CAR call type. If a single call invokes more than one mobility feature, the value of the mobileCallType field represents the integer values added together. For example, if a call uses the Mobile Connect feature and then invokes Hand-Out, the mobile call type will be 136 (8 + 128). mobileCallType Value Mobility Feature 0 Nonmobility call 1 Dial via Office Reverse Callback 2 Dial via Office Forward 4 Reroute remote destination call to enterprise network 8 Mobile Connect 10 Interactive Voice Response Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 324 CDR Records Mobility

Page 336 diagram