Recommended hardware

From Kolmisoft Wiki

Jump to: navigation, search

Contents

[edit] Specifications

Main principle - as powerful as possible. For single server solution we recommend:

Component Minimum requirement Recommended We provide as Hosted Solution Comment
CPU 4c/8t Xeon any higher CPU Germany: Intel(R) Xeon(R) CPU E3-1245-1270v6
USA: Single Quad, E3-1220/E3-1240
RAM 8 Gb 16 GB or more Germany: 32 GB
USA: 16/32 GB
HDD 100 Gb 100 Gb or more, SDD (Solid State Drives), RAID Type 1 Germany: 2 x 240 GB SSD RAID 1
USA: 120/128 GB SSD
all space must be assigned to / partition; ext3 file system
OS Linux Centos 6 Centos 6/7 x86_64 Centos 6.x/7.x OS timezone must be set to UTC or at least to Timezone which does not have daylight saving
NIC Any Intel I210, I350 Intel I210 Realtek RTL8111/8168/8411, Intel 82574L are weak NICs, not recommended
Brand Any Intel, DELL, HP, Fujitsu Intel


It is required to have clean server without any additional packets installed. Otherwise, the installation script will either wipe the IPTables rules or will not be possible at all.

Default Centos kernel is required.

[edit] Requirements for multi-server deployment

Asterisk or Freeswitch server: same requirements as above, except SSD would not increase performance so it is not needed and 4 GB of RAM is sufficient. CPU is most important component here. If Proxy solution is in use, Asterisks cannot be under NAT, it must have Public IP for SIP and RTP traffic.

Database server: same requirements as above and SSD is highly recommended here. SSD is must if system has more than one Asterisk server. There should be 100GB or more space as database grows fast on high traffic. Fast data storage device and CPU are most important here. If more than one Database server is in use, UPS (Uninterruptible Power Supply) devices must be used for these servers, otherwise power outage would cause broken replication. 8Gb RAM minimum.

GUI server: same requirements as above, except SSD would not increase performance a lot. HDD with more space is recommended here.

Proxy server: same requirements as above, except 4 GB of RAM and 40 GB on HDD will be enough here. SSD would not increase performance. Proxy server cannot be under NAT, it must have Public IP for SIP traffic.

Redundant servers: there are no special requirements on server hardware if server is part of redundant system. However, there are requirements for network to which servers are connected:

  • Both servers should be within same subnet.
  • Both servers should be able to broadcast packets to UDP 694 port.
  • Both servers should be able to receive packets broadcasted by other server.
  • There should be Virtual IP reserved in Subnet.
  • Both servers should be able to work with that Virtual IP (only one server at same time).

If any of requirements above are not met, in some cases it is possible to adapt different network configurations or services (like "IP Failover"). However, management/configuration/development of third party software (like special scripts) needed to adapt special solution should be performed by servers owner.



[edit] Virtualization

MOR system was tested and working (with low call capacity) on following Virtualization technologies:

  • VMware
  • VirtualBox
  • XEN

In general we do not recommend to run VoIP Core servers (with Asterisk/Freeswitch) on Virtual Machines.

GUI/DB servers on VM are acceptable.



[edit] FAQ

  • Do you have the provision of STUN and TURN servers on your end?

No, we do not provide STUN servers. MOR should receive Public IPs on SIP headers. NAT traversal should be done on customer's side.



[edit] See also

Personal tools

Try MOR

Try M2