Difference between revisions of "Softswitch performance"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 71: Line 71:


[[File:7.png]]
[[File:7.png]]
<br><br>
=== Wholesale transit business #4 ===
Implementation:
* 1 Asterisk (MOR) + DB + GUI server
Results - up to 400 concurrent calls, up to 1800 call attempts per minute (30 CPS)
[[File:8.png]]
[[File:9.png]]
<br><br>
=== Retail business #1 ===
Implementation:
* 1 Asterisk (MOR) server
* 1 DB + GUI server
Results - up to 100 concurrent calls, up to 50 call attempts per minute (1 CPS)
[[File:10.png]]
[[File:11.png]]
<br><br>
=== Retail business #2 ===
Implementation:
* 1 Asterisk (MOR) + DB + GUI server
Results - up to 250 concurrent calls, up to 2000 call attempts per minute (33 CPS)
[[File:12.png]]
[[File:13.png]]
<br><br>


==See also==
==See also==

Revision as of 08:22, 7 October 2014

General information

Performance results in the following conditions (recommended hardware is used, SIP protocol, no transcoding, CPS is low (<5), GUI/DB on another server, other processes than calls are not in use) are:

  • MOR - 500 concurrent calls*
  • M2 - 1000 concurrent calls*


'* We cannot guarantee such amount of concurrent calls as many factors influence it:

  • 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


If you need better performance than single server solution can offer, you should use multi-server implementations.



Real examples

Wholesale transit business #1

Recommended hardware is used. Implementation:

  • 1 SIP balancer
  • 3 Asterisk (MOR) servers
  • 1 DB/GUI server

Results - up to 1000 concurrent calls, up to 1500 call attempts per minute (25 CPS)

1.png

2.png

Wholesale transit business #2

Implementation:

  • 2 Asterisk (MOR) servers
  • 1 DB + GUI server
  • 1 DB server

Results - up to 200 concurrent calls, up to 400 call attempts per minute (7 CPS)

3.png

4.png

Wholesale transit business #3

Implementation:

  • 1 Asterisk (MOR) server
  • 1 Asterisk (MOR) + DB server
  • 1 DB + GUI server

Results - up to 250 concurrent calls, up to 200 call attempts per minute (4 CPS)

6.png

7.png

Wholesale transit business #4

Implementation:

  • 1 Asterisk (MOR) + DB + GUI server

Results - up to 400 concurrent calls, up to 1800 call attempts per minute (30 CPS)

8.png

9.png

Retail business #1

Implementation:

  • 1 Asterisk (MOR) server
  • 1 DB + GUI server

Results - up to 100 concurrent calls, up to 50 call attempts per minute (1 CPS)

10.png

11.png

Retail business #2

Implementation:

  • 1 Asterisk (MOR) + DB + GUI server

Results - up to 250 concurrent calls, up to 2000 call attempts per minute (33 CPS)

12.png

13.png

See also