Table of Contents
WARNING: This guide covers quick setting up of Oreka TR for port mirroring. For any other uses, such as TDM recording or SIPREC recording,
please get in touch with
The main Oreka TR components are listed below:
OrkAudio: this is the audio capture background service. It supports VoIP and TDM based recording.
OrkTrack: this service centrally tracks activity on the entire system and logs recordings to any popular SQL database.
OrkWeb: this service is the web interface accessible via any standard compliant web browser. It relies on the Tomcat web server.
For the sake of simplicity, Oreka TR will be referred to simply as Oreka in the rest of this document.
Table of Contents
Test Server (PC or Laptop)
Oreka TR runs on Linux and Windows platforms.
OrecX's preferred platform is Linux CentOS 6 - 64 bit. All desktop and server versions of Windows are supported, starting from Windows XP and 2003 server.
For support of other operating systems, please inquire at
MySQL is recommended as Orecx LLC's primary database environment. Oreka also supports most major database systems including Oracle, MS-SQL and PostgreSQL.
Before Oreka can start recording, ensure that VoIP traffic is seen on a server interface. Use SPAN monitoring (port mirroring) to get the right traffic to the Oreka server. Two configurations are possible:
This is to ensure that both the media traffic (RTP) and signaling (SIP, Skinny, H.323, UNISTIM, ...) are intercepted by the recorder. Use a packet analyzer such as the free Wireshark tool to verify that both types of packets are appearing on the Oreka server's interface.
Once the VoIP traffic appears on the server, you are ready to start using the Oreka software.
Here is an example port mirroring configuration guide by Cisco: http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008015c612.shtml
Alternative mechanisms to get VoIP traffic
Port mirroring is the recommended packet capture mechanism, but if port mirroring is not an option, Oreka can intercept packets through other mechanisms:
Table of Contents
Here are the steps to install Oreka using installers on Linux, mainly
CentOS and RedHat. Other Linux systems may require RPM files. For more
tar -xvf orkaudio-1.6-819-x2546.i386.centos6-installer.sh.tar.
./orkaudio-1.6-819-x2546.i386.centos6-installer.sh.tar(accept all required components)
Install OrkWeb (includes OrkTrack):
OrkWeb and OrkTrack require a database engine, preferably MySQL, Java and Tomcat. Java and Tomcat are downloaded and installed by the OrkWeb installer provided to you by OrecX. MySQL, on the other hand, needs to be downloaded and installed separately.
yum install mysql-server
service mysqld start
chkconfig mysqld on
tar -xvf orkweb-1.7-2586-linux-installer.sh.tar
The OrkWeb installer will prompt you for the MySQL "root" user password. By default, MySQL is installed with no default password. The installer will then prompt you for the installation of Java and Tomcat. Accept the default directories. It will finally install OrkWeb and OrkTrack under Tomcat.
The installer configures the Tomcat service to be automatically started after a reboot. However, it will not run the Tomcat service at the end of the installation. You will need to start it yourself after you apply the license file, as described in a later section.
Use the installer file provided to you by OrecX,
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.
Install OrkWeb (includes OrkTrack)
OrkWeb and OrkTrack require a database engine, preferably MySQL, Java and Tomcat. Java and Tomcat are included in the OrkWeb installer provided to you by OrecX. However, MySQL needs to be downloaded and installed separately.
Install MySQL: you can download the MySQL Windows Essentials for your platform at http://dev.mysql.com/downloads/mysql/5.6.html#win32. Install it accepting all the defaults. Take note of the "root" password if you assign one. It will be needed when you install OrkWeb.
Install OrkWeb: unzip the OrkWeb installer provided to you
by OrecX, e.g.
Run the embedded executable. This will first install Java, then Tomcat (accept all default options) and finally OrkWeb and OrkTrack.
Make sure to enter the correct MySQL "root" password when installing
OrkWeb. You can always update it later in the
file in the OrkWeb installation folder (
C:\Program Files\OrkWeb) by default.
When installing on multiple servers, the recorder (OrkAudio) runs on a different server than OrkWeb/OrkTrack. Thus, additional configuration is required. Here's a brief summary.
Communication with OrkTrack
The recorder needs to communicate to OrkTrack to report the recording metadata to be stored in the database. Thus, it needs to know where OrkTrack is running.
Make sure the
<TrackerHostname> entry in the
config.xml is properly set to the OrkWeb/OrkTrack
hostname or IP address.
OrkWeb access to media files
For OrkWeb to be able to access the media files stored on the recorder's server, a web server application such as Apache httpd or Apache Tomcat needs to be installed and configured on the recorder's server. For a quick solution, use the OrkWeb installer and install only the Tomcat and Java Run-Time components. E.g., run ./orkweb-1.7-2586-x64-linux-installer.sh --nomysql --nooreka on Linux. In Windows, you can stop the installer after Java and Tomcat are installed.
For more details, contact
When you request a trial setup, OrecX provides you with license files. You need to apply those licenses files to OrkAudio and OrkWeb for Oreka as a whole to run correctly.
Applying the OrkAudio License File
Store the OrkAudio license file (e.g. orkaudio-30-days-trial-license-20131005.txt)
provided to you by OrecX in the folder where OrkAudio was installed, typically
/etc/orkaudio in Linux and
on Windows. Make sure to rename the file to
Warning: under Windows, you need to make sure file extensions are shown (go to My Computer/Explore/Tools/Folder Options/View and uncheck "Hide extensions for known file types"). Otherwise you risk naming the file licence.txt.txt without realizing it.
Whenever a new license file is applied, the orkaudio service must be restarted for the change to take effect.
Applying the OrkWeb License File
To apply the OrkWeb license file, e.g.
copy and paste its content into the Input License box in OrkWeb,
accessible from the login page the first time the software is accessed,
or from the Account page at subsequent tries.
Once Oreka is installed and VoIP traffic is properly detected at one of the interfaces, Oreka is ready to start recording. Ensure that OrkAudio and OrkWeb/OrkTrack (i.e. Tomcat) services are running.
Also, it is very important that VoIP traffic is correctly reaching the Oreka server. If you are unsure whether this is the case, refer to section the section called “Getting VoIP traffic to the Oreka Server” before proceeding.
service orkaudio start".
/var/log/orkaudio/audiodirectory, using a date-based directory hierarchy.
Start/Run..., then type
services.msc. This opens the Services Manager application. Start the service by right-clicking on OrkAudio and choosing Start.
C:\oreka\audio, using a date-based directory hierarchy.
C:\Program Files\OrkAudio. The main file is
service tomcat start").
/opt/tomcat5/conf/logs/catalina.outfile, while OrkWeb and OrkTrack write to
Start/Run... and type services.msc. This opens the Services Manager application. Start Tomcat by right-clicking on the Apache Tomcat service and choosing Start.
C:\Program Files\Apache Software Foundation\Tomcat 7.0\logs\catalina.out. OrkWeb and OrkTrack write their log to
Open any standard web Browser and type the following URL: http://localhost:8080/orkweb. If you are accessing from a location other than the server on which Oreka was installed, replace localhost with the hostname or IP address of the Oreka server.
This will bring up a login screen. Login as admin/admin.
You will be presented with a license input screen. Copy the content of the license text file issued to you by OrecX and paste it into the text box.
Congratulations: you are now ready to start using Oreka!
Table of Contents
Below are the most common questions that arise from the installation
process. If you are still having issues after you consult these tips,
OrkAudio is not recording. No files are
appearing under the
<AudioOutputPath> directory configured
orkaudio.logfile to see if the last re-start, marked by "OrkAudio service starting", shows any license-related ERROR.
OrkAudio does not seem to be recording properly: only .mcf files appear in the audio folders. There are no .wav files.
Ensure that the OrkAudio license file is properly applied and
has not expired. To verify, you can restart the orkaudio service and
check at the bottom of the
orkaudio.log file to see
if the last restart marked by "OrkAudio service starting" shows any license-related ERROR.
See the section called “Starting OrkAudio” for the location of the log files.
Accessing OrkWeb from the Browser does not work.
If all the conditions above are met, you can look into the Tomcat and OrkWeb log files for more information. See the section called “Starting OrkWeb and OrkTrack” for the location of the log files.
Note: if accessing Tomcat returns Error 404, restart the Tomcat service.
OrkWeb is running well, but playing back recordings does not work.
AudioOutputPathentry in the OrkAudio
config.xmlfile matches the corresponding
docBaseentry in Tomcat's server.xml for
path="/audio". If either of these entries need to be modified, restart its corresponding service (OrkAudio or Tomcat).
You can also look into the Tomcat and OrkWeb log files for more information. See the section called “Starting OrkWeb and OrkTrack” for the location of the log files.
Recordings Local and Remote party appear as IP addresses instead of phone numbers or extensions in OrkWeb.
There is no audio when listening to calls in the Live Monitoring page.