Caveats in Oracle Communications Interactive Session Recorder 6.3

Oracle Linux

In Oracle Linux version 7.4, the default SELinux and FirewallD versions have stricter policies that impact application file handling and communications from the Linux host. The impact is very disruptive to ISR, with RSS internal API, FACE, and Archival unable to initialize with their configurations in the database and unable to write to their expected log files. Also, Recorder and converter processes cannot initialize as well, since the internal API cannot return their configurations. While the incompatibilities are expected to be addressed in a subsequent Oracle Linux release, Oracle recommends the following two workaround options:
- Permissive access to the Tomcat process—Execute the semanage permissive -a tomcat_t command.
  
  Note:
  Permissive access to the Tomcat process requires that you have an additional package installed on the system (i.e., yum install policycoreutils-python).
- Downgrade certain SELinux components—Execute the following command:
```
$ sudo yum downgrade selinux-policy-3.13.1-102.0.3.el7_3.16 selinux-policytargeted-3.13.1-102.0.3.el7_3.16 firewalld-0.4.3.2-8.1.el7_3.2 pythonfirewall-0.4.3.2-8.1.el7_3.2 firewalld-filesystem-0.4.3.2-8.1.el7_3.2 firewallconfig-0.4.3.2-8.1.el7_3.2 
```
The Oracle Linux firewalld services, enabled by default on all ISR component hosts, have demonstrated a performance impact (of as much as 25%), using Oracle hardware. When considering the balance of security vs. performance, see the Oracle Communications Interactive Session Controller Security guide for more information on the configuration options of firewalld services and their benefits.
RTP IO port initialization fails in performance load testing when there is a port conflict between the RTP port and the Linux Ephemeral port, which is used by Archiver/API for DB connection. As a result, RSS fails to record calls on the conflicted port. The Recorder process maintains a port pool to listen to RTP and this RTP port range depends upon configured session capacity.
The formula to calculate RTP port pool range is as follows:
```
RTP start port -> {RTP start port + (Number of sessions * max number ports per session)}
```
For each channel (session) the Recorder process requires 8 ports (2 Audio, 2 Video; these must be on even numbers). The RTP Start port default value is 11000. For example, if Channel capacity is configured as 2500, then the RTP port pool range will be as follows:
```
11,000 -> {11,000 + (2500*8)} => 11,000 → 31,000
```
The Linux default ephemeral port range is 32768 - 60999 (this can be found at /proc/sys/net/ipv4/ip_local_port_range).
This issue will occur only if session capacity is configured over 2500 for a single site. If configured session capacity is more than 2500, there will be port conflict between RTP and Linux ephemeral port.

To avoid conflict, first calculate the RTP port range using the formula above and then change the Linux ephemeral range value accordingly.
Workaround:
1. Login as root and use a text editor to open /etc/sysctl.conf.
2. Add or change the following:
```
net.ipv4.ip_local_port_range = <start_Port>  <End_port>
```
  Replace <start_Port> and <End_port> with the required values.
3. Restart the network using the following command:
```
# /etc/rc.d/init.d/network restart
```
4. Verify that your changes are present using the following command:
```
cat /proc/sys/net/ipv4/ip_local_port_range
```

ISR Dashboard

The Dashboard fails to load in certain scenarios with an error message that complains of too many redirects. The following is an example message in the Chrome browser:

This page isn't working
<Dashboard host name> redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS

An example message in the Firefox browser:

The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for
this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to
accept cookies.

To resolve the problem, clear the browser's cookies.

In certain scenarios with the Chrome browser, when the Allow HTTP Cache of Recording files? Dashboard configuration property set to True, the scroll bar still does not function properly for scrolling forward or back during recording playback.
A certificate handling conflict exists with the ISR Dashboard web server that occasionally leads to latency and perceived unresponsiveness when clicking links and submit buttons. The request is properly transmitted, and the response ultimately does arrive, but much later than the expected time frames of previous versions of the Dashboard.
The current Oracle JavaScript Extension Toolkit (OJET) release does not support aria labels for tables. As a result, the JAWS tool does not detect aria labels.
Upon implementation of OJET, when a browser is zoomed out to less than 100%, the Show Columns drop-down checkboxes are not visible.

ISR Archival

When multiple Archival hops are configured for a single Archival instance (i.e., Account Archival plus RSS Primary to Secondary Locations), a thread conflict may occur that leads to unresponsiveness from the Archival process.
The Source Location's Advanced Configuration settings control the Archival decisions during the "hop", (i.e. the move of the recording from the Source to Destination Location).
If the Archival cron schedule has been set to any other value than the default two minutes ("0 0/2 * ? * *"), this setting will be lost and the schedule reverted to 2 minutes. For more information on changing the Archival schedule, contact your Oracle representative.
Deletion and renaming of historical recordings that have been archived may fail due to changes in Archival Location directory paths, SFTP servers, or client user permissions.

ISR Index

Oracle recommends you configure the ISR Index component time zone to be set to UTC. To do this, upon installation the configIsr.sh script prompts the user for permission to configure the system time zone to UTC. You can configure all other ISR components' time zone as needed.
To add ISR users from the primary Index to the Secondary Index, you must execute replication configuration for mysql database in /etc/my.cnf file in single site implementations. In double site implementations, in /configIsr.sh script, ensure you give all users the same password.

ISR RSS

You can only have one MySQL user password across all RSSs for each RSS user type. For example, if multiple RSSs are configured to use the same 'israpi' MySQL user name, the password must be the same for every RSS.

Web Browsers

ISR recording playback errors have been reported for the following web browsers:

Firefox-Firefox is not supporting playback of the 8-bit/8 kHz audio format set in the "Default Recording Format Profile" for the g711 transmission codec (historically the most popular transmission codec). Most commonly, the Dashboard's playback controls appear only briefly before becoming unavailable. To work around this issue, for routes using the "Default Recording Format Profile", change the setting to the Firefox Supported Recording Format Profile, where the g711 transmission codec is converted to the PCM 16- bit/16 kHz recording format.
Internet Explorer—You must use the Windows Media Player plugin to play recorded wave files via Internet Explorer. Without the plugin, an "Invalid Source" error appears in the player popup. This browser support issue impacts ObserveIT Screen Recording integrations with ISR, where the Chrome or Firefox browsers must be used for playback instead of Internet Explorer.
Chrome—Displays some inconsistent behavior with playback of long recordings in internal tests, where the browser stops playback prematurely Playback in another browser rectifies the problem.
Video and screen capture slide playback may display recording length as NaN. Close the playback window and repeat playback.
Subsequent video playback only plays audio. Close the playback window and repeat playback.
Screen capture slide playback progress bar may not move or move accurately. Close the playback window and repeat playback.

Note:
Playback failures may also occur with the Quicktime plug-in version 7.7.7. If you encounter these issues, downgrade to version Quicktime 7.7.4.

General

The Segmentation feature, when enabled, may cause corruption to video recording. Oracle recommends disabling this feature for recording video.
In a commitment to the more flexible design of Custom Data Fields, FACE and Dashboard no longer present the following specific fields in recording segment details:
- agent ID
- agent terminal
- categories
- completed
- hours
- notes
- rating
- transcriptions
Double-check network settings to ensure that interfaces are enabled at boot, (ONBOOT=yes). For example, /etc/sysconfig/network-scripts/ifcfg-XXXX.
To use NFS shares to backup ISR configurations and data, you must meet the following prerequisites:
- Configured ISR host (with networking access to NFS share on the remote host)
- NFS share with no_root_squash option and writable by root user on the client
To store ISR configuration and data backups on a remote host via NFS:
1. Set up and export the remote share. For more information, see the Oracle Communications Interactive Session Recorder Installation Guide.
2. Configure and test the client on the ISR host.
3. Ensure that the "isradm" user (or other configured non-root user) can connect, read, and write files from the share.
4. Backup ISR configuration and data files using the b menu option in the configIsr.sh file and use the local path to the remote share to the location to store configuration and data backups.
5. Verify the contents of the data and configuration backups using the tar tzf /backup/path/<isr_component>-data.tgz or tar tzf /backup/path/<isr_conponent>-configs.tgz commands (replacing <isr_component> with the specific component data and backup filenames).
After upgrading FACE, existing tokens become invalid and you must login again to proceed.