SMTP

Available in version 8.6 and later

This page provides a guide for configuring an SMTP service as a Storage Target in the Verba Recording System.

 SMTP target can be used for e.g. Micro Focus Digital Safe, Global Relay and any other archive that provides email injection capability.Verba offers a generic SMTP Storage Target which is highly customizable to allow companies to export the recorded calls from Verba to their own storage.

For a general description of storage targets, please refer to Storage and export targets.

Currently, there are two preconfigured templates available:

  • HP Digital Safe
  • Global Relay

When using these templates, the emails to these storage targets will be sent in the format that these systems expect.

There is a third SMTP-based storage template implemented in the system for Bloomberg Vault. For the usage of this storage target, refer to the Bloomberg Vault - Instant Messaging article.

Creating an SMTP target

Follow the steps below to create a new Verba Storage target for SMTP:

Step 1 - Open the Verba Web interface then select Policies > Storage Targets from the top menu.

Step 2 - Click on Add New Storage Target

Step 3 - Fill out the configuration form according to the requirements in the following table.

Configuration itemDescription
Storage Target Data
NameName your storage target. This name will identify this target across the system.
TypeSelect SMTP
Email Template (optional)You can load pre-configured templates to the Storage Target Configuration page.
Source Email Address

This is the source e-mail address for the SMTP protocol.

Target Email Address

This is the target e-mail address for the SMTP protocol.

CC Email AddressThis is the CC e-mail address for the SMTP protocol.
TLS EncryptionYou can enable the TLS encryption for the SMTP protocol here.
PortSpecify the SMTP port here.
Login nameEnter the login name of your SMTP user.
PasswordEnter the password for your SMTP user.
Headers
From (Header)This is the from header of the message, the recipient client displays this value.
To (Header)This is the to header of the message, the recipient client displays this value.
CC (Header)This is the CC header of the message, the recipient client displays this value.
(add new header) You can specify your own key-value headers here.
Content
SubjectThis is the subject of your e-mail.
BodyThis is the body content of your e-mail.
Attachments
(add new attachment)

You can add 3 different kind of attachments with the following attributes:

  • Metadata:
    1. Content-Type

  • Media:
    1. Content-Type

  • Text file:
    1. Content-Type
    2. Filename
    3. Content

If you leave the Content-Type field empty the default application/x-msdownload will be used.

Step 4 - Click Save to save the settings

After this point, the Storage target is available for use by other Verba components (e.g. Data management policies).

In the Headers, Content and Attachments input fields you can use the following strings to include call-related metadata information:

Caller Party
[From]Phone number or address of the caller party 
[FromName]The display name of the caller party
[FromIP]The IP address of the caller party 
[FromDeviceID]The device identifier of the caller party 
[FromRTPCount]The RTP packet count of the caller party 
Verba From Party
[FromLoginName]The login ID of the Verba user associated with the caller party 
[FromVerbaName]The display name of the Verba user associated with the caller party 
[FromEmailAddress]The email address of the Verba user associated with the caller party 
[FromUserCustomField0], [FromUserCustomField1], ...The custom user field 0, 1, ... of the Verba user associated with the caller party 
Called Party
[To]Phone number or address of the called party 
[ToName]The display name of the called party 
[ToIP]The IP address of the called party 
[ToDeviceID]The device identifier of the called party 
[ToRTPCount]The RTP packet count of the called party 
Verba To Party
[ToLoginName]The login ID of the Verba user associated with the called party 
[ToVerbaName]The display name of the Verba user associated with the called party 
[ToEmailAddress]The email address of the Verba user associated with the called party 
[ToUserCustomField0], [ToUserCustomField1], ...The custom user field 0, 1, ... of the Verba user associated with the called party 
Conversation IDs
[VerbaConversationID]Verba conversation identifier 
[PlatformConversationID]Conversation identifier provided by the communication platform 
Conference
[Conference] In the case of conference recording, it shows "true" otherwise "false" 
[ConferenceParticipants]A comma-separated list of phone numbers (and e-mail addresses when available), e.g.: "testuser1" <testuser1@verbatest.local>, "testuser2" <testuser2@verbatest.local>, "John Doe", "Jane Doe" 
[NumberOfParticipants]The number of conference participants 
[MeetingID]Meeting identifier provided by the communication platform 
[StartDateTime]The start datetime of the conversation in GMT, e.g.: 2019.05.31 16:56:16.388 
[StartDate]The start date of the conversation in GMT, e.g.: 2019.05.31 
[StartTime]The start time of the conversation in GMT, e.g.: 16:56:16.388 
[EndDateTime]The end datetime of the conversation in GMT, e.g.: 2019.05.31 16:56:46.848
[EndDate]The end date of the conversation in GMT, e.g.: 2019.05.31 
[EndTime]The end time of the conversation in GMT, e.g.: 16:56:46.848 
[Duration]The length of the conversation formatted as: days hours:minutes:seconds 
[DurationInMinutes]The length of the conversation in minutes 
[MediaLength]The length of the recorded media file in seconds 
SMTP Generation
[Year]The current year in GMT 
[Month]The current month in GMT 
[Day]The current day in GMT 
[Hour]The current hour in GMT 
[Minute]The current minute in GMT 
[Second]The current second in GMT 
[DateTime]The current datetime in GMT, e.g.: 2019.05.27 14:26:46.396 
[PolicyName]The name of the export policy 
Conversation Details
[Modality]The display name of the modality, e.g.: Voice, Video, Instant Messaging, Desktop Screen, Screen & Application Share 
[ModalityId]The ID of the modality, e.g.: voice, video, instant_messaging, desktop_screen, screen_and_applicaton_share 
[RecordedParty]The value of [From] or [To] or "Unknown" when unset 
[Direction]The direction of the conversation from the system point of view as text, e.g.: "Internal", "PSTN Incoming", "PSTN Outgoing", "Inter-tenant", "Dictation", "External", "Federated Incoming", "Federated Outgoing", "Contact Center Incoming", "Contact Center Outgoing", "Conference", "Undefined" 
[DirectionUser]The direction of the conversation from the recorded user point of view as text, e.g.: "Inbound", "Outbound" or "Unknown" 
[RecordingServer]The hostname of the recording server 
[EndCause]The conversation end cause as text, e.g.: "Normal", "Caller termination", Callee termination", "Transfer", "Hold", etc. 
[UserID]The User ID obtained from the communication platform 
Errors & Statistics
[RecordingFailed]If the recording failed, it shows "true" otherwise "false" 
[MediaError]The media error as text (it can contain any or none, space character separated list), e.g.: "No media", "Length mismatch", "RTP duplication", "RTP loss", "SRTP decryption", "Decoding error", "Media mixing", "One direction", "Missing file", "Corrupted file" 
[SilenceRatio]Silence to call length ratio in percent, e.g.: 68 
[TalkoverRatio]The length where both participants are talking to call length ratio in percent, e.g.: 32 
[LongestSilence]Longest silence in seconds 
Instant Messaging Transcript
[IMTranscript]Displays the IM transcript with the timezone of the Verba user who created this policy 
[IMTranscript_NoLeaveJoin]Excludes the "Entered Conversation" and "Left Conversation" messages 
[IMTranscript_HTML]Displays the messages using HTML formatting 
[IMTranscript_HTML_NoLeaveJoin]Displays the messages using HTML formatting and excludes the "Entered Conversation" and "Left Conversation" messages 
[NumberOfMessages]The number of recorded IM messages 
Voice Transcription
[Transcription]Voice transcription text 
Metadata Templates
[Meta-TemplateID-ColumnIndex-FriendlyName]The FriendlyName is an optional syntax element and is not used by the service. It is available to make the configuration more human-readable. 

For example: [Meta-14-3-BT_ITS_Line] where the TemplateID=14 is the BT-ITS metadata template, ColumnIndex=3 is the Line field.

Expressions
ISNULL( [value1] , [value2] , [value3] )First not null (empty) value will be chosen 
ISIM( [value] )Text in the phranteses will be only displayed when the attachment is an IM file
ISNOTIM( [value] )Text in the phranteses will be only displayed when the attachment is not an IM file 
ISVOICE( [value] )Text in the phranteses will be only displayed when the attachment is a Voice file 
ISNOTVOICE( [value] )Text in the phranteses will be only displayed when the attachment is not a Voice file 
ISVIDEO( [value] )Text in the phranteses will be only displayed when the attachment is a Video file 
ISNOTVIDEO( [value] )Text in the phranteses will be only displayed when the attachment is not a Video file 
ISDESKTOP( [value] )Text in the phranteses will be only displayed when the attachment is a Desktop Screen file 
ISNOTDESKTOP( [value] )Text in the phranteses will be only displayed when the attachment is not a Desktop Screen file 
ISSHARE( [value] )Text in the phranteses will be only displayed when the attachment is a Screen & Application Share file 
ISNOTSHARE( [value] )Text in the phranteses will be only displayed when the attachment is not a Screen & Application Share file 


If you leave blank fields then Verba will use the following default values:

  • Header From = ISNULL([FromEmailAddress],[From],[FromName],[FromDeviceID],[FromIP],[FromLoginName],[FromUserCustomField0])
  • Header To = ISNULL([ToEmailAddress],[To],[ToName],[ToDeviceID],[ToIP],[ToLoginName],[ToUserCustomField0])
  • Header CC = [ConferenceParticipants]
  • Title = Verba Technologies - Export action (  <policy_name> ) - [VerbaConversationID]