System Requirements
Hardware requirements
For a single-server setup, we recommend a SGI/Rackable Server configured as follows:
- CPU Intel/AMD Pentium III 2 GHz (minimum), works on Raspbery
- RAM 1 Gb per core for IVR, 2 Gb per core for IVVR
- HDD/SSD 16 Gb (minimun)
- Motherboard with 533MHz/800MHz system bus support
- Ethernet Network board (with Mac Address)
- TDM Digium E1/T1 or any other Asterisk compatible board
Make sure that your servers are installed and equipped with all the required hardware.
| CPU | IVVR server (Video) | IVR server (Voice) |
|---|---|---|
| 1x core | min 15 ports … max 30 ports | min 30 ports .. max 60 ports |
| 2x cores | min 30 ports … max 60 ports | min 60 ports .. max 120 ports |
| 4x cores | min 60 ports … max 120 ports | min 120 ports .. max 240 ports |
| 8x cores | min 120 ports … max 240 ports | min 240 ports .. max 480 ports |
NOTE:
IVR / IVVR System performance will depend on all codecs, applications, total load used by your server.
This figures are not based on specific hardware. Our recomendation to take the min values if your are going to run transcoding by software.
Please check that other hardware installed on your server (such as network adapter, RAID controller, etc.) is supported by the Linux distribution that you use.
Software requirements
The Vxi VoiceXML browser runs on most modern Linux Operating Systems (Debian, CentOS, Ubuntu, Redhat, Mandrake, Suse, Fedora, etc). However, it may be difficult for a novice system administrator to install and configure the operating system to meet all of the requirements and provide the best performance. Installing all the software could also prove to be a time-consuming task. We provide a seamless way to perform a complete server installation from scratch, in less than 15 minutes. The installation uses tar.gz packages and bash scripts.
Vxi binaries packages are available the following Linux Master distributions:
- Debian 6, 7 - http://www.debian.org
- CentOS 5, 6 -http://www.centos.org
The last VXI V12 release add an FreePBX module and Elastix modules. They allow to control the VoiceXML configuration and administration from the Web Interface.
Other compliant Linux distributions:
| Distribution | Package | Website |
|---|---|---|
| Ubuntu | Debian | http://www.ubuntu.com |
| Redhat | CentOS | http://www.redhat.com |
| Fedora | CentOS | http://fedoraproject.org |
| Suse | Debian | http://www.opensuse.org |
| Mandrake | CentOS | http://www.mandriva.com |
| FreePBX | CentOS | http://www.freepbx.com |
| Elastix | CentOS | http://www.elastix.com |
| AsteriskNow | CentOS | http://www.asterisk.com |
| Raspbian | Debian/ARM | http://www.raspbx.com |
i6net uses Debian and Centos distributions to generate all packages provided. Most packages built are specifically configured by default for this Linux OS.
There are two available versions of our packages:
- “32bit i686” package, compiled with GCC 4.x
- “64bit i686” package, compiled with GCC 4.x
Disable the SELinux. It can lock the library loading.
You can use '/usr/sbin/setenforce 0' before launching the Vxi VoiceXML browser.
Vxi on a Virtual Environnement
You can install and run Vxi on a virtual machine for any production, development and testing system.
Vxi has been successfully tested over:
- VMware
- Amazon EC2
- Proxmox
Vxi requires a significant amount of system resources and virtualization can reduce system performance when running in a virtual environment. We recommend to run voice recognition and text-to-speech on a separate server because they are very CPU-intensive and require real-time system resources and RAM, along with any audio or media requirements of a caller session, such as dialog prompts or playing of pre-recorded audio file.
Depending on the virtual environment management, there can be issues with using cloned images, virtual network stacks, installation issues, and licensing problems.