Difference between revisions of "M4 Switch"
From Kolmisoft Wiki
Jump to navigationJump to search
| (25 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[File: | [[File:m2_full_architecture.png|500px|right|alt="M2"|link=]] | ||
<mkmeta> | <mkmeta>M4 Class 4 Softswitch Description</mkmeta> | ||
=What is it?= | =What is it?= | ||
M4 is a Class 4 Softswitch dedicated to managing VoIP wholesale business (traffic aggregation, exchange, and transit, call termination, etc.). | |||
[[ | [[M4 Switch Manual]] | ||
<br><br> | |||
= Is it M2 or M4? = | |||
M2 is an old version of M4. M2 was based on Freeswitch which was slow and buggy. We reworked the system to use Kamailio/SEMS/RTPEngine, improved its performance many times, and named it M4. | |||
In many places in the documentation, you will find M2 references, we will change this with time, but currently, it means that this functionality came from M2 and is still applicable to M4. | |||
<br><br> | <br><br> | ||
| Line 12: | Line 19: | ||
=Differences from MOR= | =Differences from MOR= | ||
Below you can see the most important differences between | Below you can see the most important differences between M4 and MOR: | ||
* ''' | * '''M4 Switch''' is designed for wholesales business (Class 4 Switch), MOR - for retail (SIP Trunking, Calling Cards, Call Back, Call Shop, Resellers, etc) and is not optimized for wholesale. | ||
* ''' | * '''M4 Switch''' uses Kamailio/SEMS/RTPEngine as a SIP engine which allows having [[Softswitch_performance | twice bigger performance]] compared with MOR which is based on Asterisk. | ||
* ''' | * '''M4 Switch''' [[M4_Switch#Logical_Structure | logical structure]] allows to manage wholesale business very easy. Accomplishing the same tasks with MOR is more complicated and you need to dedicate much more time. | ||
<br><br> | <br><br> | ||
| Line 22: | Line 29: | ||
=Why should I use it?= | =Why should I use it?= | ||
M4 Switch gives never-seen-before flexibility when managing traffic transit. | |||
* [[M2 Switch Stress Test | more calls per server ( | * [[M2 Switch Stress Test | more calls per server (up to 1500 with media [no transcoding], 8000+ without media)]] | ||
* allow/block certain destinations, callerids | * allow/block certain destinations, callerids | ||
* sell/buy exact destinations from/to suppliers/clients | * sell/buy exact destinations from/to suppliers/clients | ||
| Line 30: | Line 37: | ||
** routing and tariff based per Device (not as per User as in MOR) | ** routing and tariff based per Device (not as per User as in MOR) | ||
** different routing orders for the same Routing Groups | ** different routing orders for the same Routing Groups | ||
* many other things | * many other things | ||
<br><br> | <br><br> | ||
| Line 36: | Line 43: | ||
=Logical Structure= | =Logical Structure= | ||
[[File:m2_logical_structure.png|1000px|alt=" | [[File:m2_logical_structure_simple.png|1000px]] | ||
<br><br> | |||
More detailed structure: | |||
[[File:m2_logical_structure.png|1000px|alt="M4 Logical Structure"|link=]] | |||
<br> | <br> | ||
| Line 47: | Line 59: | ||
<br><br> | <br><br> | ||
=How can I test it?= | =How can I test it?= | ||
| Line 54: | Line 67: | ||
=FAQ= | =FAQ= | ||
Q. What is the price?<br> | Q. What is the price?<br> | ||
| Line 62: | Line 72: | ||
Q. Can I test it? <br> | Q. Can I test it? <br> | ||
A. Sure, more details [http://www.kolmisoft.com/ | A. Sure, more details [http://www.kolmisoft.com/class-4-softswitch here] | ||
Q. Can it be upgraded from MOR?<br> | Q. Can it be upgraded from MOR?<br> | ||
A. No (because of completely different architecture) | A. No (because of completely different architecture) | ||
Q. Which protocols are supported?<br> | Q. Which protocols are supported?<br> | ||
| Line 71: | Line 81: | ||
Q. How many simultaneous calls can it handle? What about CPS?<br> | Q. How many simultaneous calls can it handle? What about CPS?<br> | ||
A. [[M2 Switch Stress Test | On 1 server: | A. [[M2 Switch Stress Test | On 1 server: up to 1500 with media without transcoding, 8000+ calls without media. ~90 CPS]] | ||
Q. Does it support Radius?<br> | Q. Does it support Radius?<br> | ||
A. Yes | A. Yes | ||
Q. Is it based on Asterisk | Q. Is it based on Asterisk?<br> | ||
A. No, Freeswitch | A. No, Freeswitch | ||
Q. Will it support Multi-Level Resellers?<br> | Q. Will it support Multi-Level Resellers?<br> | ||
A. | A. Currently no. | ||
Q. Can it work with SIP Proxy?<br> | Q. Can it work with SIP Proxy?<br> | ||
A. | A. Yes. | ||
Q. Can several servers work together?<br> | Q. Can several servers work together?<br> | ||
A. Yes | A. Yes. | ||
Q. Can several servers be connected to the same DB/GUI?<br> | Q. Can several servers be connected to the same DB/GUI?<br> | ||
| Line 95: | Line 105: | ||
Q. Where is the Manual?<br> | Q. Where is the Manual?<br> | ||
A. Here: [[ | A. Here: [[M4 Switch Manual]] | ||
Latest revision as of 11:45, 28 November 2022
What is it?
M4 is a Class 4 Softswitch dedicated to managing VoIP wholesale business (traffic aggregation, exchange, and transit, call termination, etc.).
Is it M2 or M4?
M2 is an old version of M4. M2 was based on Freeswitch which was slow and buggy. We reworked the system to use Kamailio/SEMS/RTPEngine, improved its performance many times, and named it M4.
In many places in the documentation, you will find M2 references, we will change this with time, but currently, it means that this functionality came from M2 and is still applicable to M4.
Differences from MOR
Below you can see the most important differences between M4 and MOR:
- M4 Switch is designed for wholesales business (Class 4 Switch), MOR - for retail (SIP Trunking, Calling Cards, Call Back, Call Shop, Resellers, etc) and is not optimized for wholesale.
- M4 Switch uses Kamailio/SEMS/RTPEngine as a SIP engine which allows having twice bigger performance compared with MOR which is based on Asterisk.
- M4 Switch logical structure allows to manage wholesale business very easy. Accomplishing the same tasks with MOR is more complicated and you need to dedicate much more time.
Why should I use it?
M4 Switch gives never-seen-before flexibility when managing traffic transit.
- more calls per server (up to 1500 with media [no transcoding], 8000+ without media)
- allow/block certain destinations, callerids
- sell/buy exact destinations from/to suppliers/clients
- configure intelligent priority routing
- routing and tariff based per Device (not as per User as in MOR)
- different routing orders for the same Routing Groups
- many other things
Logical Structure
More detailed structure:
Changes from MOR:
- Origination Point = Device
- Termination Point = Provider
- Routing Group = LCR
- Dial Peer ~= kind of LCR by Destinations
How can I test it?
Please follow this link
FAQ
Q. What is the price?
A. Please contact our sales department: b2bsales@kolmisoft.com
Q. Can I test it?
A. Sure, more details here
Q. Can it be upgraded from MOR?
A. No (because of completely different architecture)
Q. Which protocols are supported?
A. SIP (H323/IAX2 are available with special gateways for protocol conversion).
Q. How many simultaneous calls can it handle? What about CPS?
A. On 1 server: up to 1500 with media without transcoding, 8000+ calls without media. ~90 CPS
Q. Does it support Radius?
A. Yes
Q. Is it based on Asterisk?
A. No, Freeswitch
Q. Will it support Multi-Level Resellers?
A. Currently no.
Q. Can it work with SIP Proxy?
A. Yes.
Q. Can several servers work together?
A. Yes.
Q. Can several servers be connected to the same DB/GUI?
A. Yes.
Q. Will it support SIP Registering, DIDs/Ring Groups/Auto Dialer/Online Registrations/Subscriptions/Payment Gateways?
A. No. MOR Class 5 supports all these functions.
Q. Where is the Manual?
A. Here: M4 Switch Manual
