Difference between revisions of "Softswitch performance"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 3: Line 3:
Performance results in the following conditions ([[Recommended_hardware_for_MOR_server |recommended hardware]] is used, SIP protocol, no transcoding, CPS is low (<5), other processes than calls are not in use) are:
Performance results in the following conditions ([[Recommended_hardware_for_MOR_server |recommended hardware]] is used, SIP protocol, no transcoding, CPS is low (<5), other processes than calls are not in use) are:


* MOR - 200 concurrent calls with media, 4000 concurrent calls (only signalling)
* MOR - 200 concurrent calls
* M2 - 1000 concurrent calls with media, 8000 concurrent calls (only signalling)
* M2 - 1000 concurrent calls


<br>
<br>

Revision as of 14:01, 18 September 2014

Single server performance

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

  • MOR - 200 concurrent calls
  • M2 - 1000 concurrent calls



Multi-server performance

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



Factors which determine call performance

Call capacity vary depending on the following factors:

  • Hardware specifications
  • Structure of call (you will get 8 times better performance if you send just the signalling without media through the softswitch)
  • 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)
  • Transcoding (if you do 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)



See also