Вы находитесь на странице: 1из 60

eSpace UC

V200R001C02SPC500

CDR Reference

Issue 5
Date 2013-04-28

HUAWEI TECHNOLOGIES CO., LTD.


Copyright © Huawei Technologies Co., Ltd. 2013. 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 5 (2013-04-28) Huawei Proprietary and Confidential i


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference About This Document

About This Document

Overview
This document describes the CDR format and storage mechanism for enterprise administrators
to query CDR and locate faults in the eSpace UC system.

Intended Audience
This document is intended for enterprise administrators.

Symbol Conventions
The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level or medium level of risk


which, if not avoided, could result in death or serious
injury.

Indicates a hazard with a low level of risk which, if not


avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if not


avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.

Provides a tip that may help you solve a problem or save


time.

Provides additional information to emphasize or


supplement important points in the main text.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential ii


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference About This Document

Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.

Issue 05 (2013-04-28)
This issue is the fourth official release.

Issue 04 (2013-02-06)
This issue is the third official release.

Issue 03 (2012-12-24)
This issue is the second official release.

Issue 02 (2012-10-20)
This issue is the first official release.

Issue 01 (2012-07-30)
This issue is the trial release.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential iii


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference Contents

Contents

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


1 UC CDR Description....................................................................................................................1
2 CDRs on the Call AS Server........................................................................................................3
2.1 Basic Concepts...............................................................................................................................................................3
2.2 CDR Mechanism............................................................................................................................................................3
2.2.1 Mechanism for Generating EDR Files........................................................................................................................3
2.2.2 Mechanism for Deleting EDR Files............................................................................................................................3
2.2.3 Parameter Settings.......................................................................................................................................................4
2.3 EDR File Format and Structure......................................................................................................................................5
2.3.1 CDR Path.....................................................................................................................................................................6
2.3.2 Format of CDR File Names.........................................................................................................................................6
2.3.3 Format of EDR File Content.......................................................................................................................................7
2.4 Releasing Calls.............................................................................................................................................................16
2.4.1 Calling Party Releasing a Call...................................................................................................................................16
2.4.2 Called Party Releasing a Call....................................................................................................................................18
2.5 EDR File Fields............................................................................................................................................................20

3 CDR on the PGM.........................................................................................................................25


3.1 Overview......................................................................................................................................................................25
3.1.1 CDR Configuration Items..........................................................................................................................................25
3.1.2 CDR Description.......................................................................................................................................................26
3.1.3 Directory for Storing CDR Files...............................................................................................................................26
3.1.4 CDR Types................................................................................................................................................................27
3.2 CDR Configuration.......................................................................................................................................................28
3.2.1 Configuring CDR Files..............................................................................................................................................28
3.2.2 Setting the Maximum Size of a CDR File.................................................................................................................28
3.3 CDR Processing Mechanism........................................................................................................................................29
3.3.1 Related Components..................................................................................................................................................29
3.3.2 CDR Processing Process...........................................................................................................................................29
3.4 Universal CDR Format.................................................................................................................................................30
3.4.1 Format of the Statistics CDR File Name...................................................................................................................30
3.4.2 CDR Format Specifications.......................................................................................................................................31
3.5 CDR Instance................................................................................................................................................................32

Issue 5 (2013-04-28) Huawei Proprietary and Confidential iv


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference Contents

4 CDR on the eSpace Meeting......................................................................................................35


4.1 Overview......................................................................................................................................................................35
4.1.1 Basic Concepts..........................................................................................................................................................35
4.1.2 Mechanism for Processing CDRs..............................................................................................................................36
4.1.3 CDR Classification....................................................................................................................................................37
4.1.4 Types of CDRs Generated in Service Application Scenarios...................................................................................37
4.2 General Description of CDR Format............................................................................................................................37
4.2.1 CDR File Name Format.............................................................................................................................................37
4.2.2 CDR Format Specifications.......................................................................................................................................38
4.3 Detailed Description of CDR Format...........................................................................................................................39
4.3.1 Overview...................................................................................................................................................................39
4.3.2 CDR Format..............................................................................................................................................................40
4.4 Conference CDR...........................................................................................................................................................44
4.5 User CDR.....................................................................................................................................................................46
4.6 CDR for Canceling a Scheduled Conference...............................................................................................................48
4.7 CDR for Creating a Scheduled Conference..................................................................................................................50
4.8 CDR for Modifying a Scheduled Conference..............................................................................................................52

Issue 5 (2013-04-28) Huawei Proprietary and Confidential v


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 1 UC CDR Description

1 UC CDR Description

Call detail records (CDRs) are users' original call records.

CDR Introduction
Unified communications (UC) CDR records call information including numbers of the calling
party and the called party, call duration, and call type.

CDR Generation Scenarios


UC CDRs include call CDRs generated by the Call AS server, group message CDRs generated
in the pragmatic general multicast (PGM) system, and conference CDRs generated in the eSpace
Meeting system. Table 1-1 lists the description about EDR generation scenarios.

NOTE

Here, Call AS, PGM, and Meeting servers are logic concepts that refer to servers where the Call AS, PGM,
and Meeting services are deployed.

Table 1-1 CDR generation scenarios


EDR Type Generation Scenario NE Generated from EDRs

Call CDRs Call CDRs are generated Call AS


when:
l A PC user makes a call to
another PC user.
l A PC user makes a call to
a fixed-line phone user.
l A PC user's call is
forwarded.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 1


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 1 UC CDR Description

EDR Type Generation Scenario NE Generated from EDRs

Group message CDRs Group message CDRs are PGM


generated in the following
scenarios:
l Temporary group IM
l Contact Group IM
l Point-to-point IM
l System message
l File transfer
NOTE
Large messages do not generate
CDRs.

Conference CDRs Conference CDRs are eSpace Meeting


generated in:
l Voice conferences
l Video conferences
l Data conferences

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 2


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

2 CDRs on the Call AS Server

2.1 Basic Concepts


The Call AS generates call detail records (CDRs) for incoming and outgoing calls in an
enterprise.
When a CDR is generated in the Call AS, the management server and third-party application
can use SFTP to obtain the CDR from the Call AS server. The enterprise can query the CDRs
for call information and check outgoing call fees with the carrier.
A CDR contains the called party and calling party's numbers, call duration, start and end times
of the call, call type, incoming and outgoing trunk information, and voice quality monitor (VQM)
information.

2.2 CDR Mechanism


This topic describes the mechanisms of generating and deleting CDRs and the configuration of
these mechanisms.

2.2.1 Mechanism for Generating EDR Files


Calling CDRs, as known as EDR files, are generated from the Call AS.
The Call AS server begins to generate an EDR file when the number of EDR events exceeds N
or when the interval at which the Call AS server generates EDR events is longer than M seconds
after you close an EDR file. You can configure N and M values. For example, you can set them
to 5 and 10 respectively.
l When the number of EDR events exceeds 5 after you close an EDR file, the Call AS server
begins generating a new EDR file.
l When the interval at which the Call As server generates EDR events is longer than 10
seconds after you close an EDR file, the Call AS server begins generating a new EDR file.

2.2.2 Mechanism for Deleting EDR Files


The Call As periodically deletes EDR files from the backup directory.
The Call As saves EDR files in the backup directory and deletes them at zero o'clock after N
days.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 3


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

NOTE
You can configure the value of N in Period for keeping the EDR File (days) on the eSpace EMS. For
details about the configuration, see 2.2.3 Parameter Settings.

2.2.3 Parameter Settings


This topic describes how to set EDR mechanism parameters.

Log in to the eSpace EMS and choose Resource > Resource Management. On the Resource
Management page that is displayed, select an NE, such as SEE_404011, and click .

In the left navigation tree, choose Configuration Management. In Service View, choose
Service Related Configuration > EDR Configuration > EDR Generation File

Configuration, and click . Figure 2-1 shows the EDR parameters.

Figure 2-1 Parameter settings

Table 2-1 describes the parameters.

Table 2-1 EDR parameters

Parameter Description Value Range Default Value

Configuration item Unable to be set. 1 1


primary key

Max. size of the EDR EDR files that are being An integer 1024
file (KB) written are stored in buffer ranging from 1 to
and called temporary files. 1048576.
When a temporary EDR file
exceeds Max. size of the
EDR file, the EDR file is
moved to completed.
A new temporary EDR file is
created in buffer.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 4


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Parameter Description Value Range Default Value

Interval (minutes) EDR files that are being An integer 5


written are stored in buffer ranging from 1 to
and called temporary files. 1048576.
When the existence time of a
temporary EDR file exceeds
Interval, the EDR file is
moved to completed.
A new temporary EDR file is
created in buffer.

Number of triggering Number of EDRs written to An integer 10


events for writing file an EDR file every time. ranging from 1 to
When EDRs reach a specified 1048576.
number, the system
automatically writes the
EDRs to an EDR file.

Interval for Interval for writing EDRs to An integer 10


triggering writing an EDR file. ranging from 1 to
file (s) When the specified interval 1048576.
reaches, the system
automatically writes the
EDRs to an EDR file.

Compress EDR file Whether to compress an EDR 0: no 0: no


file when moving it to 1: yes
completed.
CAUTION
Compressing EDR files
occupies CPU resources, in
particular when the EDR files
are large.

Separator Separator between fields in One character , (except


an EDR file. Quotation
marks)

Period for keeping Days when EDR files are An integer 7


the EDR file (days) reserved in backup. ranging from 1 to
1048576.

Length of the file Length of the serial number An integer 5


name SN of an EDR file. ranging from 1 to
9.

2.3 EDR File Format and Structure


This topic describes the directory for storing EDR files, and formats of the EDR file name and
content.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 5


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

2.3.1 CDR Path


CDR files are stored in $ENIP_HOME/record/edr.

Save Path
CDR files consist of temporary and complete files. The specific save paths are as follows:
l When the size of CDR files is smaller than Max. size of the EDR file (temporary), the
EDR files are saved to $ENIP_HOME/record/edr/buffer/.
l When the size of CDR files is greater than Max. size of the EDR file (complete), the EDR
files are moved from $ENIP_HOME/record/edr/buffer/ to $ENIP_HOME/record/edr/
completed/.

Example
The calling number's CDRs are stored in $ENIP_HOME/record/edr/completed, where:
l edr refers to the subdirectory under $ENIP_HOME/record.
l completed refers to a file folder in the subdirectory.
l UCSOC refers to the file prefix of the calling number's CDR, for example, UCSOC.
20130517173956.001.00000.dat.
l UCSOC refers to the file prefix of the called number's CDR, for example, UCSTC.
20130517173958.001.00000.dat.

2.3.2 Format of CDR File Names


This topic describes the format of CDR file names.
Format of CDR file names in the eSpace element management system (EMS):
<Service_Identifier>.<YYYYMMDDHHMMSS>.<NodeID>.<Sequence_Number>.dat
Table 2-2 describes the fields in the preceding format.

Table 2-2 Format of CDR file names


Field Definition

Service_Identifier File name prefix that identifies the service


process. For example, UCSOC or UCSTC.

YYYYMMDDHHMMSS Time when an EDR file is generated. The


value HH is in 24-hour format.

NodeID Service node ID that is obtained from the


default $ENIP_HOME/config/node.cfg file
on the enhanced network intelligent platform
(ENIP) platform.

Sequence_Number Sequence number of an EDR file.

Typical example:

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 6


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

UCSOC.20130517173956.001.00000.dat

2.3.3 Format of EDR File Content


This topic describes the format of the EDR file content.

EDR file content consists of the header, body, and trailer.

l Format of the header


HEADER, Timestamp, Application name, Node ID, EDR file counter, and Version number
Table 2-3 describes the preceding parameters in the header.

Table 2-3 Parameter description (1)

Parameter Description

HEADER Specified identifier of the file header.

Timestamp Time when an EDR file is generated.

Application name Service name.

Node ID Node ID

EDR file counter Unique sequence number of an EDR file.

Version number Version number of the service.

l Format of the body


0,3,1,0,20060,,20060,20061,,20061,,,20110920093303,
+08:00,20110920093321,
+08:00,18,1000,25,25,0000001500,0000001500,0,00,,900,,0000,
,,,,,,,,,,,,,,,0,
Table 2-4 describes the preceding parameters in the body.

Table 2-4 Parameter description (2)

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

1 Sequence An 0 EDR sequence number.


number integer. The EDR sequence number is
generated for a service
application, for example, in a
report system.

2 Flag An 3 Flag.
integer.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 7


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

3 CDR type Char[2] 1: calling through Identifies a CDR type.


the SIP trunk.
2: called through
the SIP trunk.
3: call
forwarding.
4: call transfer.
5: group pickup.
6: break-in.
7: calling party
using the one
number link you
(ONLY) service
through the SIP
trunk.
8: called party
using the ONLY
service through
the SIP trunk.
9: service
reregistration/
deregistration.
You can press the
star key (*) to
register a service
and press the
pound key (#) to
deregister a
service.
10: enterprise
main number.
11: call
forwarding from
the enterprise
switchboard.
12: call unhold.
13: call park.
14: calling in the
click to dial
(CTD) service.
15: called in the
CTD service.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 8


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

16: three-way
calling.
17: hunting
group.
18:follow me
19: linked call
20: emergency
call
99: malicious call

4 Charging Char[1] 0: intra-office Identifies the charging type of a


type call. call.
1: local call.
2: national call.
3: international
call.

5 Calling Char[32] Calling number This number is provided by the


number reported in an universal access platform (UAP)
INVITE message or information management
system (IMS) center.

6 Calling Char[32] International The calling party's number is


party's format: CC identified in the international
number +NDC+SN format.
on the NOTE
Internet If the calling party does not have a
calling number on the Internet, the
value of this parameter is null.

7 Calling Char[12] Calling party's UC user's number on the


party's number on the enterprise intranet.
number enterprise NOTE
on the intranet. If the calling party is not a UC user,
enterprise the value of this parameter is null.
intranet

8 Called Char[32] Called party's This number is provided by the


party's number reported UAP or IMS center.
number in an INVITE NOTE
message. When registering a service, you must
press the star key (*) before dialing
the called party's number. For
example, *51.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 9


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

9 Called Char[32] International The called party's number is


party's format: CC identified in the international
number +NDC+SN format.
on the NOTE
Internet 1: The called party's number shows in
an international call.
2: The called party's number is null
when you register a service.

10 Called Char[12] Enterprise UC user's number on the


party's number. enterprise intranet.
number NOTE
on the 1. If the called party is not a UC
enterprise user, the value of this parameter
intranet is null.
2. If the original called party's
number is an abbreviated dialing
(ABD) number, the user must set
this parameter to a number related
to the ABD service.
3. If the called party's number is an
access code, set this parameter to
the access code.
4. The called party's number is null
when you register a service.

11 Calling Char[12] Calling party's 1. If the CDR type is 3 (call


party's additional forwarding), this number is the
additional number on the calling party's original number
number enterprise on the enterprise intranet.
on the intranet. 2. If the CDR type is not 3, the
enterprise value of this parameter is null.
intranet

12 Calling Char[32] Calling party's 1. When the CDR type is 3 (call


party's additional forwarding), this number is the
additional number on the calling party's additional
number Internet number on the enterprise
on the intranet.
Internet 2. If the CDR type is not 3, the
value of this parameter is null.

13 Start time Char[14] Format: Time when a UC user answers a


YYYYMMDDH call.
HMMSS Example: 20010309103713

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 10


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

14 Start time VARCH [{+|-}Hh:Mm] Identifies the time when the DST
of the AR[10] [<1SP>DST] time starts on the Call As server.
daylight +08:00 DST NOTE
saving -07:30 1. The offset time zone Hh:Mm
time varies when the DST is enabled
(DST) or disabled.
2. When the DST is enabled, the
Call As server always displays
the DST identifier.
For example, when the Call As
server is in the United States
where the coordinated universal
time (UTC) offset time zone is
-08:00, when the DST is enabled
in June, the UTC offset time zone
is -07:00.

15 End time Char[14] Format: Time when a UC user releases a


YYYYMMDDH call.
HMMSS Example: 20010309103713

16 End time VARCH [{+|-}Hh:Mm] Identifies the time when the DST
of the AR[10] [<1SP>DST] time ends on the Call As server.
DST +08:00 DST NOTE
-07:30 1. The offset time zone Hh:Mm
varies when the DST is enabled
or disabled.
2. When the DST is enabled, the
Call As server always displays
the DST identifier.

17 Conversat An 0-2147483647 Duration between the


ion integer. (in seconds) conversation start time and end
duration time.
For example, 70 indicates that the
conversation duration is 70
seconds.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 11


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

18 Media Char[10] A string of four Media type of a call.


type binary digits. Examples:
0: no l 1000 indicates a voice call.
1: yes l 0100 indicates a video call.
Each binary digit
indicates the
media type of a
call:
First digit: voice
call
Second digit:
video call
Third digit: fax
call
Fourth digit:
modem call

19 Area code Char[6] Area code of a Area code of a calling party.


of a calling party
calling without the
party prefix 0.

20 Area code Char[6] Area code of a Area code of a called party.


of a called called party
party without the
prefix 0.

21 ID of the Char[10] ID of the ID of the enterprise that the calling


enterprise enterprise that party belongs to.
that the the calling party NOTE
calling belongs to. If the called party is not a UC user, the
party value of this parameter is null.
belongs to

22 ID of the Char[10] ID of the ID of the enterprise that the called


enterprise enterprise that party belongs to.
that the the called party NOTE
called belongs to. If the called party is not a UC user, the
party value of this parameter is null.
belongs to

23 Special Char[1] Special number 0: a non-special number


number indicator: 1: a special number
indicator 0: no
1: yes

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 12


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

24 Trigger Char[1] 0: normal Identifies the call trigger type.


type 1: card

25 Card Char[12] - Card number.


number NOTE
Only card users need this parameter.

26 Reason Char[3] 900-999 Reason for releasing a UC call.


for For details, see 2.4 Releasing
releasing Calls.
a call

27 Charging N/A 0: charged 0: charged (outer-office calls)


service 1: free of charge 1: free of charge
l Intra-office calls
l Calls made from an out-office
user to an intra-office user
l Service registration and
deregistration
l Special number service

28 Error Char - -
reason
code

29 Service VARCH Service 1. When the CDR type is 9, this


registratio AR[32] registration parameter is the service
n number number registration number.
2. When the CDR type is not 9,
the value of this parameter is
null.

30 Incoming N/A N/A From the eSpace U2900 or IMS.


trunk
number

31 Incoming N/A N/A


circuit
number

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 13


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

32 Incoming N/A 0: voice


call capability for
transmissi users that are not
on connected to the
capability integrated
of the services digital
TDM port network (ISDN)
0x10: video
capability

33 Calling N/A Calling party's


party's MG index.
MG index

34 Outgoing N/A N/A


trunk
number

35 Outgoing N/A N/A


circuit
number

36 Outgoing N/A 0: voice


call capability for
transmissi users that are not
on connected to the
capability integrated
of the services digital
TDM port network (ISDN)
0x10: video
capability

37 Called N/A Called party's


party's MG index.
MG index

38 Audio VARCH 1–5 This parameter identifies audio


quality AR[10] quality of a complete call.
index A alrger value indicates higher
audio quality.

39 Codec VARCH G.711, G.723, G. This parameter displays the codec


type of a AR[10] 729, iLBC type of a terminal when a call is
terminal complete.

40 Delay VARCH Audio quality If a delay is greater than 250 ms,


AR[10] index. the audio quality is poor.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 14


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Seri Paramet Paramet Value Range Description


al er er Type
Nu
mbe
r

41 Jitter VARCH Audio quality This parameter identifies audio


AR[10] index. quality of a complete call.

42 Packet VARCH Percentage of This parameter identifies audio


loss rate AR[10] lost packets to the quality of a complete call.
total sent The packet loss rate should be less
packets. than 0.0005.

43 IP address - Terminal IP The IP address of a terminal that


of a address. reports audio quality is displayed
terminal when a call is complete.
that
reports
audio
quality

44 Client Char[1] 0: eSpace -


type Desktop
1: eSpace Mobile
2: eSpace Web
3: iPad
4: IP Phone

45 CTD call char[32] UC account of The UC account of the user that


initiator the user that initiates the CTD call is displayed.
initiates the CTD
call.

l Format of the trailer


TRAILER, Timestamp, Application name, Node ID, EDR file counter, Version number,
and Number of EDR records
Table 2-5 describes the preceding parameters in the trailer.

Table 2-5 Parameter description (3)

Parameter Description

TRAILER Specified identifier of the file trailer.

Timestamp Time when an EDR file is generated.

Application name Service name.

Node ID Node ID.

EDR file counter Unique sequence number of an EDR file.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 15


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Parameter Description

Version number Version number of the service.

Number of EDR records Number of EDR records excluding the first


and the last records.

2.4 Releasing Calls


The calling party or called party releases calls in certain scenarios. This topic describes the
reasons, error types, and reason codes related to these scenarios.

2.4.1 Calling Party Releasing a Call


This topic describes reasons why the calling party releases calls.
Table 2-6 describes scenarios, error types, and reason codes.

Table 2-6 Calling party releasing a call


Reason Error Type Reason Code

The call ends normally. Normal 900

The calling party fails the Authentication Failed 901


authentication.

The calling party enters Authentication Failed 901


incorrect user name or
password when registering
services.

The calling party attempts to Function not enable 902


use an unavailable service.

The called party's number Invalid number format 903


cannot be analyzed.

The called party enters the Invalid number format 903


value of StarKey in an
incorrect format.

Black/White List Call Restriction 904

The user to whom the calling Operation limit 905


party breaks in is unavailable
when the user has two calls or
is being held, or when the
calling party is not in a
conversation.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 16


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Reason Error Type Reason Code

The call cannot be connected Operation limit 905


to the pickup group when the
called party's phone does not
ring.

The switchboard receiving User No Input 906


the number times out.

The calling party abandons Caller Abandon 907


the call.

The called party's number is Subscriber absent 404


not registered.

The called party is busy. Callee Busy 486

The called party does not Callee No Answer 487


answer the call.

Errors such as moveLeg System Error 500


failure occur in the system.

The calling party failed to Function Setting Failed 908


configure a service (for
example, the calling party
failed to register or deregister
services or change
passwords).

A database exception occurs. Service System Error 909

Some services cannot be Conflict Service 910


enabled at the same time.

The number of times that the Exceed MaxFwdTime 911


call is forwarded exceeds the
threshold.

Call barring callLimit 912

The calling party does not Wrong Passwd 913


enter a password or has
entered an incorrect
password when registering or
deregistering the password-
based call restriction service.

The calling party attempts to Wrong Type 914


configure an incorrect
service type when registering
or deregistering the
password-based call
restriction service.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 17


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Reason Error Type Reason Code

The calling party fails to Resume GetCallParkInfo 915


obtain Doid information Failed
when resuming call
reservation.

The calling party fails to Invoke IDL Failed 916


invoke the interface
definition language (IDL)
interface when binding the
session failed, invoking the
IDL times out, or receiving
an exception message after
invoking the IDL

The calling party has entered RLC_ONENUMBERBIND 917


different UC accounts for the _UCACCOUT_NOT_SAM
primary number and E
secondary numbers when
unbinding ONLY numbers.

Moving leg failed. move leg failed 918

DetachMedias/ DetachMedia failed 919


AttachMedias failed

Area-based VoIP whitelist VoIP Unavailable 1


restriction.

Area-based CTD whitelist CTD White-Area Limited 2


restriction.

Heartbeat timeout HeartBeat Timeout 921

Traffic control Cocurent Call Limited 920

2.4.2 Called Party Releasing a Call


This topic describes reasons why the called party releases calls.
Table 2-7 describes scenarios, error types, and reason codes.

Table 2-7 Called party releasing calls


Reason Error Type Reason Code

The call ends normally. Normal 900

The called party fails the Authentication Failed 901


authentication.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 18


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Reason Error Type Reason Code

Call collection or password Authentication Failed 901


authentication fails (in
scenarios such as remote
registration)

The called party attempts to Function not enable 902


use an unavailable service.

The called party's number Invalid number format 903


cannot be analyzed.

The called party enters the Invalid number format 903


value of StarKey in an
incorrect format.

Black/White List Call Restriction 904

Number collection timeout User No Input 906


(in scenarios such as main
number processing)

The calling party abandons Caller Abandon 907


the call.

Function (such as remote Function Setting Failed 908


service registration and
deregistration, and password
changing) configuration
failed.

Database exceptions occur. Service System Error 909

Service conflict occurs (in Conflict Service 910


scenarios such as service
registration.)

The number of times that the Call Rejected 911


call is forwarded exceeds the
upper limit.

The called party's number is Subscriber absent 404


not registered.

The called party is busy. Callee Busy 486

The called party does not Callee No Answer 487


answer the call.

Errors such as moveLeg System Error 500


failure occur in the system.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 19


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Reason Error Type Reason Code

The calling party fails to Invoke IDL Failed 916


invoke the IDL interface
when binding the session
failed, invoking the IDL
times out, or receiving an
exception message after
invoking the IDL

Moving leg failed. move leg failed 918

DetachMedias/ DetachMedia failed 919


AttachMedias failed

Area-based VoIP whitelist VoIP Unavailable 1


restriction.

Area-based CTD whitelist CTD White-Area Limited 2


restriction.

Heartbeat timeout HeartBeat Timeout 921

Traffic control Cocurent Call Limited 920

2.5 EDR File Fields


This topic describes fields in an EDR record.

Original EDR
A calling number's EDR is used as an example here:

Header: HEADER,20110920093234,UCSOC,1,12,10001

Body: 0,3,1,0,20060,,20060,20061,,20061,,,20110920093303,
+08:00,20110920093321,
+08:00,18,1000,25,25,0000001500,0000001500,0,00,,900,,0000,,,,
,,,,,,,,,,,,0,

Trailer: TRAILER,20110920093234,UCSOC,1,12,10001,1

Detailed Description
l Table 2-8 describes header fields.

Table 2-8 Description of record header fields

Value Description

HEADER Default file header.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 20


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Value Description

20110920093234 Time when the EDR file is generated (in


the Year + Month + Day + Hour + Minute
+ Second format).

UCSOC File name prefix that identifies the calling


party's EDR file.

1 Node ID.

12 Indicates the twelfth EDR.

10001 Service version


Service version of the calling party's EDR
file is 10001.

l Table 2-9 describes record body fields.

Table 2-9 Description of record body fields


Sequence Number Value Description

1 0 EDR sequence number.

2 3 Flag.

3 1 The CDR type is Calling


from the SIP trunk.

4 0 The charging type is Intra-


office call.

5 20060 Calling party's number.

6 Null The calling party does not


have a number on the
Internet.

7 20060 The calling party is a UC


user whose number on the
enterprise intranet is
20060.

8 20061 Called party's number.

9 Null Called party's number on


the Internet
The called party's number is
null in the star button
service.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 21


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Sequence Number Value Description

10 20061 The called party is a UC


user whose number on the
enterprise intranet is
20061.

11 Null Calling party's additional


number on the enterprise
intranet.
The number is null when
the CDR type is 1.

12 Null Calling party's additional


number on the Internet
The number is null when
the CDR type is 1.

13 20110920093303 Time when the UC user


begins to receive the call (in
the Year + Month + Day +
Hour + Minute + Second
format).

14 +08:00 Start time of the DST.

15 20110920093321 Time when the UC user


finishes receiving the call
(in the Year + Month + Day
+ Hour + Minute + Second
format).

16 +08:00 End time of the DST.

17 18 The call duration is 18


seconds.

18 1000 Voice call.

19 25 National area code of a


calling party.

20 25 National area code of the


called party.

21 0000001500 The calling party is a UC


user whose enterprise ID is
0000001500.

22 0000001500 The called party is a UC


user whose enterprise ID is
0000001500.

23 0 A non-specific number.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 22


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Sequence Number Value Description

24 0 The call is triggered


normally.

25 Null The user is not a card user.

26 900 Reason code.


The call ends normally. The
error type is Normal.

27 Null The release user is


unknown.

28 0000 The call is initiated


normally. The error code is
0000.

29 Null The CDR type is Others.

30 Null The value is exported from


the eSpace U2900 or IMS.
31 Null

32 Null

33 Null

34 Null

35 Null

36 Null

37 Null

38 Null -

39 Null -

40 Null -

41 Null -

42 Null -

43 Null -

44 0 The terminal type is eSpace


Desktop.

45 Null Non-CTD call

l Table 2-10 describes record trailer fields.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 23


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 2 CDRs on the Call AS Server

Table 2-10 Description of record trailer fields


Value Description

TRAILER Default record trailer.

20110920093234 Time when the EDR file is generated (in


the Year + Month + Day + Hour + Minute
+ Second format).

UCSOC File name prefix that identifies the calling


party's EDR file.

1 Node ID.

12 Indicates the twelfth EDR.

10001 Service version


Service version of the calling party's EDR
file is 10001.

1 Number of EDR records excluding the first


and the last records.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 24


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

3 CDR on the PGM

3.1 Overview

3.1.1 CDR Configuration Items


This topic describes how to query CDR configuration items in the eSpace EMS.

The procedure for querying CDR configuration items in the eSpace EMS is as follows:

1. Log in to the eSpace EMS as the admin user.

2. Choose Resource > Resource Management > SNE > Message_404201. Click . The
Message_404201 Manage page is displayed.
3. Choose Configuration Management > MSGBC > Real-Time CDR Format
Configuration. Set Time format of CDR file, CDR file name, and Backup flag on the
page as shown in Figure 3-1.

Figure 3-1 CDR configuration items

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 25


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

3.1.2 CDR Description


A CDR follows a specified format to record the information about a charging event. The recorded
information includes call setting up time, call duration, and quantity of transmitted data.

The CDRs are used for charging and settlement. In a charging event, the call fee may be paid
by one party or shared by multiple parities. The system generates an independent CDR for each
payer. That is, a charging event may involve multiple CDRs. For example, when the call duration
is quite long or multiple payers are involved in a call, multiple CDRs are generated.

3.1.3 Directory for Storing CDR Files


The CDR generation nodes such as the Messaging store the CDR files in specified directories.
The directories for storing CDR files vary with the CDR generation nodes.

The directory for storing the CDR files is defined by the CI dirName (Path). You can set the
directory for storing CDR files according to the actual situation. After the directory is set, the
CDRServer creates the dir directory in the set directory.
NOTE
The dir directory is defined by the CI dirName (Path).

The dir directory contains the following subdirectories:


l buffer
Directory where the generated CDR files are stored. When CDR files in the buffer directory
reaches the switchover threshold, the system moves these CDR files to the bak and send
directories.
The mechanism is as follows:
The generated CDR files are stored in the send directory.
If the CDR files need to be backed up, they are copied to the bak directory.
If the DBService adopts the load mode to store SMs into the history database, some
generated CDR files are stored in the load directory, and the other CDR files are stored in
the other directory.
l send
Directory where CDR files for external entities to obtain are stored.
l bak
Backup directory of CDR files. The backup CDR files are stored for three months by
default.
– When the value of the backup flag is 0, CDR files are not backed up.
– When the value of the backup flag is 1, CDR files are backed up.
– When the value of the backup flag is 2, CDR files are backed up. In the bak subdirectory,
the CDR files are named after the related dates. The date format is YYYYMMDD.
l load (only for history CDRs)
The CDR files in the load directory are used by the DBService when SMs are stored into
the history database in load mode. That is, the DBService reads SMs from the history CDR
files in the load directory, and then stores the SMs into the history database.
l other (only for history CDRs)

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 26


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

If the HCDRServer receives SMs that were submitted to the Messaging three days before,
the history CDR files related to these SMs are stored in the other directory and the send
directory at the same time.

3.1.4 CDR Types


Table 3-1 describes the types of the CDRs.

Table 3-1 CDR types


CDR CDR Type

History CDRs 10

MO CDRs 11

MT CDRs 12

Alert_SC CDRs 13

Service Statistics CDRs 14

System_SC CDRs 15

Notify_SM CDRs 16

Service Trigger Failure CDRs 17

Traffic Statistics CDRs 18

Delivery Delay CDRs 19

Repository Message CDRs 20

In-Net/Out-Net Service Statistics CDRs 21

VASGW Contents CDRs 26

Charging CDRss check

PPS Reimbursement CDR pps

Local Reimbursement CDRs charge

History CDRs of SIP Messages 40

MO CDRs of SIP Messages 41

MT CDRs of SIP Messages 42

Register_SC CDRs of SIP Messages 43

System_SC CDRs of SIP Messages 45

Service Trigger Failure CDRs of SIP Messages 47

Send Email CDRs 50

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 27


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

3.2 CDR Configuration

3.2.1 Configuring CDR Files


This topic describes how to configure CDR files in the eSpace EMS.

You can configure the CDR files by referring to Table 3-2.

Table 3-2 CIs of CDR files

Name Format Description Example

Path Configure the directory of CDR files The directory for


according to the actual need. historical CDR files
can be named as cdr/
history.

Time format of The values are as follows: The default value is


CDR file l 0(YYYYMMDD) 0.
l 1(YYYYMMDDHH)
l 2(YYYYMMDDHHMM)
l 3(YYYYMMDDHHMMSS)

CDR file name Name format of CDR files. The name of a


AAA, BBB, and CCC: Set these parameters as historical CDR can
required. be named as prm%
s_01010%09d.unl.
%s: indicates the time format type of CDR
files.
%0nd: Set n to an integer that ranges from 0
to 9. When the value of n is 4, %04d indicates
that the value range of the CDR file sequence
number is from 0000 to 9999. At 00:00 every
day, a new CDR file is generated. The starting
value and digits of the sequence number can
be set.

Backup flag Backup flag. The default value is


l 0(Not backup) 2.
l 1(Backup)
l 2(Backup by time)

3.2.2 Setting the Maximum Size of a CDR File


The maximum size of a CDR file is restricted.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 28


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

If the CDR files are backed up by the date, the CDRServer creates a directory named after a date
in the bak directory every day. The date is in the format of YYYYMMDD. The CDRs are stored
in the related directory.

The CDR files being processed are in the buffer directory. When a CDR file reaches the specified
size (the value of maxBillLen) or the specified time (the value of maxBillTime), the CDR file
in the buffer directory is backed up in the bak directory; meanwhile, the CDR file in the
buffer directory is moved to the send directory.

The billing system and report system can obtain the CDR files in the send directory through
FTP or a shared directory.

Table 3-3 describes the CIs related to the maximum size of a CDR file.

Table 3-3 CIs defining the maximum size of a CDR file

Name Unit Value Range Default Value

Max CDR file switch length Kbyte 1-1048576 2048


(KB)

Max CDR file switch Second 1-172800 900


duration (second)

Backup file save duration Month 0-12 3


(month) When the value is 0, the
CDRs are not deleted
automatically.

3.3 CDR Processing Mechanism

3.3.1 Related Components


The Messaging generate CDRs through the CDRServer.

The CDRServer follows the configured file format to write the CDRs into the related CDR files
in a designated directory. The report system and other modules can obtain these CDR files
through FTP or a shared directory.

The HCDRServer processes history CDRs. The HCDRServer:


l Provides an interface for the PGM to write history CDRs.
l Stores the generated CDRs into the CDR files in the load directory.
l Supports the DBService to read SMs from the CDR files and store SMs into the database
in load mode.
l The report system and other modules can obtain these CDR files through FTP or a shared
directory.

3.3.2 CDR Processing Process


Figure 3-2 shows the process for processing all types of the CDRs.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 29


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

Figure 3-2 CDR processing process

FTP File Transfer Protocol

ODBC open database connectivity

The CDRServer and HCDRServer saves the CDRs into files, and then generates CDR files. The
following are the process for processing the CDR files:
l The pre-process system accesses the statistics CDR directory and scans CDR files in this
directory. It copies the new CDR files to its local directory, makes resolution, and collect
statistics on the CDR records according to the user-defined rules. Then it generates the
statistics result table, and then writes the statistics table into the report database for the use
by the intelligent report system and the network management system.
The report system is responsible for generating and displaying reports. It takes the statistics
table generated by the pre-statistics system from the report database, and generates service
reports by using the user-defined templates. By invoking the stored procedures in the report
database, it implements data statistics.
l The PGM writes history CDRs through the HCDRServer. If the load mode is adopted, the
DBService reads SMs from history CDRs, and then stores the SMs into the history database.
The report system and other modules can obtain these CDR files through FTP or a shared
directory.

3.4 Universal CDR Format

3.4.1 Format of the Statistics CDR File Name


The format of the statistics CDR file name is as follows:
{Prm}{YYYY}{MM}{DD}_{AA}{BBB}{xxxx}.{unl}
Table 3-4 describes the names of the statistics CDR file.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 30


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

Table 3-4 Name description of the statistics CDR file


Field Description

Prm Indicating that the CDR type is the statistics CDR.

YYYY Year for backup.

MM Month for backup.

DD Day for backup.

AA The value of AA is always 01.

BBB CDR type number.


The Messaging can generate CDR data of many types. The CDR data of
different types are stored in different CDR files.
All the CDR types are numbered uniformly. The CDR type name is used to
name the original CDR data file.

xxxx Serial number. It ranges from 0 to 9999. That is, up to 10,000 original CDR
files are generated every day. (A new file is generated at 0:00 every day.)
Note that the value of this CI cannot be too small when the SM traffic is heavy;
otherwise, the last CDR file of a day is oversize. If the value of xxxx is FFFF,
it indicates an abnormal CDR file.

An example of the CDR file name is as follows:


Prm20070601_010100001.unl
This file name indicates the first history CDR file generated by the Messaging on June 1, 2007.

3.4.2 CDR Format Specifications


This topic describes the format of PGM service CDRs.
PGM service CDRs are stored in /home/see/cdr/pgmbill. Table 3-5 describes CDR fields.

Table 3-5 CDR fields


No. Name Description

1 Message serial number The serial number starts from


0 at the beginning of every
day and increases by degree.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 31


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

No. Name Description

2 Message type The message type


specifications are as follows:
l TG: temperature group
message
l IM: instant message
l Gm: group message
l System: system message
l FT: file transmission

3 Sending party's number Message sending party's


number (in SIP URI format).

4 Receiving party's number Message receiving party's


number (in SIP URI format).
The value of this parameter is
empty if the message is a
temporary group message.

5 Message sending time The message sending time is


displayed in the format of
yyyy-mm-
ddThh:mm:ss.sss.

6 Message content The message content is a


string of characters. The
temperature group, instant,
group, and system messages
are encoded in base64
format. The file transmission
message is in plain texts.

7 Group ID Temporary group ID. The


value of this parameter is
empty if the message is not a
temporary group message.

8 Moderator number Routing number of a


temporary group's
moderator. The value of this
parameter is empty if the
message is not a temporary
group message.

3.5 CDR Instance


This topic describes fields in an original CDR record.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 32


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

Original CDR Record


0,TG,sip:3867023@nj13219225.huawei.com,,
2013-03-19T00:02:53.000,WWTJBz
+d9ZGcl8N0exTj5kpZHquyJzpLEfJ1rbNQBzhKFYH/Gwpcn9gIN03ePjaUwpz/
sMgAAYMe8PUiV1aSJGWT
+2NxHAJtrWhb84nuXqRx6BNVDHAku4H1Wyc84D2mvEsY9H80Kau4Pk
+GZGEMpCDe0gvFFIgdfwkMXFb1 gsgW2yrq
+XkxxktMszgxVhcREdIQ5i0pQgy7k4KMKaeylpKM/0oraYkcv5bQdPXDQSF/
Sl2/Mi8m7MPXl6Fd4vF9lvFpmPTPWJNK0Yc3Ltr8sAPiVzZp9pqKDA
+JwRru8uo=,sip:22522513622115001@chatas.huawei.com,sip:
3867023@nj13219225.huawei.com

CDR Field Description

Table 3-6 Description of a temporary group CDR.

No. Value Description

1 0 The message serial number is 0.

2 TG The message is a temporary group message.

3 sip: Message sending party's number (in SIP URI


3867023@nj13219225.huawei.co format).
m

4 - Message receiving party's number (in SIP


URI format). The value of this parameter is
empty if the message is a temporary group
message.

5 2013-03-19T00:02:53.000 The temporary group message sending time


is Match 19, 2013, 00:02:53.

6 WWTJBz The temporary group message (in base64


+d9ZGcl8N0exTj5kpZHquyJzpL format).
EfJ1rbNQBzhKFYH/
Gwpcn9gIN03ePjaUwpz/
sMgAAYMe8PUiV1aSJGWT
+2NxHAJtrWhb84nuXqRx6BNV
DHAku4H1Wyc84D2mvEsY9H8
0Kau4Pk
+GZGEMpCDe0gvFFIgdfwkMX
Fb1 gsgW2yrq
+XkxxktMszgxVhcREdIQ5i0pQ
gy7k4KMKaeylpKM/
0oraYkcv5bQdPXDQSF/Sl2/
Mi8m7MPXl6Fd4vF9lvFpmPTP
WJNK0Yc3Ltr8sAPiVzZp9pqK
DA+JwRru8uo=

7 sip: Temporary group ID.


22522513622115001@chatas.hua
wei.com

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 33


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 3 CDR on the PGM

No. Value Description

8 sip: Routing number of the temporary group's


3867023@nj13219225.huawei.co moderator.
m

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 34


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

4 CDR on the eSpace Meeting

4.1 Overview

4.1.1 Basic Concepts


This section describes the basic concepts and terms relevant to CDRs.

CDR
A call detail record (CDR) refers to the information about a charging event collected in a certain
format. The information includes the call start time, call duration, and amount of transferred
data. The information is used for charging and settlement.
The naming rules for the three types of CDR files in the eSpace Meeting system are the same.
The CDR type is specified by a specific field in a CDR.

AS
The application server (AS) is the logical processing center of the eSpace Meeting system and
the module for generating CDRs.

CDR File Name Prefix


The CDR file name prefix identifies the type of charging event in the CDR file. For example,
the prefix cdr_econf indicates the CDR files of the eSpace Meeting system

Storage Path of Generated CDRs


The storage path of generated CDRs is the path for storing CDR files.

Maximum Size of a CDR File


The maximum size of a CDR file is 512 KB by default. The maximum number of records in a
CDR file is 1000 by default. The two parameters are configurable.

Storage Duration of a CDR File


By default, the storage duration of a CDR file is 30 minutes. This parameter is configurable.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 35


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

4.1.2 Mechanism for Processing CDRs

Components Related to CDR Processing


Figure 4-1shows the modules involved in CDR processing.

Figure 4-1 CDR processing

The function of each module is described as follows:

l AS: The AS generates a CDR based on conference information and stores the CDR in a
designated directory.
l Charging system: The charging system obtains the CDR from the AS and performs charging
based on the content of the CDR.
l Pre-statistics: The CDR is parsed and the data is stored in the database to generate a report.

CDR Processing Flow


This section describes the progresses of generating and transferring CDRs, and also illustrates
the management functions including how to query and obtain a CDR.

Generating CDRs
l When a user quits a conference and the conference ends, the system generates a conference
CDR and a user CDR.
l When a user cancels a scheduled conference, the system generates a CDR for canceling a
scheduled conference.
l When a user schedules a conference, the system generates a CDR for scheduling a
conference.
l When a user modifies the scheduled conference, the system generates a CDR for modifying
a scheduled conference.

Configuration Items
Bill File Path: indicates the CDR storage path.

Bill File Size: indicates the maximum size of a CDR file.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 36


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Processing CDRs
The CDRs initially generated by the system are stored in the temp folder in the path specified
by Bill File PathWhen the size of the CDR file reaches the value of Bill File Size,the system
moves the CDR file to the upper-level directory, that is, to the path specified by Bill File Path

4.1.3 CDR Classification


CDRs of the eSpace Meeting system can be classified into the following types:
l Conference CDR
l User CDR
l CDR for canceling a scheduled conference
l CDRs for modifying a scheduled conference
l CDRs for scheduling a conference

4.1.4 Types of CDRs Generated in Service Application Scenarios


Conference CDRs
When a conference ends, the system generates a conference CDR.

User CDRs
When a user quits a conference, the system generates a user CDR, which records the time when
the user joins the conference and the duration in which the user stays in the conference.

CDR for Canceling a Scheduled Conference


A conference is scheduled in the system. A user cancels the scheduled conference before the
conference starts. In this case, the system generates a CDR for canceling a scheduled conference.

CDR for Creating a Scheduled Conference


When a user creates a conference, the system generates a CDR no matter the creation is
successful or failed.

CDR for Modifying a Scheduled Conference


A user can modify the information about a scheduled conference before it starts. In this case,
the system generates a CDR for modifying a scheduled conference.

4.2 General Description of CDR Format

4.2.1 CDR File Name Format


The name of a CDR file is as follows:
VF_TYYYYMMDDxxx.100
Table 4-1describes the fields in a CDR file name.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 37


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Table 4-1 Fields in a CDR file name

Field Description

VF_T Prefix of a CDR file name which indicates the CDR of the eSpace
Meeting system.

YYYYMMDD Year, month and day when a CDR is generated.

xxx Serial number, ranging from 001 to 999. The serial number
continues to increase from 001. The serial number returns to 001
only after reaching the maximum value 999, and then return 001.

100 Extension of a CDR file name.

4.2.2 CDR Format Specifications

Types of CDR Fields


This section describes the types of fields in a CDR. The types of fields are explained according
to the definitions of data types in the JDK. Table 4-2describes the types of CDR fields.

Table 4-2 Types of CDR fields

Field Type Description

Integer Integer.

Smallint Small integer. The number of bits of a small integer is half of that of
an integer.

Char Character.

Time Format
Table 4-3describes the specifications on time format in a CDR.

Table 4-3 Specifications on time format

Time Format Example

Year YYYY 2010

Month MM 02

Day DD 25

Hour hh 11

Minute mm 42

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 38


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Time Format Example

second ss 23

4.3 Detailed Description of CDR Format

4.3.1 Overview

CDR File Name Format


VF_TYYYYMMDDxxx.100

CDR Save Path


The CDR save path in the eSpace Meeting system is configurable. The configuration item in
Bill Charging Config is Bill File Path. The CDRs initially generated by the system are stored
in the temp_cdr folder in the path specified by Bill File Path, and are moved to the path specified
by Bill File Path after the CDRs are processed.
The following is an example of querying for the storage path of CDRs.
1. Log in to the eSpace EMS as the admin user.

2. Choose Resource > Resource Management > SNE > SLEE_404041. Click . The
SLEE_404041 Manage page is displayed.
3. Choose Configuration Management > ECONFAS > hw_IMS_Conference_focus
Device > eSpace Meeting > Bill Charging Config. Set Bill File Path, as shown in Figure
4-2.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 39


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Figure 4-2 Bill File Path

NOTE

The CDR save path can be viewed and modified using the eSpace EMS. The value of Bill File Path must
be an actual path when modified.

4.3.2 CDR Format


Table 4-4describes the fields in a CDR, which are separated by vertical bars (|).

Table 4-4 Format of a conference CDR


No. Field Type Description

1 Rec_Type Char(2) This field is set to 20, indicating that the CDR
is a normal CDR.

2 Servicekey Integer The service key is 290.

3 Conf_ID Char(11) Conference ID, a number consisting of 11


digits. The value of this field is generated by
the Conference server automatically.
NOTE
If the conference is an instant conference created by
the IVR, the conference ID is a number consisting
of 9 digits.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 40


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Field Type Description

4 CDR_Sequence Char(9) CDR sequence number, a number consisting


of 9 digits. The number starts from 000000000
and increases by 1 incrementally. When
reaching the maximum value, the number
starts from 000000000 again.

5 AS_ID Char(3) Different ASs may be connected to a single


charging system. This field identifies the AS
that generates the CDR. Currently, the ASs
generate CDRs by themselves, and this field is
set to null.

6 Subtype Smallint Service type.


l 0: individual
l 1: enterprise ID

7 Corporation_Ac- Char(32) Enterprise account assigned by the Business


count Support System (BSS). If the Subtype field is
set to 0, this field is null.

8 Creator_MSISDN Char(18) Creator number.

9 reserve Char(8) Reserved.

10 Charge_Type Smallint Charging type. The value of this field is set to


0 for the eSpace Meeting system.
l 0: postpaid
l 1: prepaid

11 CDR_Type Char(2) CDR type.


l 01: conference CDR
l 02: user CDR
l 03: CDR for canceling a scheduled
conference
l 04: CDR for creating a scheduled
conference
l 05: CDR for modifying a scheduled
conference

12 Attendee_Number Char(18) Participant number.

13 reserve Char(4) Reserved.

14 CDR_GEN_way Char(4) Source of CDR data.


l 0: memory
l 1: database

15 Conf_Type Smallint Conference type.


l 0: instant conference
l 1: scheduled conference

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 41


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Field Type Description

16 Conf_Create_Way Char(2) Conference creation mode.


l 00: audio IVR
l 02: Web

17 Media_Type Smallint Media type.


l 0: audio
l 1: audio+video
l 2: audio+video+data
l 3: audio+data
l 4: data

18 Audio_Count Integer l In a conference CDR, this field indicates


the number of the audio conference
participants.
l In a CDR for canceling or modifying a
scheduled conference, this field is set to 0.
l In a user CDR, this field is set to 1.

19 Video_Count Integer Number of video channels.


l In a conference CDR, this field indicates
the participant number of the video
conference.
l In a CDR for canceling or modifying a
scheduled conference, this field is set to 0.
l In a user CDR, this field is set to 1.

20 Start_Time Char(14) l In a conference CDR, this field indicates


the time when the conference starts.
l In a user CDR, this field indicates the time
when the user joins the conference.
l In a CDR for canceling a scheduled
conference, this field is null.
l In a CDR for creating or modifying a
scheduled conference, this field is set to the
start time of the scheduled conference.

21 Duration Integer l In a conference CDR, this field indicates


the conference duration.
l In a user CDR, this field indicates the
duration in which the user stays in the
conference.
l In other CDRs (CDRs for canceling,
creating, or modifying scheduled
conferences), this field is set to 0.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 42


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Field Type Description

22 User_CDR_Identifi- Char(2) l In a user CDR, this field is set to 00.


er l In a conference CDR or a CDR for
canceling a scheduled conference, this
field is set to 01.
l In other CDRs (for example, CDRs for
canceling, creating or modifying scheduled
conferences), this field is set to null.
NOTE
The conference duration is in seconds.

23 version_id Char(32) Reserved. Set this field to null.

24 Reserve Char(4) Reserved. Set this field to null.

25 Access code Char(18) l For an individual user, this field is set to a


fixed value, and the value is configurable.
You do not need to enter a value for this
field.
l For an enterprise user, this field is set to the
enterprise access number.

26 Communication_Fee Integer Charging rate of the communication fee. 0 is


the default value.

27 Function_Fee Integer Charging rate of the function fee. 0 is the


default value.

28 Record_fee Char(32) Charging rate of the recording fee. The default


value is 0. 0 is the default value.

29 Call_Type Char(2) Call type.


l 01: conference server outgoing call
l 02: incoming call for an external user to
join the conference by IVR
In a user CDR, this field is set to 01 or 02.
In a conference CDR, or a CDR for canceling,
modifying, or creating a scheduled
conference, this field is set to null.

30 Record_Duration Integer Recording duration.


l In a conference CDR, or a CDR for
modifying or creating a scheduled CDR,
this file is set to 0.
l In a conference CDR or a CDR for
canceling a scheduled conference with
recording, this field is set to the recording
duration; otherwise, this field is set to 0.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 43


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Field Type Description

31 End_Time Char(14) l In a conference CDR, this field indicates


the time when the conference ends.
l In a user CDR, the field indicates the time
when the user exits the conference.
l In a CDR for canceling a scheduled
conference, creating or modifying a
scheduled conference, this field is null.

4.4 Conference CDR


Scenario
In the morning of March 29, 2010, an individual user 13607550052 creates a scheduled
conference on the Portal. The conference starts at 10:08 on March 30, 2010 with conference
duration of 15 minutes. The media type of the conference is audio conference without recording.
There are three participants. When the start time arrives, all the participants normally join the
conference.

CDR
20|290|01000002020|000000019||0||+8613607550052||0|01|+8613607550052||0|1|02|0|3|0|
20100330100800|900|01|||123456789|150|0|0||0|20100330102300|

Interpretation of the Fields in the CDR

Table 4-5 Interpretation of the fields in the conference CDR

No. Value Field Description

1 20 Rec_Type This field is set to 20, indicating


that the CDR is a normal CDR.

2 290 Servicekey The service key is 290.

3 01000002020 Conf_ID Conference ID, a number


consisting of 11 digits. The value
of this field is generated by the
Conference server automatically.

4 000000019 CDR_Sequence CDR sequence number, a number


consisting of 9 digits. The number
starts from 000000000 and
increases by 1 incrementally.
When reaching the maximum
value, the number starts from
000000000 again.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 44


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

5 - AS_ID Different ASs may be connected


to a single charging system. This
field identifies the AS that
generates the CDR. Currently, the
ASs generate CDRs by
themselves and this field is set to
null.

6 0 Subtype Individual.

7 - Corporation_Account Individual user with no enterprise


account.

8 +861360755005 Creator_MSISDN The account of the creator of the


2 conference is 13607550052.

9 - reserve This field is set to null.

10 0 Charge_Type The payment type is postpaid.

11 01 CDR_Type The CDR type is conference


CDR.

12 +861360755005 Attendee_Number The account of the participant is


2 13607550052.

13 - reserve Reserved.

14 0 CDR_GEN_way The CDR data is from the


memory.

15 1 Conf_Type The conference type is scheduled


conference.

16 02 Conf_Create_Way The conference is created through


the Web.

17 0 Media_Type The media type of the conference


is audio.

18 3 Audio_Count The CDR type is conference


CDR, and there is no suspended
participant in the conference. This
field indicates the number of
participants in the conference.
The value 3 indicates that there
are three participants in the
conference.

19 0 Video_Count The number of video channels is


0.

20 2010033010080 Start_Time The conference starts at 10:08:00


0 on March 30, 2010.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 45


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

21 900 Duration The conference duration is 900


seconds.

22 01 User_CDR_Identifier In a conference CDR, this field is


set to 01.

23 - version_id Reserved.

24 - Reserve Reserved.

25 123456789 Access code This field is set to a fixed value for


an individual user, and the value
is configurable.

26 150 Communication_Fee The charging rate of the


communication fee is 150.

27 0 Function_Fee The charging rate of the function


fee is 0.

28 0 Record_fee The charging rate of the recording


fee is 0.

29 - Call_Type Call types are not involved in a


conference CDR.

30 0 Record_Duration The recording duration is 0.

31 2010033010230 End_Time The conference ends at 10:23:00


0 on March 30, 2010.

4.5 User CDR


Scenario
A product manager 13607550052 actively joins a video conference organized by the company
at 14:20 on May 18, 2010 to discuss the reproduction expansion scale of products. The product
manager stays in the conference for 90 minutes and then quits the conference before the
conference ends.

CDR
20|290|01000001327|000004111||0||+8613607550002||0|02|+8613607550002||0|1|02|1|1|4|
20100518142000|5400|00|||123456789|800|0|0|02|0|20100518155000|

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 46


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Interpretation of the Fields in the CDR

Table 4-6 Interpretation of the fields in the user CDR


No. Value Field Description

1 20 Rec_Type This field is set to 20,


indicating that the CDR is a
normal CDR.

2 290 Servicekey The service key is 290.

3 01000001327 Conf_ID Conference ID, a number


consisting of 11 digits.

4 000004111 CDR_Sequence CDR sequence number, a


number consisting of 9
digits.

5 - AS_ID This field is set to null.

6 0 Subtype Individual.

7 - Corporation_Account Individual user with no


enterprise account.

8 +8613607550002 Creator_MSISDN The account of the creator


of the conference is
13607550052.

9 - reserve This field is set to null.

10 0 Charge_Type The payment type is


postpaid.

11 02 CDR_Type The CDR type is user CDR.

12 +8613607550002 Attendee_Number The account of the


participant is 13607550052.

13 - reserve Reserved.

14 0 CDR_GEN_way The CDR data is from the


memory.

15 1 Conf_Type The conference type is


scheduled conference.

16 02 Conf_Create_Way The conference is created


through the Web.

17 1 Media_Type The media type of the


conference is video.

18 1 Audio_Count In a user CDR, this field is


set to 1.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 47


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

19 4 Video_Count The number of video


channels is 4.

20 20100518142000 Start_Time The user joins the


conference at 14:20:00 on
May 18, 2010.

21 5400 Duration The conference duration is


5400 seconds.

22 00 User_CDR_Identifier In a user CDR, this field is


set to 00.

23 - version_id Reserved.

24 - Reserve Reserved.

25 123456789 Access code This field is set to a fixed


value for an individual user,
and the value is
configurable.

26 800 Communication_Fee The charging rate of the


communication fee is 150.

27 0 Function_Fee The charging rate of the


function fee is 0.

28 0 Record_fee The charging rate of the


recording fee is 0.

29 02 Call_Type The user actively joins the


conference.

30 0 Record_Duration The recording duration is 0.

31 20100518155000 End_Time The user exits the


conference at 15:50:00 on
May 18, 2010.

4.6 CDR for Canceling a Scheduled Conference


Scenario
A team needs to convene an audio conference to discuss work issues. The conference will start
in two hours. Due to time pressure, the organizer 13607550052 creates a scheduled conference
on the Portal. After the conference time is announced, however, the feedback shows that most
of the team members are not able to attend the conference. As a result, the organizer
13607550052 cancels the scheduled conference.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 48


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

CDR
20|290|01000002026|000000027||0||+8613607550052||0|03|+8613607550052||0|1|02|0|0|0||0|
01|||123456789|0|20|0||0||

Interpretation of the Fields in the CDR

Table 4-7 Interpretation of the fields in the CDR for canceling a scheduled conference
No. Value Field Description

1 20 Rec_Type This field is set to 20, indicating


that the CDR is a normal CDR.

2 290 Servicekey The service key is 290.

3 01000002026 Conf_ID Conference ID, a number


consisting of 11 digits.

4 000000027 CDR_Sequence CDR sequence number, a number


consisting of 9 digits.

5 - AS_ID This field is set to null.

6 0 Subtype Individual.

7 - Corporation_Account Individual user with no enterprise


account.

8 +86136075500 Creator_MSISDN The account of the creator of the


52 conference is 13607550052.

9 - reserve This field is set to null.

10 0 Charge_Type The payment type is postpaid.

11 03 CDR_Type The CDR type is CDR for


canceling a scheduled conference.

12 +86136075500 Attendee_Number The account of the participant is


52 13607550052.

13 - reserve Reserved.

14 0 CDR_GEN_way The CDR data is from the


memory.

15 1 Conf_Type The conference type is scheduled


conference.

16 02 Conf_Create_Way The conference is created through


the Web.

17 0 Media_Type The media type of the conference


is audio.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 49


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

18 0 Audio_Count In a CDR for canceling a


scheduled conference, if one or
more participants are suspended,
this field is set to 0.

19 0 Video_Count The number of video channels is


0.

20 - Start_Time The scheduled conference that is


canceled has not started.

21 0 Duration The conference has not started,


and the conference duration is 0.

22 01 User_CDR_Identifier In a CDR for canceling a


scheduled conference, this field is
set to 01.

23 - version_id Reserved.

24 - Reserve Reserved.

25 123456789 Access code This field is set to a fixed value for


an individual user, and the value is
configurable.

26 0 Communication_Fee The charging rate of the


communication fee is 0.

27 20 Function_Fee The charging rate of the function


fee is 20.

28 0 Record_fee The charging rate of the recording


fee is 0.

29 - Call_Type Call types are not involved in a


CDR for canceling a scheduled
conference.

30 0 Record_Duration The recording duration is 0.

31 - End_Time The scheduled conference that is


canceled has not started, this field
is null.

4.7 CDR for Creating a Scheduled Conference


Scenario
In the morning on January 2, 2011, user 13607550052 creates a scheduled conference on the
Portal. The start time of the conference is set to 12:00 on January 3. The conference is a video
conference that has five participants, and does not support recording.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 50


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

CDR
20|290|00000000165|000000556||0||+8613607550052||0|04|+8613607550052||0|1|02|1|0|0|
20110103120000|0||||123456789|0|20|0||0||

Interpretation of the Fields in the CDR

Table 4-8 Interpretation of the fields in the CDR for creating a scheduled conference

No. Value Field Description

1 20 Rec_Type This field is set to 20, indicating


that the CDR is a normal CDR.

2 290 Servicekey The service key is 290.

3 00000000165 Conf_ID Conference ID, a number


consisting of 11 digits.

4 000000556 CDR_Sequence CDR sequence number, a number


consisting of 9 digits.

5 - AS_ID This field is set to null.

6 0 Subtype Individual.

7 - Corporation_Account Individual user with no enterprise


account.

8 +86136075500 Creator_MSISDN The account of the creator of the


52 conference is 13607550052.

9 - reserve This field is set to null.

10 0 Charge_Type The payment type is postpaid.

11 04 CDR_Type The CDR type is CDR for creating


a scheduled conference.

12 +86136075500 Attendee_Number The account of the participant is


52 13607550052.

13 - reserve Reserved.

14 0 CDR_GEN_way The CDR data is from the


memory.

15 1 Conf_Type The conference type is scheduled


conference.

16 02 Conf_Create_Way The conference is created through


the Web.

17 1 Media_Type The media type of the conference


is video.

18 0 Audio_Count The scheduled conference is not


started.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 51


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

19 0 Video_Count The scheduled conference is not


started.

20 201101031200 Start_Time The scheduled conference starts at


00 12:00 on January 3, 2011.

21 0 Duration The conference has not started,


and the conference duration is 0.

22 - User_CDR_Identifier In a CDR for creating a scheduled


conference, this field is null.

23 - version_id Reserved.

24 - Reserve Reserved.

25 123456789 Access code This field is set to a fixed value for


an individual user, and the value is
configurable.

26 0 Communication_Fee The charging rate of the


communication fee is 0.

27 20 Function_Fee The charging rate of the function


fee is 20.

28 0 Record_fee The charging rate of the recording


fee is 0.

29 - Call_Type Call types are not involved in a


CDR for creating a scheduled
conference.

30 0 Record_Duration The recording duration is 0.

31 - End_Time The conference has not started,


and this field is null.

4.8 CDR for Modifying a Scheduled Conference


Scenario
A group needs to hold an audio conference to discuss works. User 13607550052 creates a
scheduled conference on the Portal. The start time is at 14:00 on January 1, 2011. However, the
conference cannot be held on time. The conference start time is postponed to 16:00.

CDR
20|290|01000002026|000000027||0||+8613607550052||0|05|+8613607550052||0|1|02|0|0|0|
20110103160000|0||||123456789|0|20|0||0||

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 52


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

Interpretation of the Fields in the CDR

Table 4-9 Interpretation of the fields in the CDR for modifying a scheduled conference

No. Value Field Description

1 20 Rec_Type This field is set to 20, indicating


that the CDR is a normal CDR.

2 290 Servicekey The service key is 290.

3 01000002026 Conf_ID Conference ID, a number


consisting of 11 digits.

4 000000027 CDR_Sequence CDR sequence number, a number


consisting of 9 digits.

5 - AS_ID This field is set to null.

6 0 Subtype Individual.

7 - Corporation_Account Individual user with no enterprise


account.

8 +86136075500 Creator_MSISDN The account of the creator of the


52 conference is 13607550052.

9 - reserve This field is set to null.

10 0 Charge_Type The payment type is postpaid.

11 05 CDR_Type The CDR type is CDR for


modifying a scheduled
conference.

12 +86136075500 Attendee_Number The account of the participant is


52 13607550052.

13 - reserve Reserved.

14 0 CDR_GEN_way The CDR data is from the


memory.

15 1 Conf_Type The conference type is scheduled


conference.

16 02 Conf_Create_Way The conference is created through


the Web.

17 0 Media_Type The media type of the conference


is audio.

18 0 Audio_Count In a CDR for modifying a


scheduled conference, this field is
set to 0.

19 0 Video_Count The number of video channels is


0.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 53


Copyright © Huawei Technologies Co., Ltd.
eSpace UC
CDR Reference 4 CDR on the eSpace Meeting

No. Value Field Description

20 201101031600 Start_Time The start time of scheduled


00 conference.

21 0 Duration The conference has not started,


and the conference duration is 0.

22 - User_CDR_Identifier In a CDR for modifying a


scheduled conference, this field is
set to null.

23 - version_id Reserved.

24 - Reserve Reserved.

25 123456789 Access code This field is set to a fixed value for


an individual user, and the value is
configurable.

26 0 Communication_Fee The charging rate of the


communication fee is 0.

27 20 Function_Fee The charging rate of the function


fee is 20.

28 0 Record_fee The charging rate of the recording


fee is 0.

29 - Call_Type Call types are not involved in a


CDR for modifying a scheduled
conference.

30 0 Record_Duration The recording duration is 0.

31 - End_Time In a CDR for modifying a


scheduled conference, this field is
set to null.

Issue 5 (2013-04-28) Huawei Proprietary and Confidential 54


Copyright © Huawei Technologies Co., Ltd.

Вам также может понравиться