6.3 Call Data Records
Call data record files are created and stored by Conferencing and allow you to track information about each event. The comma-delimited text file records each event, including meeting times and duration, call connection times, and which clients joined the meetings. This information is useful when determining billing.
The call data records are stored in /var/iic/cdr/calls.elg on the host specified in controller_host in the global-config file for the cluster. The file is rotated daily to /var/iic/cdr/calls+<timestamp>.log. After the call data record of one of the rotated files is exported, you can delete it. You might want to place /var/iic/cdr on a network file system to ease exporting call data records. Otherwise, you can fetch the call data records using tools such as ssh/scp.
The database service outputs the following information:
Table 6-2 Database Service Output
|
Record ID |
String: <hostname>-<10-digit sequence number> |
11 + <max host name length> |
|
Time |
String: <YYYY>-<MM>-<DD>-<HH>-<mm>-<SS> |
19 |
|
Duration |
Integer |
10 |
|
Event |
Integer
1 = meeting started
2 = meeting ended
3 = inbound call started
4 = outbound call started
5 = call connected
6 = call ended
7 = IIC client joined meeting
8 = IIC client left meeting
9 = App share started
10 = App share ended
11 = App share viewer connected
12 = App share viewer disconnected
13 = Meeting recording started
14 = Meeting recording stopped |
2 |
|
Event Info |
String:
DNIS (inbound call)Dialed number (outbound call)
User name (IIC client) |
297 + <max host name length> |
|
Community ID |
4-byte non-negative integer |
10 |
|
Meeting ID |
8-byte non-negative integer |
19 |
|
Meeting Start (in seconds) |
4-byte non-negative integer |
10 |
|
Host ID |
4-byte non-negative integer |
10 |
|
Participant ID |
8-byte non-negative integer |
19 |