Академический Документы
Профессиональный Документы
Культура Документы
V200R001C02SPC500
CDR Reference
Issue 5
Date 2013-04-28
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.
Website: http://enterprise.huawei.com
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
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.
Contents
1 UC CDR Description
CDR Introduction
Unified communications (UC) CDR records call information including numbers of the calling
party and the called party, call duration, and call type.
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.
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.
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
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.
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.
Typical example:
UCSOC.20130517173956.001.00000.dat
Parameter Description
Node ID Node ID
2 Flag An 3 Flag.
integer.
16: three-way
calling.
17: hunting
group.
18:follow me
19: linked call
20: emergency
call
99: malicious call
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.
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.
28 Error Char - -
reason
code
Parameter Description
Parameter Description
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.
Value Description
Value Description
1 Node ID.
2 3 Flag.
23 0 A non-specific number.
32 Null
33 Null
34 Null
35 Null
36 Null
37 Null
38 Null -
39 Null -
40 Null -
41 Null -
42 Null -
43 Null -
1 Node ID.
3.1 Overview
The procedure for querying CDR configuration items in the eSpace EMS is as follows:
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.
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.
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).
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.
History CDRs 10
MO CDRs 11
MT CDRs 12
Alert_SC CDRs 13
System_SC CDRs 15
Notify_SM CDRs 16
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.
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 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.
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.
4.1 Overview
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.
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.
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.
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
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.
Field Description
VF_T Prefix of a CDR file name which indicates the CDR of the eSpace
Meeting system.
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.
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.
Month MM 02
Day DD 25
Hour hh 11
Minute mm 42
second ss 23
4.3.1 Overview
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.
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.
1 Rec_Type Char(2) This field is set to 20, indicating that the CDR
is a normal CDR.
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|
6 0 Subtype Individual.
13 - reserve Reserved.
23 - version_id Reserved.
24 - Reserve Reserved.
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|
6 0 Subtype Individual.
13 - reserve Reserved.
23 - version_id Reserved.
24 - Reserve Reserved.
CDR
20|290|01000002026|000000027||0||+8613607550052||0|03|+8613607550052||0|1|02|0|0|0||0|
01|||123456789|0|20|0||0||
Table 4-7 Interpretation of the fields in the CDR for canceling a scheduled conference
No. Value Field Description
6 0 Subtype Individual.
13 - reserve Reserved.
23 - version_id Reserved.
24 - Reserve Reserved.
CDR
20|290|00000000165|000000556||0||+8613607550052||0|04|+8613607550052||0|1|02|1|0|0|
20110103120000|0||||123456789|0|20|0||0||
Table 4-8 Interpretation of the fields in the CDR for creating a scheduled conference
6 0 Subtype Individual.
13 - reserve Reserved.
23 - version_id Reserved.
24 - Reserve Reserved.
CDR
20|290|01000002026|000000027||0||+8613607550052||0|05|+8613607550052||0|1|02|0|0|0|
20110103160000|0||||123456789|0|20|0||0||
Table 4-9 Interpretation of the fields in the CDR for modifying a scheduled conference
6 0 Subtype Individual.
13 - reserve Reserved.
23 - version_id Reserved.
24 - Reserve Reserved.