Call detail record fields reference
- Kiss, Mate
The following table defines all fields in the Section table. Additional business data can be added to the CDR, see Metadata columns on conversation lists and Metadata designer.
| Field name | Format | Description and Values |
|---|---|---|
CCDR_ID | Char (36) | Unique identifier of the call. In certain cases, complex calls appears as single call records in the database, but detailed information is available about the different call legs in a separated database table, called section_participant. This table is only used by certain recording engines. |
Location | Varchar (40) | Hostname of the Recording Server, which inserted/recorded the call. |
Cause_ID | Integer (4) | Reflects the reason for the clearance of the call. The following valid values descriptions apply:
|
Audio_Codec_ID | Integer (4) | Identifies the codec type that used to transmit media. The following valid values descriptions apply:
|
Video_Codec_Id | Integer (4) | Identifies the codec type that used to transmit media. The following valid values descriptions apply:
|
Direction_ID | Integer (4) | Identifies the direction of the call (calls going through a gateway are treated as incoming or outgoing). The following valid values descriptions apply:
|
FileFormat_ID | Integer (4) | Identifies the current file format. |
Source_IP | Varchar (16) | Identifies the IP address of the caller party. For IP Phones, this field specifies the address of the IP Phone. For PSTN calls, this field specifies the address of the gateway. |
Source_Caller_ID | Varchar (64) | For calls originating at an IP Phone, this field shows the extension number of the line that is used. For incoming calls this field specifies the value received in the Calling Party Number field in the SETUP message. This field reflects the translations applied to the Calling Party Number before it arrives at the IP PBX (such as translations at the gateway). |
Source_Name | Varchar (64) | This field shows the name of the caller party if it is available in the signaling messages. |
Destination_IP | Varchar (16) | Identifies the IP address of the called party. For IP Phones, this field specifies the address of the IP Phone. For PSTN calls, this field specifies the address of the gateway. |
Destination_Caller_ID | Varchar (64) | This field specifies the number to which the call was placed. If translation rules are configured on the IP PBX, this number reflects the called number after the translations have been applied. |
Destination_Name | Varchar (64) | This field shows the name of the called party if it is available in the signaling messages. |
Start_Time | Datetime (8) | Start date and time of the call in UTC timezone. |
End_Time | Datetime (8) | Termination date and time of the call in UTC timezone.. |
Url | Char (256) | Media file path. |
| Archive_status | Bit(1) | This field identifies whether a call is archived or not.
|
Keep | Bit (1) | If on-demand recording is set to an extension, users can decide to record a call or not. The following valid values descriptions apply:
|
Conference | Bit (1) | This field identifies if a call was a conference. The following valid values descriptions apply:
|
Transmitted | Bit (1) | This field identifies if a call was a transferred to the Media Repository from a Recording Server. The following valid values descriptions apply:
|
Source_User_ID | Integer (4) | Unique identifier of the user, which was linked to the calling party phone number through phone number mapping. By linking the user table to this field you can display the Verba user properties along with call information. |
Destination_User_ID | Integer (4) | Unique identifier of the user, which was linked to the called party phone number through phone number mapping. By linking the user table to this field you can display the Verba user properties along with call information. |
| ondemand | Bit(1) | This field identifies if a call was an Ondemand recording. The following valid values descriptions apply:
|
| Native_ID | Varchar (256) | Call identifier generated by the recording service. |
| Owner_EID | Char (4) | Identifies which tenant the call belongs to. This field is only used in multi-tenant systems. |
| inserted_by_trigger | Bit(1) | Means that the record was moved from the ongoing table to this section table by a trigger. The following valid values descriptions apply:
|
| Recorder_Service_ID | Integer (4) | Identifies the recording service, which recorded the call. The following valid values descriptions apply:
|
| Signaling_ID | Integer (4) | Identifies the signalling/technology used for the call. The following valid values descriptions apply:
|
| agent_id | NVarchar(64) | The contact center Agent ID of the recorded agent. |
| location_eid | Char(4) | To which tenant the recorder server belongs to (this is very rarely used). |
| platform_call_id | NVarchar(127) | Call id provided by the hosting PBX. |
| silence_percent | Decimal(3,0) | The rate of the silence in the recording (percent). |
| talkover_percent | Decimal(3,0) | The rate of the talkover periods in the recording (percent). |
| longest_silence_length | Decimal(10,0) | How long is the longest silence period. |
| meeting_id | Varchar(64) | Lync / Skype for Business Meeting ID. |
| recording_id | Varchar(64) | Identifier of the recorded call leg. |
| manual | Integer(4) | In case of controlled recording, this field differentiates the technical records (what the user can use to start/stop recording)
|
| media_delete_date | Datetime(8) | When the media file has been deleted. |
| exists_related_call | Bit(1) | Identifies whether the call has any related call. The following valid values descriptions apply:
|
Source_Audio_RTP_Count | Integer (4) | Number of audio RTP packets recorded for the calling party. This information is only inserted by certain recording services. |
| Destination_Audio_RTP_Count | Integer (4) | Number of audio RTP packets recorded for the called party. This information is only inserted by certain recording services. |
| Encryption_ID | Integer (4) | Identifies the encryption key used to encrypt the media. |
| Signature_ID | Integer (4) | Identifies the signature key used to sign the media. |
| do_not_delete | Numeric(1,0) | Stores the protected flag
|
| secondary | Bit(1) | Identifies whether the call is a secondary recording. The following valid values descriptions apply:
|
| source_device_id | NVarchar(100) | MAC address or other physical identifier of the caller party. |
| destination_device_id | NVarchar(100) | MAC address or other physical of the called party. |
| recorded_party | Bit(1) | Identifies wheter the caller or the called party was the recorded. The following valid values descriptions apply:
|
| notified | Bit(1) | Identifies wheter Verba has sent a notification e-mail about the recorded call. The following valid values descriptions apply:
|
| storage_folder_id | Integer(4) | If data retention has moved the file to a storage target then the Storage Target id is set here. Otherwise this value is NULL. |
| retention_start | Datetime(8) | Means when was the file moved to it's current place. |
| retention_until | Datetime(8) | Means until what datetime we don't allow the deletion of this file. |
| retention_auto_delete | Bit(1) | Means wheteher we will auto delete the file when the retention_until datetime arrives. The following valid values descriptions apply:
|
| record_failed | Bit(1) | If this is set to 1 then it means that the Lync CDR Reconsiliation created this record. It happens when we didn't record a call that we should have record indicating a recorder outage/error. Otherwise it's 0 (or NULL). |
| media_error | Integer(4) | Identifies the media error. The following valid values descriptions apply:
|
| media_length | Integer(4) | Stores the length of the call in seconds. |
The Verba system maintains an archived section table for archived calls to reduce searching time. It means that when you access the section table directly, you can access only those calls that are not archived yet. The archived calls are stored in the section_archived table, which is almost identical the original section table. The Verba database also contains a view for accessing both tables from a single query. The name of this view is: v_section.
The system originally stores the call in the section_ongoing table, while the call is being recorded. After the call is finished, the record is moved to the section table. The ongoing calls are stored in the section_ongoing table, which has exactly the same structure as the original section table has.