Minimum Requirements

When thinking on deploying a VitalPBX installation, there are a couple of questions that you might want to address. On this Lesson, we are going to go over some of the different questions that you might have during this initial process. Like, with what hardware and services is VitalPBX compatible with? Do I need telephony hardware? How many concurring calls do I expect to have? All of this and more gets an explanation.

The Requirements

These are the minimum requirements that VitalPBX has to run, so it can make and receive calls. The more features you need, like Call Recording, Call Compression, Sonata Suite, or VitXi, then the better your hardware would be.

Considerations

Keep in mind these considerations when deciding on the size for your VitalPBX installation. The more features you require, the bigger your system must be so it can perform those features. An interesting thing with VitalPBX is that the Core count on a CPU is not as important as to how fast they are. Even though various tasks within VitalPBX are multi-core, those core can get loaded fast if they are not fast enough. Then, in terms of RAM, VitalPBX is not that Heavy. It would then come if you want to process big data with the Sonata Suite Applications, where RAM is very important. And storage is one of the most obvious, you must consider your Call Traffic, Call Volume, and how much time you wish to keep those recordings stored in server.

Better Understanding (VitalPBX’s Stress Test Script)

For a long time many people have asked us the following:

“What is the concurrent call capacity of VitalPBX or Asterisk?… What is the bandwidth consumption for calls in VitalPBX or Asterisk?”

We took on the task of conducting an investigation of how to perform a test of concurrent calls and we realized that the information was very poor and did not meet our expectations. So we decided to make a script to test the capacity of concurrent calls in VitalPBX depending on the hardware it has been installed on and bandwidth consumption.

Prerequisites

To do this test it is necessary to have two VitalPBX servers installed, the server on which we will perform the tests and the remote server to which we will connect. It should be noted, that it is necessary that the remote VitalPBX server should have more capacity than the local one. Because if it had less capacity, it will not stress test the maximum capacity of the local server.

Script

Next, copy and run the following script on the server you wish to stress test.

[root@vitalpbx1 ~]# cd /

[root@vitalpbx1 ~]# wget https://raw.githubusercontent.com/VitalPBX/VitalPBX-Stress-Test/master/stress-test.sh

[root@vitalpbx1 ~]# chmod +x stress-test.sh

[root@vitalpbx1 ~]# ./stress-test.sh

Set up the following information (In your case the values can change):

IP Local....................................... > 192.168.30.10
IP Remote...................................... > 192.168.30.20
Network Interface name (ej: eth0).............. > eth0
Protocol (1.-SIP, 2.-IAX)...................... > 1
Codec (1.-None, 2.-G79, 3.- GSM)............... > 1
Recording Calls (yes,no)....................... > no
Max CPU Load (Recommended 90%)................. > 90
Calls Step (Recommended 5-20).................. > 10
Seconds between each step (Recommended 5-30)... > 10

Are you sure to continue with these settings? (yes,no) > yes

Are you sure you want to continue connecting (yes/no)? yes

root@192.168.30.20’s password: The root password from Remote Server

Note:
The test cannot last more than 10 minutes due to the duration of the audio.
If you want a longer duration, change the audio or add more time to the “demo-instruct” audio on this line on the stress-test.sh script:

asterisk -rx "channel originate Local / 200 @ call-test-ext application Playback demo-instruct&demo-instruct......

Results

Hardware Info
Motherboard----> YANYU STX-N92_VER:1.0
CPU Model------> Intel(R) Core(TM) i5-4210Y CPU @ 1.50GHz
CPU Cores------> 4
MEMORY RAM-----> 4 GB