
Avaya Contact Recorder is a system for selectively or completely recording conversations.
We will install it under the cut.
If interested, please.
We will need:
')
CD - Avaya Contact Recorder (Linux) from Avaya Aura Workforce Optimization
(earlier this software was called Witness, although nothing changed except for the name)
DVD disc - Red Hat Enterprise Linux Server 5.4
(Please note that you need a version exactly 5.4 rhel-server-5.4-x86_64-dvd.iso)
Openssl097a-0.9.7a-9.el5_2.1.i386.rpm RPM package
(it is this version, if there will be difficulties with its search, then two options
rhel repository
vault.centos.org
Configuration file - ks.cfg
(obtained using the kickstart2.exe utility from Avaya Contact Recorder,
when creating, do not forget to rearrange the radio button on rh5)
Utility for working with iso images - for example, ultraiso.
If interested, please under the cat.
Further from all of the above, you need to collect one image (based on rhel).
Inside put a daddy, for example witness containing
all from Avaya Contact Recorder (Linux) disk
Openssl097a-0.9.7a-9.el5_2.1.i386.rpm RPM package
configuration file - ks.cfg
Received iso write on the disc and ...
The complete Avaya Contact Recorder installation disc is ready!
Next we need
Server (you can use virtual - for example on ESXi)
The image of rhel-5.4-witness.iso collected in the first part is written to disk.
A pair of not very crooked hands
Loading from the assembled disk in the inviting line we write
linux ks=cdrom:/witness/ks.cfg
under the condition that the configuration file you put in the witness folder
then the whole installation will take place automatically, the only thing that you will be asked for is the license key rhel, if you have to enter it, if not, just skip this step.
account will be created in accordance with the configuration file
root with password ContactStore
after installation we login in the witness daddy on the disk and run autorun, if nothing happens, then two options
1st
manually install 3 rpm package
jre-6u20-linux-i586.rpm
cscm-10.1-2.i586.rpm
cs-services-3.0.0-1.noarch.rpm
in that order
If in the process an error related to lib.so.4 comes out, then we also set
openssl097a-0.9.7a-9.el5_2.1.i386.rpm
2nd
climb in the installation instructions
and run autorun from the terminal
cd /media/cdromlabel sh ./autorun
and in the pop-up window click install
after installation we reboot the server and on port 8080 on the server’s ip address it becomes available to us
Avaya Contact Recorder web interface
Password at the first call
root / ContactStore
The system will immediately ask him to change, use her wise advice.
We put AES without which Contact Recorder will not be able to interact with the CM and accordingly fulfill its role.
We will need:
Avaya Aura Application Enablement Services Drive
Avaya Aura System Platform Disk
Server (a virtual server on ESXi, for example, is also suitable, with installation on a virtual machine there are nuances, after all, a hypervisor on the hypervisor, so for an amateur)
First we install the Avaya Aura System Platform, when installing nothing unusual is asked.
There is a bug / feature - after the first launch, the web-based management interface is not available.
The treatment is simple - reboot.
It may also be necessary to enable / disable ip forwarding, this is done from under the administrator account
admin / admin01 (if not changed during installation)
ip_forwarding enable ip_forwarding disable
It is still useful to log in as root and check the status of XEN.
root / root01
xm list
must be active domain-0 and udom
Next, we go to the web-interface under the administrator account admin / admin01 (if not changed during the installation process)
Virtual Machine Management -> Solution Template -> Install Template From - then select the source in our case dvd disk - SP CD / DVD - search
Select the found template - aes r6-1-1-30, click to install
Installation starts - a pop-up window will ask about the ip address and password for the login cust
On root, the password will also be requested, but it will not change.
Therefore we use later root / root01 admin / admin01
After successful installation by command
xm list
The third line appears.
Domain-0 aes udom
It remains to configure Communication Manager and AES.
but this, next time.