Difference between revisions of "Softswitch performance"
| Line 78: | Line 78: | ||
<br><br> | <br><br> | ||
=== | === Wholesale transit business #3 === | ||
Implementation | Implementation - M2 single server solution with 600 concurrent calls limit. | ||
<br> | <br> | ||
Results: up to | Results: up to 600 concurrent calls, > 400 call attempts per minute (>7 CPS) | ||
[[File: | [[File:15.png]] | ||
<br><br> | |||
=== Calling Cards and Retail business #1 === | === Calling Cards and Retail business #1 === | ||
Revision as of 07:22, 22 November 2016
What is the maximal single server performance?
Max. performance of single server solutions (real examples):
- MOR - 500 concurrent calls*, 25 CPS (screenshots of this business case)
- M2 - 2000 concurrent calls*, 100 CPS (screenshots of this business case)
Once you reach limits of a single server, it is recommended to deploy a multi-server solutions.
What is the maximal multi-server performance?
- MOR - 1000 concurrent calls* (screenshots of this business case)
- M2 - screenshots will be added soon...
We have not implemented bigger systems than above, so it is not possible to show or predict performance results if you add more servers.
Factors that influence softswitch performance
- Hardware specifications (CPU, RAM, HDD type - 5400/7200 rpm, SSD, SAS, Raid, etc.)
- Network (routers/switches)
- Providers (connectivity, quality, PDD)
- CPS (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
- Structure of call (signalling only or signalling with media)
- Processes, running on the same time (if you generate invoices, statistics or run other processes, softswitch performance decreases)
- Additional functionality usage (if you record calls, use different IVR structures, softswitch performance decreases)
- Codec and protocol used
- Protocol and codec conversion (in case of transcoding performance decreases two times)
- Calls length (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
- DB and GUI on same server or on the separate (if you separate DB and GUI, you can increase performance)
- SIP balancer present or not (if you use SIP balancer in front of the servers, you can increase performance)
- Business model (Calling Card, Callback and Call Center calls decreases softswitch performance)
- etc
See also: How do you select a softswitch based on concurrent calls?
Real examples
In all of below examples companies are using recommended hardware.
Wholesale transit business #1
Implementation:
- 2 SIP balancers (in redundancy)
- 3 Asterisk (MOR) servers
- 2 DB/GUI server (with MySQL replication, redundancy)
Results: up to 1000 concurrent calls, up to 1500 call attempts per minute (25 CPS)
Wholesale transit business #2
Implementation - single server solution (GUI is not used almost at all, server has 24 cores).
Results: up to 500 concurrent calls, up to 1500 call attempts per minute (25 CPS)
File:Example.jpg=== Wholesale transit business #3 ===
Implementation - M2 single server solution with 600 concurrent calls limit.
Results: up to 600 concurrent calls, > 400 call attempts per minute (>7 CPS)
Wholesale transit business #3
Implementation - M2 single server solution with 600 concurrent calls limit.
Results: up to 600 concurrent calls, > 400 call attempts per minute (>7 CPS)
Calling Cards and Retail business #1
Implementation:
- 1 Asterisk (MOR) + DB + GUI server
Note: main business - calling cards and retail
Results: up to 100 concurrent calls, up to 800 call attempts per minute (13 CPS)
