Huawei Vp9660&Vp9650&Vp9630 v200r001c30 CDR Reference 02

HUAWEI VP9660&VP9650&VP9630
V200R001C30
CDR Reference
Issue 02
Date 2014-07-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://enterprise.huawei.com
Issue 02 (2014-07-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
CDR Reference About This Document
About This Document
Purpose
Call detail records (CDRs) are important files that the system generates as proof of
communication services used by users. The handling mechanism for CDRs must address all
cases, including exceptions.
This document provides formats and types of CDRs produced by the VP9650 and VP9630
multipoint control units (MCUs). The document also describes how to view these CDRs.
NOTE
As the VP9660 is used in conjunction with the Service Management Center 2.0 (SMC2.0), description of
the CDRs produced by the VP9660 is provided in the HUAWEI SMC2.0 CDR Reference.
Intended Audience
This document is intended for:
l Technical support engineers

l Reseller engineers
l Enterprise customers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Conventions
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.
Issue 02 (2014-07-30) Huawei Proprietary and Confidential ii

CDR Reference About This Document
Symbol Description

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to
personal injury, equipment damage, and environment
deterioration.
Change History
Issue Date Description
02 2014-07-30 Added About This Document.
01 2014-05-28 This issue is the first official release.
Issue 02 (2014-07-30) Huawei Proprietary and Confidential iii

CDR Reference Contents
Contents
About This Document.....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 CDR................................................................................................................................................................................1
1.2 CDR File Name..............................................................................................................................................................1
1.3 CDR Export....................................................................................................................................................................1
1.4 Maximum Size and Maximum Number of Records in a CDR File...............................................................................1
2 CDR Formats..................................................................................................................................3
2.1 Conference CDRs...........................................................................................................................................................3
2.2 Point-to-Point CDRs.......................................................................................................................................................7
Issue 02 (2014-07-30) Huawei Proprietary and Confidential iv

CDR Reference 1 Overview
1 Overview
1.1 CDR
A CDR contains information about communication transaction in specified format. The
information includes the setup time, duration, and data traffic of a call, and is used for billing
and settlement.
1.2 CDR File Name

mcu-conf-cdr.xml
1.3 CDR Export

Step 1 Log in to the MCU web interface.
NOTE
The default user name and password are admin and Change_Me respectively. If the password has been
changed, contact your system administrator.
Step 2 Choose Settings > Maintenance > Export.
Step 3 Click Export All CDRs.
----End
1.4 Maximum Size and Maximum Number of Records in a

CDR File
The maximum size of an MCU CDR file is 100 MB, and each CDR file contains a maximum
of 1000 records.
The MCU moves CDRs to the specified FTP server and deletes the local CDRs, using the
following policies:
Issue 02 (2014-07-30) Huawei Proprietary and Confidential 1

CDR Reference 1 Overview
l If the MCU is hosting a conference, it does not move CDRs to the FTP server. If CDRs
have been stored for 14 days or longer, the MCU deletes them without moving them first.
l If the MCU is not hosting any conferences, it moves CDRs that have been stored for 7 days
or longer to the FTP server. If CDRs fail to be moved, they are deleted once they have been
stored for 14 days or longer.
l When the number of records in a CDR file reaches 1000, new records overwrite the old
ones.

CDR Reference 2 CDR Formats
2 CDR Formats
2.1 Conference CDRs

The MCU produces conference CDRs for conferences ended from the MCU web interface.
CDR File Name

mcu-conf-cdr.xml
NOTE
This file is exported from the MCU web interface.
CDR Save Path

CDRs are saved to /ata00:1/svrdata/cdr/ on the Compact Flash (CF) memory card. When the
MCU produces a CDR, it creates a folder whose name is the date when the CDR is produced in
yyyymmdd format, such as 20120830. In the folder, you can find the CDR file
20120830_cdr.xml and DAT files generated during conferences ended that day.
NOTE
The preceding files cannot be exported using commands.
The information display format of CDRs saved on the CF memory card is different from that of
CDRs displayed on the MCU web interface.
As CDRs saved on the CF memory card are difficult to read, this section uses the CDRs displayed
on the MCU web interface as an example.
Conference CDR Generation Prerequisites

The MCU produces a conference CDR only when the following prerequisites are met:
l The MCU is managed from its web interface.

l A conference is ended from the MCU web interface.

NOTE
The conference must be initiated using one of the following methods:

l The conference is initiated from the MCU web interface.
l The conference is scheduled from the MCU and the scheduled time arrives.
l The conference is an ad hoc conference defined on the MCU and is activated.
CDR Format
Conference CDRs are displayed in form of a conference list. Each conference CDR provides
call details about each participant in the conference.
Table 2-1 Conference parameters in a conference CDR
No. Field Type Description
1 Conference name String Unique identifier of a conference. The

conference name is defined when the
conference is initiated or scheduled on the
MCU or is activated following IVR
instructions from an endpoint.
2 Start time String Conference start time, accurate to the

second.
3 End time String Conference end time, accurate to the

second.
4 Conference duration String Duration for which the conference has run,
accurate to the second.
5 Convener String Conference convener name. If the

conference is an ad hoc conference, this
field is left blank. The convener is a user
predefined on the MCU web interface.
6 Conference type String Initiation type of the conference, which can

be ad hoc or non ad hoc.
Table 2-2 Participant parameters in a conference CDR
1 Time String Time when an event occurs, accurate to the

second.

2 Event String Event that occurs and is related to the

conference, which can be:
l The conference starts.
l The conference ends.
l A participant joins the conference.
l A participant exits the conference.
l A participant is added.
l A participant is deleted.
l The conference is extended.
l The number of reserved ports is
changed.
3 Information String Important information about the event.
4 Operator String User that triggers the event.
Table 2-3 Event parameters in the conference CDR
No. Event Information Recorded Information

Type
1 The conference starts. String Number of video parties and

number of audio-only parties
predefined for the conference.
2 The conference ends. String No information is displayed for

this event.


Type
3 A participant joins the String If participant capability is

conference. automatically negotiated:
l Participant name
l Video capability
l Audio capability
l Participant rate
If participant capability is user
defined:
l Participant name
l Video capability
l Audio capability
l Participant rate
If the participant joins the
conference by following IVR
instructions from an endpoint:
l Endpoint name
l Video capability
l Audio capability
l Participant rate
If the participant uses a Lync
client:
l Domain user name of the
Lync client
l User ID of the Lync client
l Video capability
l Audio capability
l Participant rate
The preceding information is
separated by a space.
4 A participant exits the String If the participant joined the

conference. conference using its IP address:
name of the participant that exits
the conference.
If the participant joined the
conference using its number:
l Participant call address
l Participant name


Type
5 A participant is added. String If the participant joined the

conference using its IP address:
l Participant name
l Video capability
l Audio capability
l Participant rate
conference using an address other
than its IP address:
l Participant name
l Video capability
l Audio capability
l Participant rate
6 A participant is deleted. String If the participant joined the

conference using its IP address:
name of the participant that is
deleted
conference using an address other
than its IP address:
l Participant name
7 The conference is String Conference extension time in

extended. minutes. Example: 120 minutes.
8 The number of reserved String New numbers of video ports and

ports is changed. audio-only ports, in format of
"number of video ports-number
of audio-only ports." For
example, if the numbers of the
reserved video ports and audio-
only ports are 4 and 6, the
displayed information will be
4-6.
2.2 Point-to-Point CDRs

After a call set up through the MCU's embedded GK is ended by either of the parties, the MCU
produces a point-to-point CDR.

CDR File Name

mcu-conf-cdr.xml
NOTE
This file is exported from the MCU web interface.
Point-to-Point CDR Generation Prerequisites

The MCU produces a point-to-point CDR only when the following prerequisites are met:
l The MCU is managed from its web interface.

l The MCU and the two parties' endpoints are registered with the MCU's embedded GK.
NOTE
An endpoint calls the other endpoint's participant number registered on the MCU's embedded GK. After
the call is set up, a point-to-point CDR on the MCU is generated when either party ends the call.
CDR Save Path

CDRs are saved to /ata00:1/svrdata/cdr/ on the CF memory card. When the MCU produces a
CDR, it creates a folder whose name is the date when the CDR is produced in yyyymmdd format,
such as 20120901. In the folder, you can find the CDR file 20120901_cdr.xml and
20120901_p2p.dat generated during the call.
NOTE
The preceding files cannot be exported using commands.
The information display format of CDRs saved on the CF memory card is different from that of
CDRs displayed on the MCU web interface.
Point-to-Point CDR Format

Point-to-point CDRs are displayed in form of a conference list. Each point-to-point CDR
provides call details about the calling and called parties.
Table 2-4 Details in a point-to-point CDR
1 Start time String Conference start time, accurate to the

second.
2 End time String Conference end time, accurate to the

second.
3 Conference duration String Duration for which the call has run,
accurate to the second.

4 Calling party information String Participant number, IP address, and call

signal (CS) port used when the calling
endpoint registers with the MCU's
embedded GK. Example:
0107771/200.54.1.71:1720.
5 Called party information String Participant number, IP address, and CS

port used when the called endpoint
registers with the MCU's embedded GK.
Example: 0107773/200.54.1.73:1720.
6 Call information String Participant rate.


Huawei Vp9660&Vp9650&Vp9630 v200r001c30 CDR Reference 02

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Huawei Vp9660&Vp9650&Vp9630 v200r001c30 CDR Reference 02

Загружено:

Авторское право:

Доступные форматы

HUAWEI VP9660&VP9650&VP9630

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2014-07-30) Huawei Proprietary and Confidential i

About This Document

l Technical support engineers

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 02 (2014-07-30) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

02 2014-07-30 Added About This Document.

01 2014-05-28 This issue is the first official release.

Issue 02 (2014-07-30) Huawei Proprietary and Confidential iii

About This Document.....................................................................................................................ii

Issue 02 (2014-07-30) Huawei Proprietary and Confidential iv

1.2 CDR File Name

1.3 CDR Export

Step 2 Choose Settings > Maintenance > Export.

Step 3 Click Export All CDRs.

1.4 Maximum Size and Maximum Number of Records in a

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 1

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 2

2.1 Conference CDRs

CDR File Name

This file is exported from the MCU web interface.

CDR Save Path

The preceding files cannot be exported using commands.

Conference CDR Generation Prerequisites

l The MCU is managed from its web interface.

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 3

The conference must be initiated using one of the following methods:

Table 2-1 Conference parameters in a conference CDR

No. Field Type Description

1 Conference name String Unique identifier of a conference. The

2 Start time String Conference start time, accurate to the

3 End time String Conference end time, accurate to the

5 Convener String Conference convener name. If the

6 Conference type String Initiation type of the conference, which can

Table 2-2 Participant parameters in a conference CDR

No. Field Type Description

1 Time String Time when an event occurs, accurate to the

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 4

No. Field Type Description

2 Event String Event that occurs and is related to the

3 Information String Important information about the event.

4 Operator String User that triggers the event.

Table 2-3 Event parameters in the conference CDR

No. Event Information Recorded Information

1 The conference starts. String Number of video parties and

2 The conference ends. String No information is displayed for

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 5

No. Event Information Recorded Information

3 A participant joins the String If participant capability is

4 A participant exits the String If the participant joined the

Issue 02 (2014-07-30) Huawei Proprietary and Confidential 6

No. Event Information Recorded Information

5 A participant is added. String If the participant joined the

6 A participant is deleted. String If the participant joined the

7 The conference is String Conference extension time in

8 The number of reserved String New numbers of video ports and