Hardware requirements

From DooxSwitch wiki
Jump to: navigation, search

Hardware Specification Guidelines

Stick to reputable name brand hardware.

  • A note about Real CPU cores, versus Hyper Threads or Virtual Cores

Our documentation states “physical cores”. This excludes virtual or hyperthreading cores.


For example, the Intel | E5-2690processor, is marketed as having 8 physical cores and 8 virtual cores or “Threads”. This CPU counts as having 8 physical cores.


Component Minimum requirement Recommended We provide as Hosted Solution Comment
CPU Quad Xeon/Intel Core i5+ any higher CPU 2xIntel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz
RAM 4 Gb 16 GB or more 32 GB
HDD 100 Gb 100 Gb or more, SDD (Solid State Drives), RAID Type 1 2 x 120 GB SSD RAID 1 all space must be assigned to / partition; ext3 file system
OS Linux Centos 6 x86_64 Centos 6.6
Brand Any Intel, DELL, HP, Fujitsu Intel

Requirements for multi-server deployment

Asterisk 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.

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.



Virtualization

DooxSwitch system was tested and working on following Virtualization technologies:

  • VMware
  • Citrix Xen
  • KVM



It is required to have clean server without any additional packets installed.

Default Centos kernel is required.


Switch Hardware

2,000 Concurrent Calls, 30 CPS Spec guideline


CPU

2x 8 Core, 2.0GHz, Intel Xeon E5 or better or comparable AMD**

RAM

16GB or more (may depends on number rates/routes/environments)

Disk

RAID 10 SSD configuration with hardware RAID controller and BBU

 

Optionally RAID 5 1TB sata drives for log files.

Network Interface

GigE Network Interface Intel(R) PRO/1000 PCI Express Gigabit Ethernet. Bonded (FEC) interface is recommended

Bandwidth

less than 10 MBit/sec

3,000 Concurrent Calls, 50 CPS Spec guideline


CPU

2x 8 Core, 2.5GHz, Intel Xeon E5 or better or comparable AMD**

RAM

24GB or more (may depends on number rates/routes/environments)

Disk

RAID 10 SSD configuration with hardware RAID controller and BBU

 

Optionally RAID 5 1TB sata drives for log files.

Network Interface

GigE Network Interface Intel(R) PRO/1000 PCI Express Gigabit Ethernet. Bonded (FEC) interface is recommended

Bandwidth

less than 100MBit/sec


6,000 Concurrent Calls, 100 CPS Spec guideline


CPU

2x 16 Core, 2.5GHz, Intel Xeon E5 or better or comparable AMD**

RAM

32GB or more (may depends on number rates/routes/environments)

Disk

RAID 10 SSD configuration with hardware RAID controller and BBU

 

Optionally RAID 5 1TB sata drives for log files.

Network Interface

GigE Network Interface Intel(R) PRO/1000 PCI Express Gigabit Ethernet. Bonded (FEC) interface is recommended

Bandwidth

less than 100MBit/sec


10,000 Concurrent Calls, 150 CPS Spec guideline


CPU

32 Core, 2.5GHz, Intel Xeon E5 or better or comparable AMD**

RAM

64GB or more (may depends on number rates/routes/environments)

Disk

RAID 10 SSD configuration with hardware RAID controller and BBU

 

Optionally RAID 5 1TB sata drives for log files.

Network Interface

GigE Network Interface Intel(R) PRO/1000 PCI Express Gigabit Ethernet. Bonded (FEC) interface is recommended

Bandwidth

less than 100MBit/sec

Media Relay hardware guidelines

Media Relay Cluster is a beta product, and only available to enterprise customers participating in our beta program. If you wish to take part in this program, please contact [email protected]

The relay or proxying of media through an intermediary system is useful for some specific scenarios, such as NAT helping. and network topology masking. Relaying media will increase the network requirements, bandwidth resources and CPU resources of your system.

Media Relay causes the RTP stream between your client system and your vendor to travel via your DooxSwitch infrastructure.

The type of codec used by your client & vendor has a large bearing on the resources consumed. For example, here is the example of relative sizes between a selection of popular codecs:

Codec / Bandwidth usage examples

G.711

G.729/G.723

2,000CC / 30CPS

250 MBit/sec

40 MBit/sec

3,000CC / 50CPS

375 MBit/sec

60 MBit/sec

6,000CC / 100CPS

750 MBit/sec

120 MBit/sec

10,000 CC / 150 CPS

1.25 GBit/sec

300MBit/sec

 

Furthermore, the characteristics of traffic using the same codec can vary.

 

For example, the packetization window of a codec at 10msec will have a throughput of X and bandwidth usage of Y. If the packetization window is changed to 20msec, then the throughput changes to ~A and bandwidth usage to ~B.

 

The point to remember here is that all media traffic, even using the same codec is not always equal in terms of the resources required to relay it.

 

Medium spec Media Relay hardware suitable up to 2,000 Concurrent Calls, 30 CPS


CPU

16 Core, 2.5GHz, Intel Xeon E5 or better or comparable AMD**

RAM

8GB

Disk

Mirrored SATA hard drives or better

Network Interface

GigE Network Interface Intel(R) PRO/1000 PCI Express Gigabit Ethernet. Bonded (FEC) interface is recommended