Definitions of CDR and Recording Index Files

1

developer

String (1–64)

ID of a developer.

2

account_id

String (1–64)

Enterprise account.

3

cc_id

String (1–64)

ID of a call center.

4

agent_id

String (1–32)

Agent ID.

5

call_id

String (1–25)

Call ID.

6

caller_no

String (1–25)

Calling number.

7

callee_no

String (1–25)

Called number.

8

call_begin

Date

Start time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

9

call_end

Date

End time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

10

file_name

String (1–255)

Name of a recording file, for example, /10/1/record/100/13533/0903379.wav.

11

task_status

String (1–20)

Indicates whether to convert a recording file to a text file. The options are 1 (yes) and 0 (no).

12

task_result

String (1–20)

Whether a recording file is successfully converted into a text file. The options are success and failed.

13

original_file_name

String (1–129)

Path to the original recording file. Example: X:\17\0\20180903\15470\2043295.V3

14

vdn_id

String (1–64)

ID of the VDN that processes a call.

15

call_type

String (1–64)

Call type. For details, see Description of Call Types.

16

media_type

String (1–64)

Media type. For details, see Media Type.

17

user_wanted_skill_id

String (1–64)

Direction skill.

18

current_skill_id

String (1–64)

ID of the skill queue that processes a call.

1

developer

String (1–64)

ID of a developer.

2

account_id

String (1–64)

Enterprise account.

3

cc_id

String (1–64)

ID of a call center.

4

agent_id

String (1–32)

Agent ID.

5

call_id

String (1–25)

Call ID.

6

caller_no

String (1-26)

Calling number.

7

callee_no

String (1-26)

Called number.

8

wait_begin

Date

Waiting start time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

9

wait_end

Date

Waiting end time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

10

ack_begin

Date

Response start time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

11

ack_end

Date

Response end time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

12

call_begin

Date

Call start time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

13

call_end

Date

Call end time.

The time format is YYYY-MM-DD hh:mm:ss, for example, 2015-02-08 20:23:30.

14

device_type

Integer (1–4)

Device type.

The options are 1 (skill queue), 2 (agent), and 3 (IVR flow).

15

device_no

Integer (1–5)

Device number.

If the device type is skill queue, the device number is the skill queue ID.

If the device type is agent, the device number is the agent ID.

If the device type is IVR, the device ID is the IVR flow ID.

16

call_type

Integer (1–4)

Call type. For details, see Description of Call Types.

17

release_cause

Integer (1–5)

Call release cause. For details, see Cause Code.

For the bill in which the value of CallIDNUM is -1 (refer to item 18 in this table), this field indicates the call release reason. In other cases, this field is meaningless.

18

call_id_num

Integer (1–4)

Sequence number of a call ID.

If there is only one call ID, that is, the call ID is unique, the sequence number is -1.

If there are multiple records with the same call ID, the sequence number of the last record is -1, and those of other records are numbered in sequence. For example, if four records have the same call ID, and the values of callidnum are 1, 2, 3, and -1.

19

vdn_id

String (1–32)

ID of the VDN that processes a call.

20

pre_device_type

String (1–32)

Type of the previous device that a call passes through. The options are 1 (skill queue), 2 (agent), and 3 (IVR).

21

pre_device_no

String (1–32)

ID of the previous device that a call passes through.

22

skill_id

String (1–32)

ID of the skill queue to which a call belongs. When a call is transferred because the skill queue to which the call belongs overflows or no agent is on duty, the value is the ID of the first skill queue that the call enters.

23

current_skill_id

String (1–32)

ID of the skill queue that processes a call.

24

device_in

String (1–32)

Description of the current device.

• For a skill queue, the value is DEVICE_QUEUE.
• For an agent, the value is DEVICE_AGENT.
• When the value of DeviceType is IVR process (3), the value is the IVR flow access code.
• For a call, the value is a phone number.
• For a temporary routing device, the value is DEVICE_ROUTE.
• For a virtual device, the value is DEVICE_VNR.
• When the value of DeviceType is CDN device (10), the value is the CDN number.
• When the value of DeviceType is PGR (14), the value is the PGR access code.

25

pre_device_in

String (1–32)

Description of the previous device. The values are as follows:

• For a skill queue, the value is DEVICE_QUEUE.
• For an agent, the value is DEVICE_AGENT.
• When the value of DeviceType is IVR process (3), the value is the IVR flow access code.
• For a call, the value is a phone number.
• For a temporary routing device, the value is DEVICE_ROUTE.
• For a virtual device, the value is DEVICE_VNR.
• When the value of DeviceType is CDN device (10), the value is the CDN number.
• When the value of DeviceType is PGR (14), the value is the PGR access code.

26

service_no

String (1–32)

Business type. Type of the business currently provided by a device.

27

leave_reason

String (1–32)

Reason why a call is disconnected from a device. For details, see Reasons for Leaving the Device of the Call.

28

media_type

String (1–32)

Media type of a call. For details, see Description of Call Media Types.

29

sub_media_type

String (1–32)

Submedia type. For details, see Table 1.

This parameter is valid only when media_type (call media type) is set to MEDIA_TYPE_WEB_LEAVE_MESSAGE (20).