Introduction to Oracle Communications Interactive Session Recorder 6.4

Hardware

The Interactive Session Recorder (Oracle Communications Interactive Session Recorderi) components are distributed as applications running on Oracle Linux Releases 7.2 - 7.7, which abstracts the ISR application from the physical hardware. As such, ISR can be deployed on any hardware platforms that support Oracle Linux Releases 7.2 - 7.7. For a comprehensive list of the hardware platforms currently certified, see the Oracle Linux and Oracle VM Hardware Certification List (HCL).

ISR testing is predominantly done on Oracle Server X5-2, Oracle Server X6-2, Oracle Server X7, and Oracle Server X8-2 systems with the following resource configurations:

Hardware Description	Quantity
Intel® Xeon® E5-2630 v3 8-core 2.4 GHz processor	2
One 16 GB DDR4-2133 DIMM	8
One 1.2 TB 10000 rpm 2.5-inch SAS-3 HDD with marlin bracket in RAID 10 configuration using 12Gb SAS RAID HBA	4

Note:

RAID must be configured BEFORE performing the ISR component installation.

Each of the ISR components must be installed on their own server/VM instance.

Installation Prerequisites

Before beginning your Interactive Session Recorder (ISR) installation, ensure you have completed the following prerequisites:

Have at least three servers (physical or virtual) with Oracle Linux Releases 7.2 - 7.7 installed.
Have access to the ISR rpms:
- isr-Index-<release#>.x86_64.rpm
- isr-Dashboard-<release#>.x86_64.rpm
- isr-rss-<release#>.x86_64.rpm
- isr-Face-<release#>.x86_64.rpm (optional)
Note:
You may access these files via https://edelivery.oracle.com..
Have access to the Ruby 2.6 rpm (ruby-2.6.4-1.el7.centos.x86_64.rpm). Ruby is the framework the ISR Dashboard uses and must be installed as part of the ISR Dashboard installation.
Configure a Linux User named isradm on each of the Linux instances created in step 1 to allow you to automatically gain access to config and log files. Once you have configured the isradm Linux user, you must add the user to the "sudoers" group.
Verify that the hosts you are installing the ISR components on are connected to the internet.

Note:
If your ISR hosts do not have internet connectivity, see "Oracle Public Yum Repository Configuration and Offline Installation Pre-Requisites in the Installation Guide.
Oracle Linux 7 has the yum package management utility configured by default with access to the "public-yum.oracle.com" repositories in the file located at /etc/yum.repos.d/public-yum-ol7.repo. If, for some reason, this file needs to be created, see the Appendix, "Oracle Public Yum Repository Configuration File" in the Oracle Communications Interactive Session Recorder Installation Guide, which contains the specific repository entries.
Configure interfaces; Oracle Communications Interactive Session Recorderi expects network configuration to include 4 interfaces, connecting to separate Administration, Local, Data, and Voice networks. Refer to the Oracle Communications Interactive Session Recorder Security Guide for more information on networking and trusted boundaries.
For more information on configuring networking in Oracle Linux 7, see the man nmtui guide and http://www.unixarena.com/2015/04/rhel-7-network-management-nmcli-or-nmtui.html.
If access to the external yum repository is gated by a proxy, ensure the proxy parameter in the/etc/yum.conf file is set to:
```
proxy=http://<your_proxy_host>
```

Note:

During the installation process, you will be asked to provide and/or verify the users, passwords and interfaces you created during the Oracle Linux installation. Ensure you have that information before you begin the installation process.

Oracle Communications Interactive Session Recorder Dashboard Requirements

The Oracle Communications Interactive Session Recorderi Dashboard is the web portal used for recording configuration and playback. As web technologies advance, some functionality may not be available on older browser versions. The Oracle Communications Interactive Session Recorderi has been tested with the following web browsers and versions:

Google Chrome (Version 63.0.3239.84 64-bit)
Mozilla Firefox (Version 52.5.2 32-bit)
Microsoft Edge (Version 40.15063.674.0)

Note:
Browser playback support for recording codecs changes frequently. Refer to the Oracle Communications Interactive Session Recorder Release Notes for current details.

Supported Codecs

The Oracle Communications Interactive Session Recorderi supports the following transmission codecs:

g.711 mulaw
g.711 alaw
g.729
g.722 and g.722.2 (excluding g.722.1)
H.264
AMR-WB

The audio transmission codecs can be mapped to the following recording formats:

Header Raw	Header WAVE	Format	Bit Rate	Sample Rate (KHz)	Channels Mono	Channels Stereo
YES	YES	ulaw	8	8	YES	YES
YES	YES	alaw	8	8	YES	YES
YES	YES	Linear PCM	8	8	YES	YES
NO	YES	Linear PCM	16	8	YES	YES
NO	YES	Linear PCM	16	1	YES	NO
NO	YES	Linear PCM	16	16	NO	YES
NO	YES	ADPCM	4	8	YES	YES

H.264 video content is stored and replayed in MP4 format.

Upgrade Prerequisites

To upgrade the Oracle Communications Interactive Session Recorderi components, you must complete the following prerequisites:

The Oracle Communications Interactive Session Recorderi component hosts are properly running on the Oracle Linux Release 7.2 - 7.7 OS
Access to the following upgrade tar files from the Oracle Communications Interactive Session Recorderi component hosts:
- isr-Index-<release#>-upgrade.tgz
- isr-Dashboard-<release#>-upgrade.tgz
- isr-rss-<release#>-upgrade.tgz
- isr-Face-<release#>-upgrade.tgz
Have access to the Ruby 2.6 rpm ( ruby-2.6.4-1.el7.centos.x86_64.rpm).
For the duration of the maintenance window, all call traffic is stopped on all sites and outside client access to the Dashboard and API services is prohibited.

Note:

The following instructions assume the recommended "isradm" Linux user has sudo permissions.

WARNING: The upgrade process for each component includes a critical backup step that copies important host configuration, Oracle Communications Interactive Session Recorderi application configuration, Oracle Communications Interactive Session Recorderi application platform configuration, Oracle Communications Interactive Session Recorderi application data, encrypted keys, keystores, and log files to a temporary directory before consolidating these copies into a compressed set of files for a potential rollback situation. This backup step requires additional disk space to successfully write the files, and a warning prompt is displayed to detail concerns and recommend an option to mount an additional drive if disk space may be an issue. Oracle strongly recommends you consider these details and the recommended option carefully before continuing with the upgrade. For more information about mounting remote storage, see Chapter 22, Shared File System Administration from the Oracle Linux Administrators Guide Release 7.

For more information on upgrading the ISR, see the Installation Guide.

Upgrade Caveats

The following items provide key information about upgrading with this software version.

Upgrading from 5.2 to 6.4

The nokogiri 1.8.4 gem installation failed during ISR 5.2 to 6.4 upgrade using the Dashboard.

Workaround: When the error occurs, run the following commands:

sudo yum install -y gcc ruby-devel libxml2 libxml2-devel libxslt libxslt-devel
bundle config build.nokogiri --use-system-libraries

Then run configIsr.sh to install the remaining gems.

Dashboard Rack Issue

A Dashboard rack issue has been observed during ISR 6.0.5 to 6.4 upgrade.

Workaround: Stop the puma server, using the service puma stop command, before running upgradeIsr.sh. Execute the gem uninstall rack and gem uninstall nio4r commands to uninstall the rack and nio4r gems, then execute the upgradeIsr.sh and configIsr.sh scripts.

Conversion Errors

An upgrade from 5.2 to 6.x likely results in conversion failures until each Location has been updated to properly reflect connections to the Converter using the Data Network. Log into the Dashboard and update each Location in the "Recording Converter" section by setting the "Converter IP Address" field to the Converter's data network IP address. You may confirm the Converter data IP in the "Converter Server Configurations" accordion of the corresponding RSS.