Skip to end of metadata
Go to start of metadata

This section provides information on configuring the IP Trade trading solution for recording. For the latest configuration guides and options, please contact IP Trade directly.

For the supported turrets and versions, see BT IP Trade

TSS 9.3 and later

Recording server configuration

Step 1       Login to the web-based “TSS Console” administration interface.

Step 2       Navigate to the Device Management \Recording servers menu.

Step 3       Add a new recording server with Add new

Configure the recording server according to the following table:

ItemExample valueDescription
TitleHU-BUDLAB-MRDescriptive name of the recording server
Recorder BrandVerbaType of the recorder
Primary URIvrc://10.110.77.129:8000

vrc://<IP address>:port number

Secondary URIvrc://10.110.77.128:8000vrc://<IP address>:port number
Recorder mixing modelMixedThe recording mixing mode used

Turret-based recording configuration

Step 1       Login to the web-based “TSS Console” administration interface.

Step 2       Make sure TPO-based recording is not enabled. 

Step 3       Navigate to Device Management -> Zones -> System (or custom zone)

Step 4       Go to the General tab then select the previously created recording server (select disabled to turn off turret based recording)

Step 5       Click on the Update button to save the changes.

Step 6       Select Turret Boot Settings tab, select the Expert mode Tab within, and select Recorder settings.

Step 7      Set the Recorder keep alive timeout (default recommended value is 1300)  

Step 8      Set the following options to True:

      • Recorder keep alive
      • Send device type information
      • Recorder parse displayname in UTF8
      • Recorder wait DDI master callID

Separated recorder mode

Recording channels should not be set for separated mode, any defined channels should be removed

Mixed recorder mode

If mixed recording mode is used for turret based recording, it is necessary to set Recording channels.

Step 1       Navigate to Device Management -> Zones -> System (or custom zone)

Step 2       Go to the Turret boot settings tab then select the Recorder settings.

Step 3       Go to the Basic Mode tab and define the Recording channel devices (Hints are provided by the right side in the  icon)

Step 4       Select the Expert mode Tab, and set Send multi calls information to true.

TPO-based recording configuration

Step 1       Login to the web-based “TSS Console” administration interface. 

Step 2       Make sure Turret based recording is not enabled.

Step 3      Navigate to the Device Management \ TPO Clusters menu.

Step 4       Go to the General tab then select the previously created recording server (select disabled to turn off TPO based recording)

Step 5       Click on the Update button to save the changes.

Step 6       Select Turret Boot Settings tab, select the Expert mode Tab within, and select Recorder settings.

Step 7      Set the Recorder keep alive timeout (default recommended value is 1300)

Step 8      Set the following options to True:

      • Recorder keep alive
      • Send login in call information
      • Send multi calls information
      • Talkstate in call information
      • Use TPO name/DNS name as Device Id and User Id for recording

Step 9       Click on the Update button to save the changes.

The TPO should be added as a recorded extension in Verba, the Type of the extension has to be set to User/Agent ID, and the description should be TPO. This extension can be assigned to a technical user, or left unassigned.

Retention of TPO recordings

The media records from the TPO cannot be deleted as long as CDR records from users are referencing it. If Data retention is utilized, this means that the media records are implicitly under the longest retention. It is recommended to set this retention explicitly if Automatically Delete Conversations after the Retention Period is Over is used in the Upload policy.
In this case the best practice is to assign the TPO extensions to a technical user, and set the highest retention period for this technical user.

Configuring Redundancy

Step 1        In the Recording server configuration two recording servers should be provided

Step 2       After Step 4 in the TPO or Turret based recording configuration select Boot Settings

Step 3       Move to the Expert mode Tab, and select Recorder settings.

Step 4       Select the Redundancy dual stream mode setting. Set to true for 2N or false for N+1 recording mode.

Step 5       Click on the Update button to save the changes. 

 

TSS 9.2 and earlier

System-wide configuration

Step 1       Login to the web-based “TSS Console” administration interface.

Step 2       Navigate to Device Management -> Zones -> System (or custom zone) -> Turret Boot Settings (Tab)

Step 3       Go to Recorder (on Left Button/Tabs) and on the Basic (Tab) check Recorder compatibility to “iptrade”.

Step 4       Move to the Expert (Tab) still under the Recorder settings and Enable Keep-Alive on all recorded turrets.

Step 5       Move to the Advanced Mode (Tab), and add the following key:

         profile.setting.disablerecorder = false

 

Turret-based recording configuration

Step 1       Create a Shared Profile which will be attached to all of the recorded turrets (if there is an existing shared profile for recording it can be used for these settings but make sure it is assigned to all of the recorded turrets).

 

Step 2       In the Shared Profile (created above) apply the following settings:

 

Step 3       Select the Settings (Tab) and then the Recorder (Button/Tab on left) and go to Basic Mode (Tab) and set the Recording server address. (vrc://192.168.5.69:8000)

Step 4       Set Recording Mixing mode to separated.

Step 5       Set at least 1 or both Handsets to record. (There is additional help provided on the right side in the  icon)

Step 6       Click on the Update button to save the changes.

TPO-based recording configuration

Step 1       Login to the web-based TSS administration interface.

Step 2       Navigate to the Device Management \ TPOs menu.

Step 3       Select the TPO from the list.

Step 4       Go to the Boot Settings tab (Basic Mode).

Step 5       Set the Recorder compatibility setting to iptrade.

Step 6       Provide the Verba Recording Server(s) in the Recorder Server setting in vrc://server_name:port format.

Step 7       Click on the Update button to save the changes.

The TPO should be added as a recorded extension in Verba, the Type of the extension has to be set to User/Agent ID. This extension should not be assigned to a user.

Configuring Redundancy

       Step 1       Login In Step 7 of Turret-based recording or Step 6 of TPO-based recording, two recording servers should be provided:

Step 2       Move to the Expert mode (Tab) still under the Recorder settings and select the Redundancy dual stream mode setting. Set to true for 2N or false for N+1 recording mode.

Step 3       Click on the Update button to save the changes.

Playback on turret

The Verba Recording System does not require a separate IP Trade ReplayBox component to provide playback-on-turret functionality. The Agent needs the User permission Play Conversation in Verba for the playback functionality.

 

If the recording server is not co-located with the media repository, the playback will not work if the configured storage target is Media Repository Local Disk.

 Step 1      Set Authorize Replay to true.

 

Step 2       Set the ReplayBox URL to http://192.168.5.69:8000 (Verba recorder IP)

Step 3       To see the Replay panel on the turrets, go to the shared profile's for all turrets and go to the Screen Layout tab and from there go to the Access Button Configuration and add the Recorder button to the menu.

 

Step 4       In Device Management -> Zones -> System (or custom zone), select the Turret Boot Settings (Tab) and then the Advanced Mode (Tab)

 

Step 5       Add the following key:

         application.global.replay.mode = TCP

 

Step 6       Make sure to reboot all recorded turrets after the configuration changes.

 

 

Recorder configuration

Keep alive configuration

Parameter reference

Please make sure you follow the Location field (FTP or Shared Profile) in this table. If not properly followed, recording and/or playback-on-turret will not work.
Configuration Name and Key

Location

ValueDescription

Recorder compatibility

application.recorder.compatibility

FTPiptrade

Defines which type of recorder is in use.

For Verba Recording System it has to be the default value: iptrade.

Recorder server

profile.setting.activerecording

Shared Profilevrc://192.168.2.1:8000

Recorder Server URI for active recording.

Format: vrc://recorder_address:port

For redundancy, add the second recorder after ";" Example: vrc://192.168.2.1:8000;vrc://192.168.2.2:8001

The port number is configured in the Verba Recording System, see IP Trade Recorder settings.

Recording mixing mode

profile.setting.recording.mixingmode

Shared Profileseparated

Indicates the mixing mode:

  • separated: each call is recorded separately by recorder channel at the same time. We use one recorder channel per call.
  • mixed: calls can be recorded on the same recorder channel at the same time. One recorder channel can be used for several calls at the same time.

Default recording channel

profile.setting.recording.default.channel

Shared Profile0All devices which are not configured to be recorded on a particular channel are recorded on the default channel set using this key No effect if mixing mode is not "mixed".

Recording channel 0..9 devices

profile.setting.recording.channel.0..9.devices

Shared Profile Devices recorded on channel 0 (mixing mode only). Multiple devices may be listed separated by ';' character. For advanced GUI editions, applet may be referenced in this key.

Authorize replay

profile.setting.authorizereplay

Shared ProfiletrueDefines if recorder replay is authorized on the turret.

ReplayBox URL

profile.setting.replaybox.url

Shared Profilehttp://192.168.2.1:8000

Defines the URL path to the ReplayBox module for recording replay features.

Format: http://recorder_address:port

The port number is configured in the Verba Recording System, see IP Trade Recorder settings.

If you have multi-server deployment, where you have a separated Media Repository, you have to point the replay URL to a server where the Verba Unified Call Recorder Service is running.

Replay mode

application.global.replay.mode

FTPTCPDefines the replay mode.

Disable recorder

profile.setting.disablerecorder

Shared ProfilefalseSpecifies if the recorder button is disabled on the screen. If true, the user is not able to access the recorder panel.

Recorder icon blink count

profile.setting.recorderblinkingcount

Shared Profile10Defines the number of times the recorder icon has to blink (red) when the recorder connection fails.

 

 

  • No labels