Oreka TR 1.2 Administrator Manual

Here are the steps to install OrkAudio using installers on Linux, mainly CentOS and RedHat. Other Linux systems may require RPM files. Refer to the section called “Installing under RPM-based Linux Distributions” for more details.

Requirements

Installation

Upgrade

Upgrading OrkAudio on Linux requires applying RPM files. The RPM archive comes either as a single file named e.g. orkaudio-1.2-660-x1459-linux-i386-RPMs.tar, or as 3 separate .rpm files. Assuming the former, here is the procedure to upgrade:

            # service orkaudio stop
          

             # rpm -e orkaudio-addons
             # rpm -e orkaudio
             # rpm -e orkbasecxx
             # rpm -i orkbasecxx-1.2-660.i386.centos5.rpm
             # rpm -i orkaudio-1.2-660.i386.centos5.rpm
             # rpm -i --nodeps orkaudio-addons-1.2-1459.i386.centos5.rpm
          

            # service orkaudio start    
          

Requirements

Installation

Use the installer file provided to you by OrecX, e.g. orkaudio-1.2-657-x1463-win32-installer.zip. Copy this file to a temporary folder on the target machine, unzip it and run the embedded executable. This will install WinPcap as well as OrkAudio.

Audio output files are written to the c:\oreka\audio under Windows and in /var/log/orkaudiounder Linux by default. This can be changed using the <AudioOutputPath> configuration parameter described in the section called “Configuration”. In typical installations, <AudioOutputPath> needs to be tuned according to the section called “Cannot replay recordings” so that replay from the orkweb user interface is allowed.

Audio files are classified according to the following default scheme (see also TapeFileNaming and TapePathNaming in the section called “Configuration”):

yyyy/MM/dd/hh

Audio file themselves are named after the following scheme:

yyyyMMdd_hhmmss_capturePort.extension

OrkAudio configuration files are located in the install directory under Windows and in /etc/oreka under Linux. The files are:

Log files are located in the install directory under Windows and in /var/log/oreka under Linux. By default, Oreka produces the following output:

Plugins exist as dll files under Windows and as DSO (Dynamic Shared Objects) with .so extensions under Linux. They are located in {OrkAudioInstallDirectory}/audiocaptureplugins under Windows and in /usr/lib under Linux.

Wire audio encodings are detected automatically by OrkAudio. Audio is not usually stored in its original wire format. Audio is recorded in real time to mcf files in order to maximize capturing performance and is later transcoded to the final storage format as specified in the section called “Storage audio formats”. The following encodings are supported:

Configuration of OrkAudio and its plugins is performed by modifying the config.xml file (see also the section called “Configuration Files”). Core OrkAudio configuring parameters are the following:

It is possible to configure the path to which audio files are written as well as the audio file names as a combination of the following dynamic parameters:

VoIP plugin specific configuration is found in the config.xml file under the VoIpPlugin tag. Many options are available for this plugin, such as limiting traffic, blocking traffic from/to a specific IP address, ... The default config.xml has some of the main options listed in it and commented out. Please consult that file or contact <support@orecx.com> for more details.

As an example, it is possible to configure the network device to monitor for VoIP traffic using the <Devices> directive. While OrkAudio attempts to automatically select the server interface on which it detects VoIP traffic, you may in some cases need to configure the interface manually. E.g.

In Windows:

<Devices>\Device\NPF_{E0E496FA-DABF-47C1-97C2-DD914DFD3354}</Devices>

In Linux:

<Devices>eth2</Devices>

Several comma-separated interfaces may be configured in the examples above

For Live Monitoring from OrkWeb to work, the 59120 port must be accessible on the server where OrkAudio is running. In Linux check the iptables settings. in Windows, the firewall settings.

Under Windows, start the OrkAudio service in Service Management (start/run/services.msc).

Under Linux, start the OrkAudio service by typing service orkaudio start on the command line.

You might need to double-check that the orkaudio service was started correctly.

In Linux, use the following command:

# ps -ef | grep orkaudio

A line showing that orkaudio is running must appear:

root     32071     1  0 10:02 ?        00:00:00 /usr/sbin/orkaudio

In Windows' Service Management tool (start/run/services.msc), ensure that the orkaudio service is started

During installation using the official installers, OrkAudio will install itself as an automatic service, i.e. a service that restarts automatically if the server is rebooted. This is important in the case of power failure, maintenance or other unpredictable events that may cause the system to fail or be restarted. Ensure that the service is configured properly as follows:

# orkaudio        0:off   1:off   2:on    3:on    4:on    5:on    6:off

If not, chkconfig orkaudio on will need to be executed.

If no recordings appear in the <AudioOutputPath> directory, Here is the checklist:

Recoded wav files should all be replayable by a media player such as Windows Media Player. Here is the checklist

Make sure that RTP traffic for both sides is actually seen on the considered network interface. A packet sniffer such as Ethereal can be used for that.

Use wireshark to see if signalling packets (e.g. SIP or Skinny) can be seen on your chosen sniffing NIC. Simply capture some traffic for 1 minute and type "sip" or "skinny" as a wireshark display filter in order to see only the relevant packets. If resultset is empty, it might mean that the packet interception strategy is missing some traffic, see the section called “Getting VoIP traffic to the Oreka Server”.

OrkWeb/OrkTrack need the following software:

The OrkWeb installer can install Java JRE and Apache Tomcat, it has them as options. However, MySQL needs to be installed separately and prior to running the installer.

Here are the steps to install OrkWeb on Linux (mainly CentOS, RHEL, Fedora, OpenSuse). For assitance with other Linux distributions, contact <support@orecx.com>.

To upgrade using .war files use the procedure below. The version of the .war file made available to you by OrecX may differ from the example below, but the procedure still applies.

Note that there are two types of license files: trial and production. The trial type is sent to you by OrecX as a first license and allows you to record everything on the wire. It is good to start with this type of license to uncover any configuration tweaks that may be necessary.

For example, you may be seeing only the RTP streams but not the control packets, thus no phone number or extensions can be associated to calls. With a trial license, you will be able to quickly detect such a situation and correct it since all calls would be recorded and would appear in the OrkWeb Browse page with the local and remote party typically showing as IP addresses.

With a production license, users must be configured in OrkWeb with their phone numbers or extensions (or other) as a login string, for Oreka to be able to associate the local party in the VoIP packets with the configured user and thus recording the call. If no users have been configured in OrkWeb, a production license will inhibit all recording. See also the section called “Login Strings”

Before migrating to a production license, make sure all extensions, phone numbers, SIP URIs, ... that need to be recorded, are configured as login strings for defined users in OrkWeb. The login string field must match what you see in the local party field in the Browse page.

OrkWeb and OrkTrack have a set of configuration files that allow them to know where and how to access the database, and what information to write to log files. The main configuration files are shared between OrkWeb and OrkTrack and can be found under /etc/orkweb in Linux, and typically under C:\Program Files\OrkWeb in Windows. These folders contain 3 main files:

Both the OrkWeb-OrkTrack applications, and the Tomcat web server have their own logging mechanisms. Below are the files of interest for both cases:

You can use ps -ef | grep mysqld to verify if mysqld is running, and service mysqld start to start it if it is not.

Once the MySQL is running, start the Apache Tomcat web server, e.g. service tomcat start.

Go to Start/Run... and type services.msc. This opens the Services Manager application. Ensure that the MySQL service is running. If not, start it.

Once the MySQL service is running, start the Apache Tomcat web server, by right-clicking on the Apache Tomcat service and selecting Start.

Each user can have multiple login strings entered as a cvs list of text strings. Those login strings serve two purposes:

When a new call occurs, if the local party field, as would be seen in the OrkWeb Browse page, matches one of the user's login strings, the recording will be associated to that user. The login string matching is case sensitive.

For example, Tom's login strings might be "tom, 5312". Any call to extension 5312 will be associated to Tom, and Tom will be able to log into OrkWeb using either "tom" or "5312" as an identifier (assuming Tom has a password defined. OrkWeb login is denied for users with blank passwords).

Configuration of users and login strings is very important for correct behavior when using production licenses. Refer to the section called “Trial versus Production license”

When you have a great number of users to define in OrkWeb, it could be a daunting task to create them all, one at a time, from the Admin/users page. In this case, you can use the Import Users feature available on that page. This feature allows you to import a comma-separate list of users directly into OrkWeb. Below are the fields that define the file format:

firstname, lastname, login string, password, recordable, force password change

Only the firstname and lastname fields are mandatory. The rest can be left blank if not required. Also, only one login string can be entered on one line. The "recordable" and "force password change" fields can be set to "false"/"true", "0"/"1" or "no"/"yes". The "force password change" field, if set, forces the corresponding user to change their password the next time they login. This is mainly useful when defining new users.

There are two other global settings that can be configured when importing users: "Keep old login strings" and "Recordable". "Keep old login strings" allows you to select whether a user in the csv list that already exists in OrkWeb should have their login string(s) replaced by the login string in the imported file, or whether the new login string is to be simply added to that user's existing login string(s).

When you click on the "view" link next to a group in the Admin/groups page, a "Managed Access Policies" button appears. Clicking on it displays the Access Policies definition page. You can create your own secuity groups and give them the access policies that you wish.

Users or groups of users associated to a particular Security Group inherit that group's access policies.

Below are the instructions for how to configure Oreka to delete all media files in the system and their database info, if they are older than 180 days (approximately 6 months):

The "Stop Auto-Delete" button provides a quick mean for turning off this feature. It resets the "Delete files in filesystem" and "Delete entries in database" to Disabled, and "Wake-up period" to 0.

For deletion of remote files, a ssh server needs to be running on the remote server. Also, the corresponding service must be configured with the ssh parameters in OrkWeb, in the Config/services page.

It is recommended to delete both files and database info with this feature. Deleting only database info leaves orphaned recordings that are neither easily accessible nor identifiable, while deleting files only and leaving the corresponding data in the database means that the Auto-Delete feature will unnecessarily re-attempt to remove already deleted files every time it wakes up.

It is possible to configure the media files path and filename as a combination of the following dynamic parameters:

The following foreign languages are currently included in OrkWeb:

For other languages, please contact <support@orecx.com>.

The selection of the OrkWeb language usually occurs automatically by default, and depends on your Operating System language. For example, if you are running the Spanish version of Windows, OrkWeb will appear in Spanish by default.

If you would like to change the displayed language, you would have to use the Language Options in your Browser as described below:

In Internet Explorer:

In FireFox:

Most likely, the database server is down or there is something wrong in the database URL and credentials in the database.hbm.xml configuration file.

If you fail to replay recordings through OrkWeb, here is the checklist:

You need to add at least one login string for the user. Users can log into OrkWeb using any of the login strings they own. For more details, please refer to the section called “Login Strings”

Make sure the end date in the multi-criteria search form is not in the past.