Call detail record fields reference

The following table defines all fields in the Section table. Additional business data can be added to the CDR, see Metadata columns on conversation listsSearching by metadata and markers and Metadata designer.

Field nameFormatDescription 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:

  • 0 Normal
  • 1 Source Disconnected
  • 2 Destination Disconnected
  • 3 Hold
  • 4 Transfer
  • 5 Cancelled
  • 6 Busy
  • 7 Not Found
  • 8 Error
  • 13 Conference
  • 14 Call park
  • 15 Join
  • 28 Direct Transfer
  • 60 Line change
  • 80 Timeout
  • 81 Forced termination
  • 82 Manual termination
  • 83 Program termination
  • 84 Video escalation
  • 500 Undefined

Audio_Codec_ID

Integer (4)

Identifies the codec type that used to transmit media. The following valid values descriptions apply:

  • 1 Non standard Codec
  • 2 G.711 A-Law 64K
  • 3 G.711 A-Law 56K
  • 4 G.711 -Law 64K
  • 5 G.711 -Law 56K
  • 6 G.722 64K
  • 7 G.722 56K
  • 8 G.722 48K
  • 9 G.723.1
  • 10 G.728
  • 11 G.729
  • 12 G.729AnnexA
  • 13 Is11172AudioCap
  • 14 Is13818AudioCap
  • 15 G.729AnnexB
  • 16 G.729 Annex AwAnnexB
  • 18 GSM Full Rate
  • 19 GSM Half Rate
  • 20 GSM Enhanced Full Rate
  • 25 Wideband 256K
  • 32 Data 64k
  • 33 Data 56k
  • 80 GSM
  • 81 ActiveVoice
  • 82 G726_32K
  • 83 G726_24K
  • 84 G726_16K
  • 90 iLBC 20ms
  • 91 iLBC 30ms

Video_Codec_Id

Integer (4)

Identifies the codec type that used to transmit media. The following valid values descriptions apply:

  • 200 H.261
  • 201 H.263
  • 202 H.263+
  • 203 H.263++
  • 204 H.264 AVC
  • 205 H.264 DCDO
  • 206 H.264 SVC
  • 300 TechSmith
  • 301 Windows Media 8 768 Kbps
  • 302 Windows Media 8 1024 Kbps
  • 303 Windows Media 8 1512 Kbps
  • 304 Windows Media 8 2048 Kbps
  • 305 Windows Media 9 768 Kbps
  • 306 Windows Media 9 1024 Kbps
  • 307 Windows Media 9 1512 Kbps
  • 308 Windows Media 9 2048 Kbps
  • 309 Windows Media Screen 768 Kbps
  • 310 Windows Media Screen 1024 Kbps
  • 311 Windows Media Screen 1512 Kbps
  • 312 Windows Media Screen 2048 Kb
  • 313 Verba Screen Codec Lossless
  • 314 Verba Screen Codec High Quality
  • 315 Verba Screen Codec Low Quality
  • 316 Verba Screen Codec Black and White

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:

  • 0 internal
  • 1 incoming
  • 2 outgoing
  • 3 inter tenant
  • 4 undefined
  • 5 dictation
  • 6 external

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_statusBit(1)

This field identifies whether a call is archived or not.

  • In the section table this value will always be 0 or NULL.
  • In the section_archived table this value will always be 1.

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:

  • 0 the call has to be dropped
  • 1 the call has to be kept

Conference

Bit (1)

This field identifies if a call was a conference. The following valid values descriptions apply:

  • 0 not conference call
  • 1 conference call

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:

  • 0 not transferred call
  • 1 transferred call

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.

ondemandBit(1) This field identifies if a call was an Ondemand recording. The following valid values descriptions apply:
  • 0 not Ondemand recorded call
  • 1 Ondemand recorded call
Native_IDVarchar (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_triggerBit(1)

Means that the record was moved from the ongoing table to this section table by a trigger. The following valid values descriptions apply:

  • 0 the record wasn't moved to this table by a trigger
  • 1 the record was moved to this table by a trigger
Recorder_Service_IDInteger (4)

Identifies the recording service, which recorded the call. The following valid values descriptions apply:

  • 1 Verba Passive Recorder Service
  • 2 Verba Central Cisco Recorder Service
  • 3 Verba Dial-in Recorder Service
  • 4 Verba IP Trade Recorder Service
  • 6 Verba Avaya Recorder Service
  • 7 Verba Lync Recorder Service
  • 8 Verba Central Cisco Silent Monitoring Service
Signaling_IDInteger (4)

Identifies the signalling/technology used for the call. The following valid values descriptions apply:

  • 1 Cisco Skinny
  • 2 SIP
  • 3 H.323
  • 4 JTAPI
  • 5 UniStim
  • 6 Analog
  • 7 ISDN Trunk
  • 8 Generic ISDN/Digital Extension
agent_id

NVarchar(64)

The contact center Agent ID of the recorded agent.
location_eidChar(4)To which tenant the recorder server belongs to (this is very rarely used).
platform_call_idNVarchar(127)Call id provided by the hosting PBX.
silence_percentDecimal(3,0)The rate of the silence in the recording (percent).
talkover_percentDecimal(3,0)The rate of the talkover periods in the recording (percent).
longest_silence_lengthDecimal(10,0)How long is the longest silence period.
meeting_idVarchar(64)Lync / Skype for Business Meeting ID.
recording_id

Varchar(64)

Identifier of the recorded call leg.
manualInteger(4)

In case of controlled recording, this field differentiates the technical records (what the user can use to start/stop recording)

  • 0 (or NULL): not a controlled recording
  • 1: a recording that was created using the controlled method
  • 9: a technical record that the user can use to start/stop the real recording
media_delete_dateDatetime(8)When the media file has been deleted.
exists_related_callBit(1)

Identifies whether the call has any related call. The following valid values descriptions apply:

  • 0 related call doesn't exist
  • 1 related call exists

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_CountInteger (4)Number of audio RTP packets recorded for the called party. This information is only inserted by certain recording services.
Encryption_IDInteger (4)Identifies the encryption key used to encrypt the media.
Signature_IDInteger (4)Identifies the signature key used to sign the media.
do_not_deleteNumeric(1,0)

Stores the protected flag

  • 0 (or NULL): not protected
  • 1: protected
  • -1: this recording should be deleted
secondaryBit(1) Identifies whether the call is a secondary recording. The following valid values descriptions apply:
  • 0 related call doesn't exist
  • 1 related call exists
source_device_idNVarchar(100)MAC address or other physical identifier of the caller party.
destination_device_idNVarchar(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:

  • 0 the caller was the recorded party
  • 1 the called was the recorded party
  • NULL unknown
notifiedBit(1)

Identifies wheter Verba has sent a notification e-mail about the recorded call. The following valid values descriptions apply:

  • 0 notification e-mail hasn't been sent out
  • 1 notification e-mail has been sent out
storage_folder_idInteger(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_startDatetime(8)Means when was the file moved to it's current place.
retention_untilDatetime(8)Means until what datetime we don't allow the deletion of this file.
retention_auto_deleteBit(1)

Means wheteher we will auto delete the file when the retention_until datetime arrives. The following valid values descriptions apply:

  • 0 we won't delete the file when retention_until datetime arrives
  • 1 we will delete the file when retention_until datetime arrives
record_failedBit(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_errorInteger(4)

 Identifies the media error. The following valid values descriptions apply:

  • 1 there was no media
  • 2 length mismatch
  • 4 packet loss
  • 8 packet duplicated
  • 16 srtp error
  • 32 decoding error
  • 64 mixing error
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.