/mcpDiverted Call CDR Original Connected Call CDR Field Names 50 0 origCalledPartyRedirectReason 50 0 lastRedirectRedirectReason 14 origCalledPartyRedirectOnBehalfOf 14 lastRedirectRedirectOnBehalfOf 14 14 origTerminationOnBehalfOf 12 14 destTerminationOnBehalfOf 14 joinOnBehalfOf IMS Application Server 1. IMS A with calls IMS B through Unified Communications Manager The incoming invite to Unified Communications Manager contains: Icid: 5802170000010000000000A85552590A (say, PCV1) and orig_ioi: rcdn-85.swyan.open-ims.test (say, IOI_1). The INVITE from the Unified Communications Manager to IMS B has the same icid as 5802170000010000000000A85552590A (PCV1), orig_ioi as rcdn-85.swyan.open-ims.test (IOI_1). 2. When B answers, 200 OK to Unified Communications Manager has icid as 5802170000010000000000A85552590A (PCV1), orig_ioi as rcdn-85.swyan.open-ims.test (IOI_1), and term_ioi, rcdn-86.swyan.open-ims.test (IOI_2). There could be extra fields with this 200 OK. 3. The 200 OK from Unified Communications Manager to IMS A has icid 5802170000010000000000A85552590A (PCV1), orig_ioi as rcdn-85.swyan.open-ims.test (IOI_1), and term_ioi as rcdn-86.swyan.open-ims.test (IOI_2). The extra fields in the 200 OK will be passed to IMS A. Side B Side A CDR term_ioi orig_ioi icid term_ioi orig_ioi icid parties IOI_2 IOI_1 PCV1 IOI_2 IOI_1 PCV1 A-B CDR Fields Names 3 globalCallID_callId 300 origLegCallIdentifier 301 destLegIdentifier CUCM_ISC_TRUNK1 origDeviceName Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 312 CDR Records IMS Application Server