Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT - Manual de usuario descargar pdf (Pagina 6)

MCUs

Call Detail Records File Format Reference Guide Page 6 of 26

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 Description

scheduled_conference_started A scheduled conference was started. Either a permanent conference or

one with a scheduled end time

ad-hoc_conference_started An ad hoc conference was started through the auto attendant

participant_joined A participant joined the conference

participant_left A participant disconnected or was forcibly disconnected

conference_finished The 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 Name Description

<conference> unique_id Unique identifier for the conference in the

format nnnnnnnn. This is generated

automatically by the MCU

name 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

<conference details> numeric_id 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

has_pin Whether or not a PIN was used to enter the

conference. This will be one of:

yes

Note that PINs are optional for scheduled

conferences

billing_code For future expansion

<owner> name Log in user name of the person who

1 2 3 4 5 6 7 8 9 10 11 ... 25 26

Sin comentarios

Cisco TELEPRESENCE CALL DETAIL RECORDS FILE FORMAT - Manual de usuario Pagina 6