Creating Trader data sources

In Recording Management > Data Sources > Settings, click Create Data Source.
In the pop-up Data Source Type page, do the following:
1. From the Type drop-down list box, select Trader.
2. From the Switch/Sub Type list box, select a switch/sub-type.
  
  Your license determines which switches are displayed in the Switch/Sub Type list box.
3. Click Select.
Name - Type a data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. name. This is a required field. Only alphanumeric characters (no quotation marks and no back or forward slashes) are supported in the data source name.
Type a short description.
Select a Time Zone from the drop-down list.

When defining the Trader Data source, you must select the correct time zone.

For UK installations, select Greenwich Mean Time (GMT): Dublin, Edinburgh, Lisbon, London time zone so that the Daylight Savings Time (DST) changes are accounted for. The same time zone should also be used in Enterprise Manager and Recorder Manager Preferences.
Do the following:
1. Enable the Rollback Period (in minutes) to ensure that a recording is kept for a certain amount of time before deletion, so that in the event of a disconnection it is possible to retrieve it. A rollback period is applicable only to Performance Mode (set in the IP Extension Pool member group) and N+N redundancy. The default value is 15; the maximum value is 60.
2. Type a number for Alarm - Device Not Recorded Call Count. This field contains number of calls for a configured device that must fail to record before triggering the DeviceNotRecording alarm. The default is 1 failure.
3. Type a number in milliseconds for Alarm - Device Not Recorded Duration (milliseconds). Failed call durations under this threshold will not count against the Device Not Recording Call Count. The default is 15 seconds.
4. Long Call Duration (minutes)—This setting allows you to specify the length of a call, in minutes, after which the system will trigger an alarm. The system will also stop tracking the call from a CTI perspective, so in CTI-controlled application or performance mode environments this may cause loss of recording. Enter any number between 1 and 1440 (24 hours)—an alarm is raised in the cases In Risk Management, use cases to group interactionss according to the needs of the enterprise. Interactions can reside in multiple cases simultaneously. where calls exceed this number of minutes. The default is 120.
  
  The Integration Service runs maintenance checks every five minutes to close calls that last for more than the length of time specified as the Long Call Duration. An alarm indicates when a call is closed because it was too long.
  
  Since these maintenance checks are not run more frequently in order to avoid imposing an additional load on the system, it may take up to five minutes to close a long call after it has passed the defined Long Call Duration threshold.
5. Long Hold Duration (minutes)—Indicates the maximum duration of a single hold. Any holds over this duration will raise an alarm. Enter any number between 1 and 3000, representing the number of minutes. The default is 30.
6. Recording Resource Allocation Behavior—This setting is for duplicate streaming solutions, which allow you to distribute recordings across multiple recorders.
  To use the CTI-based recorder selection feature available for Shared Interception or Avaya DMCC environments, you must select either LineFirst or LineExclusive.
  
  For details, see the Recorder Configuration and Administration Guide:
  - For Shared inception, see the section “IP Extension Pool Member Group Settings”.
  - For Avaya, see the section “Extension Recording Resource Member Group Settings”.
  - IgnoreLine—Records the next recording on the least-utilized recorder connected to the Integration Service, regardless of data source, member group, and extension list settings.
  - LineFirst—First attempts to record on the least-utilized recorder that contains the extension being recorded in a member group associated with the recorder. If the Integration Service can’t find an associated recorder it will attempt to find any connected recorder with the capacity (whether or not the extension is associated with the recorder). LineFirst provides a way to keep recorders local to the extensions/site. The Integration Service will fail over to another set of recorders if a call can’t be recorded locally. If you don’t want fail over to another set of recorders, use ‘LineExclusive’, described below. This is the default.
  - LineExclusive—First attempts to allocate the recording to the least-utilized recorder that contains the extension being recorded in a member group associated to the recorder. If the Integration Service fails to find a recorder associated with the line to be recorded, it will not record the call. By recording calls on a recorder co-located with the PBX for agents taking calls on a remote site, the use of this setting has the advantage of reduced WAN traffic.
  The “least-utilized” recorder is the one with the most unused capacity. For example, if one recorder has 300 licenses and 50 calls are currently being recorded, and another recorder has with 100 licenses and 10 calls currently being recorded, the capacity left on the recorders are 250 and 90 respectively. The system will attempt to record the next duplicate streamed call on the first recorder.
7. Always Report Extension as Primary Extension—If enabled, the extension field of the session will always be the primary extension on a telephone. If disabled, the extension field will contain the DN/extension that first answered the call. This only affects multiline phones. Enabled by default.
8. Select the Enable Selective Recording check box to activate selective recording.
  
  When the check box is selected, only the recordings of calls on turrets where a specific set of traders is logged in are saved. Other calls will be deleted.
  
  When the check box is not selected, all recorded content on all turrets is kept.
9. Video Recording Mode— Select one of the following options:
  - Start On Trigger - Do not record video calls for the extensions associated with this data source until a recording rule is triggered or an external API command starts recording. Video recording starts whenever the call starts, but video prior to the recording trigger is deleted.
  - Application Controlled - Record every video call for every extension associated with this data source, and then delete it. At any time during a call, a recording rule or an external API command can cause the recorder to keep the video call. If the call is kept, the recording includes all video from the start to the end of the call.
  - Do Not Record - Do not record video calls for extensions associated with this data source. Recording rules are ignored and cannot trigger the recording of video calls.
  - Record - Record all video calls for extensions associated with this data source. Only a block recording rule, AIM command, or external API command can prevent calls from being recorded.
10. Keep Duplicate Recording—
  For an N+N recording environment, select one of the following options:
  - Select the Keep Duplicate Recording option when a customer's compliance recording policies require them to archive duplicate recordings of every call. To support this configuration, you must double the size of the Contact Database Server role in the Data Center that includes long-term interactions. The Contact Database is optimized for searching operations, and interactions are inserted and updated in bulk operations., the Archive Database, and the archive storage media.
  - Clear the Keep Duplicate Recording option (default) so that the system deletes the secondary interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. after determining which copy to keep.
    When N+N recording is configured, the system evaluates the interactions captured by both Recorders. It marks one as primary and the other as secondary based on several criteria, including call quality. For details, refer to Selective Recording Configuration.
    Archive campaigns provide alternative methods for managing recordings in N+N environments. Set the N + N Dual Marking options to turn off the double-archiving of recordings, which keeps a single copy. For details, refer to Campaign conditions.
11. Require Replay Audio Redaction - When redaction is enabled for the system, select whether redaction occurs for interactions that the data source captures. Redaction obscures sensitive customer information in captured audio and transcriptions. Select from the following for interactions that the data source captures:
  - Disabled: No information in the interaction is obscured. Disabled is the default setting.
  - Always: Sensitive customer information is obscured.
  - In Fallback: Sensitive customer information is obscured, but only in the event of CTI or recorder disconnection from the Integration Service.
12. Require Replay Audio Morphing - When morphing is enabled for the system, select whether replay of interactions captured by the data source requires morphing. Morphing changes the voice heard during replay such that the speaker remains anonymous and the audio remains intelligible. Select from the following options for interactions that the data source captures:
  - Disabled: The original voice of the agent and the customer are heard during interaction replay. Disabled is the default setting.
  - Always: The voice of the selected channel or channels is morphed during interaction replay, as configured by the Audio Morphing Channel setting.
  - In Fallback: The voice of the selected channel or channels is morphed during interaction replay, as configured by the Audio Morphing Channel setting, but only in the event of CTI or recorder disconnection from the Integration Service.
13. Audio Morphing Channel - Enabled when Require Replay Audio Morphing is set to Always or In Fallback, choose the audio channel or channels that use morphing. Select from:
  - Agent: Only the voice of the agent channel is morphed during interaction replay. The voice on the customer channel is the original captured voice. Agent is the default setting.
  - Agent and Customer: The voice of the agent channel and the customer channel are morphed during interaction replay.
Under Time Zone Settings, specify a Local Time Tagging Mode. Select one of the following options:

Organization - Select this option to base the time zone tagging on that of the organization. This setting is useful in scenarios where agents are working in different regions. The setting allows you to unify tagging across multiple time zones.
Data Source - Select this option to base time zone tagging on the time zone specified in step 5.

Expand the Associated Integration Service Installations area and select the server for the recorder for which you are configuring this data source.

In a Multi-Tenant SaaS environment, the tenant name associated to each Site Group, Site, and Server appears beside the Site Group, Site, and Server name on the right side of the Installations tree.
Under Advanced Settings, use the Key and Value fields to enter any proprietary pairs that are in use in your system. This should be done only in consultation with our field engineers.
Click Save. The new Trader data source is listed.