Hardware requirements
FlySIP Softswitch runs on a dedicated server that you provide. Size it by two numbers: concurrent calls (CC) and calls per second (CPS). Then add capacity if the switch relays media. The figures below come from synthetic and real traffic tests with signalling only, with the features that slow down call processing turned off.
General rules
Section titled “General rules”- Use name-brand server hardware. Avoid desktop parts and unknown brands.
- Count physical cores only. Hyper-threads and virtual cores do not count. A CPU sold as “8 cores, 16 threads” has 8 cores.
- Use hardware RAID with a write-back cache (WBC) and a battery backup unit (BBU). Software RAID slows the database down under load and is not recommended.
- Use an Intel PRO/1000 Gigabit Ethernet card. Bonded interfaces are recommended.
- Give FlySIP support remote console access, such as KVM or IPMI, for installation and upgrades.
The installer sets up the operating system and the database. You do not install them yourself.
Conversational traffic
Section titled “Conversational traffic”This is traffic with a low to medium CPS and long calls: high ASR and ACD, typical for retail and quality wholesale. CPU is Intel Xeon E5 or better, or a comparable AMD.
| Capacity | CPU | RAM | System and database disks | Backup and log disks | Bandwidth |
|---|---|---|---|---|---|
| 75 CPS, 2,000 CC | 8 cores, 2.0 GHz | 16 GB | RAID 1, 2 × 480 GB SSD | RAID 1, 2 × 1 TB SATA | under 10 Mbit/s |
| 90 CPS, 3,000 CC | 8 cores, 2.5 GHz | 24 GB | RAID 10, 4 × 240 GB SSD | RAID 1, 2 × 1 TB SATA | under 100 Mbit/s |
| 135 CPS, 6,000 CC | 12 cores, 2.0 GHz | 32 GB | RAID 10, 4 × 480 GB SSD | RAID 1, 2 × 800 GB SSD | under 100 Mbit/s |
| 200 CPS, 8,000 CC | 16 cores, 2.5 GHz | 32 GB | RAID 10, 4 × 480 GB SSD | RAID 1, 2 × 1.2 TB SSD | under 100 Mbit/s |
| 300+ CPS, 10,000+ CC | 24+ cores, 2.5 GHz | 64 GB | RAID 10, 4 × 960 GB SSD | RAID 1, 2 × 1.9 TB SSD | under 100 Mbit/s |
RAM is a minimum. Large rate tables, many routes or many environments need more.
The disks in the table are the best fit. These are acceptable alternatives, slower under load:
| Capacity | System and database disks | Backup and log disks |
|---|---|---|
| 75 CPS, 2,000 CC | RAID 10, 4 × 1 TB SATA; RAID 1, 2 × 1 TB SATA as a last resort | |
| 90 CPS, 3,000 CC | RAID 1, 2 × 480 GB SSD; RAID 10, 4 × 1 TB SATA as a last resort | |
| 135 CPS, 6,000 CC | RAID 1, 2 × 960 GB SSD | RAID 10, 4 × 1 TB SATA |
| 200 CPS, 8,000 CC | RAID 1, 2 × 960 GB SSD | RAID 10, 4 × 1 TB SATA |
| 300+ CPS, 10,000+ CC | RAID 1, 2 × 1.2 TB SSD; RAID 10, 4 × 1 TB SATA as a last resort |
International and call centre traffic
Section titled “International and call centre traffic”This is traffic with a medium to high CPS and short calls: low ASR and ACD, typical for international wholesale and call centres. Many short attempts load the switch more than the same number of long calls.
| Capacity | CPU | RAM | System and database disks | Backup and log disks | Bandwidth |
|---|---|---|---|---|---|
| 150 CPS in, 225 CPS out, 1,200 CC | 12 cores, 2.0 GHz | 16 GB | RAID 10, 4 × 480 GB SSD, or RAID 1, 2 × 960 GB SSD | RAID 1, 2 × 800 GB SSD, or RAID 10, 4 × 1 TB SATA | under 10 Mbit/s |
Media relay
Section titled “Media relay”When the switch relays media, the RTP of every call passes through the server. It costs CPU and bandwidth on top of signalling, so decide on media relay before you buy the hardware.
- CPU: at about 1,000 CC and 20 CPS, media relay keeps 3 to 4 physical cores fully busy. For 2,000 CC and 30 CPS with media relay, plan 16 physical cores.
- Network card: if audio quality drops above about 60,000 packets per second, which is 600 to 700 relayed calls, use an Intel PRO/1000 card.
- Bandwidth: depends mostly on the codec. Approximate figures:
| Load | G.711 | G.729 / G.723 |
|---|---|---|
| 2,000 CC, 30 CPS | 250 Mbit/s | 40 Mbit/s |
| 3,000 CC, 50 CPS | 375 Mbit/s | 60 Mbit/s |
| 6,000 CC, 100 CPS | 750 Mbit/s | 120 Mbit/s |
| 10,000 CC, 150 CPS | 1.25 Gbit/s | 300 Mbit/s |
The same codec can load the server differently: a 10 ms packetization time sends twice as many packets as 20 ms.
Media gateway servers
Section titled “Media gateway servers”A separate media gateway server takes media relay off the switch. Use one when you relay media for many calls, to help devices behind NAT or to hide your network.
| Load | CPU | RAM | Disks | Network |
|---|---|---|---|---|
| Up to 40 CPS out, 2,000 CC | 8 cores, 2.0 GHz, Intel Xeon E5 or better | 8 GB | Mirrored SATA or better | Intel PRO/1000, bonded recommended |
| Up to 60 CPS out, 3,000 CC | 2 × Intel Xeon E5-2620 v2, 2.1 GHz, 12 cores in total | 8 GB | RAID 1, 2 × 1 TB SATA | Intel PRO/1000 with LACP link aggregation |
The second line is a tested configuration. It was stable at 180 s ACD, 240,000 packets per second and 128 Mbit/s.
Several media gateways can work as a cluster that shares the load and survives the loss of one node. When the cluster is full or down, media goes through the switch’s own media relay. Ask FlySIP support whether the cluster is available for your licence.
Sandbox
Section titled “Sandbox”Customers with a purchased licence can order a sandbox: a second, small switch for tests and training. It needs:
| CPU | RAM | Disk |
|---|---|---|
| 2 or more physical cores | 4 GB or more | 50 GB or more |