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

MCUs

Call Detail Records File Format Reference Guide Page 7 of 26

Section Name Description

created the conference

<end> scheduled_date

End date of the conference in the format dd

Month yyyy unless this is a permanent

conference in which case the end date is

not included

scheduled_time

Either the time in the format hh:mm:ss or

permanent.

scheduled_duration_in_minutes Scheduled length of the conference in

minutes. Not included for permanent

conferences

ad-hoc_conference_started

This event is seen when a conference is started from the MCU’s auto attendant with the Create new

conference option.

Section Name Description

<conference> unique_id Unique identifier for the conference in the

format nnnnnnnn. This is generated

automatically by the MCU

name Usually the same as the numeric_id

<conference details> numeric_id The conference ID entered by the creator of

the conference or <none>

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 ad hoc

conferences

billing_code For future expansion

<creator> participant_id A number corresponding to one of the

participants' "participant_id" values that can

be found in its "participant_joined" record (see

next event)

<end> scheduled_time Not relevant to an ad hoc conference and

therefore always <none>

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

Sin comentarios

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