Mcu And Mcu Mse Blade Cdr Event Types; Scheduled_Conference_Started - Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT Reference Manual

MCU and MCU MSE blade CDR event types

Currently the MCU and MCU MSE blade CDRs support the event types listed in the table below. They
are listed in the order that they occur in the CDR.
Event type

scheduled_conference_started

ad-hoc_conference_started
participant_joined
participant_left
conference_finished
The tables in the sections below show the parameters for each event type in the order in which they
appear in the CDR. There is an explanation for each parameter.
scheduled_conference_started
There are two variations for this event. One for permanent conferences and one for conferences with
a scheduled end time. The differences are indicated in the table.
Section
<conference>
<conference details>
<owner>
Call Detail Record File Format Reference Guide
Description
A scheduled conference was started. Either a permanent conference or
one with a scheduled end time
An ad hoc conference was started through the auto attendant
A participant joined the conference
A participant disconnected or was forcibly disconnected
The conference finished
Name
unique_id
name
numeric_id
has_pin
billing_code
name
Description
Unique identifier for the conference in the
format nnnnnnnn. This is generated
automatically by the MCU
For scheduled conferences, this is the
conference name as allocated by the user.
For ad hoc conferences, it is a name
provided by the MCU
Numeric id given to the conference by the
creator or <none>. Used either for calling
into a conference via a gatekeeper or
calling in using the MCU as an H.323
gateway
Whether or not a PIN was used to enter the
conference. This will be one of:
yes
no
Note that PINs are optional for scheduled
conferences
For future expansion
Log in user name of the person who
MCUs
Page 6 of 26