McDewey

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

Page 296

↗ View in doc context
page
296
source
cucm/v15/reporting-billing-admin-guide/reporting-billing-admin-guide.md
chunk_id
cucm::v15::reporting-billing-admin-guide::reporting-billing-admin-guide::273

of the actual direction; however, by examining the setup call CDRs, you can determine the original direction of each call. You can find the conference controller information in the comment field of the CDR. The format of this information follows: Comment field = “ConfControllerDn=1000;ConfControllerDeviceName=SEP0003” • The conference controller DN + conference controller device name uniquely identify the conference controller. The system needs the device name in the case of shared lines. • If the call is involved in multiple conference calls, the comment field contains multiple conference controller information. This situation can occur when the conference goes down to two parties, and one of these parties starts another conference. If this is the case, the last conference controller information in the comment field identifies the conference controller. The call legs that are connected to the conference include the following information fields: • The finalCalledPartyNumber field contains the conference bridge number “b0019901001.” • The origCalledPtyRedirectOnBehalfOf field gets set to Conference = 4. • The lastRedirectRedirectOnBehalfOf field gets set to Conference = 4. • The joinOnBehalfOf field gets set to (Conference = 4). • The comment field identifies the conference controller. • The destConversationID field remains the same for all members in the conference. You can use this field to identify members of a conference call. The original placed call and all setup calls that were used to join parties to the conference have the following characteristics: • The origCallTerminationOnBehalfOf field gets set to Conference = 4. • The destCallTerminationOnBehalfOf field gets set to Conference = 4. Conference Call CDR Example • Call goes from 2001 to 2309. • 2309 answers and talks for 60 seconds. • 2001 presses the conference softkey and dials 3071111. • 307111 answers and talks for 20 seconds; then, 2001 presses the conference softkey to complete the conference. • The three members of the conference talk for 360 seconds. 3071111 hangs up and leaves 2001 and 2309 in the conference. Because only two participants are left in the conference, the conference features joins these two directly together, and they talk for another 55 seconds. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 284 CDR Records Conference Calls