2.1. Hardware Requirements
Network
SPAN recording requires:
-
Managed network switch with port-mirroring capability (SPAN)
-
At least two network interface cards are required on the recording server, one for each monitored switch, and another for the site (a monitoring port can only receive packets). Using one interface card is possible, but the administration site will only be accessible from the physical console.
Forked recording requires:
- One network interface card on the recording server, for administration site and recording
- Cisco CallManager platforms newer than 5.0. For Cisco CallManager Express please use SPAN recording.
- Selected Cisco phone models.
Server
Virtual Machines: VMs are supported in all recording modes for up to 50 simultaneous calls. Forked Recording mode works directly, while SPAN recording requires additional configuration to enable network cards to work in promiscuous mode.
CPU: any modern quad core CPU will support 500 simultaneous calls, the limits are in the RAM and disk IO subsystems.
RAM: 1 GB of RAM for the system + 1GB for each million call records stored in the database. For example, if you intend to store 2 million calls in the db, provision at least 3GB of RAM for the server.
Storage: audio compression rate of 1.7 KB/s means that each GB on the drive can keep about 160 hours of recordings (voice compression is 8 times better than MP3). That is, you can keep 96,000 calls of 10 minutes on one 100 GB HDD. One month of typical call center recordings (160,000 calls) takes about 55 GB.
Please use only redundant disks (RAID1 and above) for storing call recordings!
2.2. Software Requirements
Server Side
Operating System: Any Windows Server. Desktop Windows OSes (Professional, XP, Vista, 7) can also be used, but TCP connection on these platforms are limited to 10 simultaneous sessions, limiting the number of users which can replay calls using the web site or a phone service.
IMPORTANT: It is recommended not to run any other server software on a production recording server! Call recording is essentially real-time. Failing to keep up with the traffic can result in lost calls. Other software can unpredictably use critical processor and memory resources which are necessary for packet capture. The application allocates computing resources according to priorities so an uncontrolled processing spike of another program may disrupt recording.
Client Side
- Any operating system, with a browser running Adobe Flash 11.1 or later, ( for example Internet Explorer 6, Firefox 3.0 and Opera 11.x ).
Software Optimizations
The Windows system cache is by default too large. Go to Control Pane / System / Advanced / Performance Settings / Advanced:
- set memory usage for best performance of Programs
- set processor scheduling for best performance of background services
2.3. Get the application and the license
Application
Our website always contains the latest version of application: http://call-replay.com/go/download
The setup automatically downloads the latest patch from our web site. If that does not happen MAKE SURE you download and apply it manually.
License
If you want an evaluation license, you can request it via email from info@call-replay.com or http://call-replay.com/go/contact.