Requirements

Hardware Requirements

Server

  • Virtual Machines: VMs are supported in all recording modes. 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 200+ simultaneous calls, the limits are in the RAM and disk IO subsystems. For virtual CPUs please multiply the number with 1.5, ie the minimum configuration for a VM should be 6 vCPUs or 10 for larger configurations.
  • RAM: 8 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 database, provision at least 10GB 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.

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.

Software Requirements

Server Side

  • Operating System: Any Windows Server. Desktop Windows OSes (Professional, XP, Vista, 7, 10) 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.

    Firewall The Windows Firewall must be completely disabled in order to not block RTP packets, which use dynamically allocated ports

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.

Warning

Most ANTIVIRUS software brands are incompatible with CallReplay for the following reasons:

  1. CallReplay has many hundreds of megabytes of executable JAR archives, which are scanned by AV at every service restart. Many times the service times out before it can report succes because the AV tries to scan every JAR file.
  2. The recorder software writes and manages hundreds of GBs of audio data. Scanning the recorded data by AV is tremendously slow and resource consuming.
  3. Some AV offer active network protection and block or disable the incoming SIP and RTP connections.

We cannot offer support for any problem caused by the interaction with AVs

Client Side

  •  Any operating system, with an ever green browser for example Chrome, Firefox or Microsoft Edge (Chromium based).