McDewey

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

Page 371

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

• 1 record for the final two parties in the conference You can associate the setup calls with the correct call leg in the conference by examining the calling leg ID and called leg ID. The conference bridge device has special significance to the Unified Communications Manager, and calls to the conference bridge appear as calls to the conference bridge device. A special number in the form "b0019901001" shows the conference bridge port. All calls in or out of the conference bridge get shown going into the conference bridge, regardless of the actual direction. By examining the setup call CDR records, 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 identifies the conference controller. You need the device name in the case of shared lines. • If the call is involved in multiple conference calls, the comment field will contain multiple conference controller information. This could happen in case 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 will identify the conference controller. The call legs that are connected to the conference will have the following fields information: • 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 will have the following fields: • The origCallTerminationOnBehalfOf field gets set to (Conference = 4). • The destCallTerminationOnBehalfOf field gets set to (Conference = 4). Video Conference Call CDR Example 1. Call from 2001 to 2309; 2309 answers, and they talk for 60 seconds. 2. 2001 presses the conference softkey and dials 3071111. 3. 307111 answers and talks for 20 seconds; 2001 presses the conference softkey to complete the conference. 4. The three members of the conference talk for 360 seconds. 5. 3071111 hangs up; 2001 and 2309 stay in the conference. Because only two participants remain in the conference, the conference feature joins the two directly together, and they talk for another 55seconds. Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs 359 CDR Records Video Conference Calls