MOR vs. M4
Not sure what the difference is between Kolmisoft Softswitches MOR and M4?
Use this comparison to determine which platform best fits your business.
| Category | MOR | M4 SBC |
|---|---|---|
| Best fit | MOR is a better fit if you need a feature-rich Class 5 platform with billing, customer management, resellers, recordings, PBX-type features, or other service-provider features in one system. | M4 SBC is a better fit if your main priority is high-volume SIP traffic routing, SBC functionality, scalability, and strong Class 4 performance. |
| Quick recommendation | Choose MOR if you need more end-user, billing, reseller, PBX, prepaid/postpaid, or service-management features. | Choose M4 SBC if you do not need MOR-specific service features and mainly want a robust, scalable platform for SIP routing and high call volume. |
| Technology | MOR is based on Asterisk, one of the most popular frameworks for building communication applications. It is flexible and supports many service-provider features, but it is not designed for very high call volumes. | M4 SBC is based on Kamailio, SEMS, and RTPEngine. Its architecture is robust, powerful, and scalable, making it better suited for large SIP traffic volumes. |
| Performance | MOR single-server solution: up to 500 concurrent calls, up to 50 CPS, although in practice it is usually closer to 20 CPS.
MOR multi-server solution: up to 2,000 concurrent calls, up to 100 CPS. |
M4 SBC single-server solution: up to 500 concurrent calls, up to 100 CPS.
M4 SBC multi-server solution: up to 10,000 concurrent calls, up to 1,000 CPS. |
| Signaling protocols | SIP, H.323, IAX2 | SIP |
| Working behind NAT | MOR can work behind NAT. If your clients are behind NAT, MOR is usually the better choice because it handles these cases better. | M4 SBC can work behind NAT, but it is not designed for scenarios where many clients are behind NAT and use multiple registrations from one IP. In such cases, MOR is usually recommended. |
| Force provider/route by dialed prefix for SIP-registered users | Supported. MOR can use Localization Rules to change the LCR based on dialed prefixes. | Not supported when the customer does not have a fixed IP and connects by SIP registration. |
| API | MOR API | M4 API |
| Main features | MOR features | M4 SBC features |
| Hardware requirements | Hardware requirements for MOR | The same general hardware recommendations apply. Pay special attention to the recommended NIC if you need over 700 concurrent calls. |
| Implementations / topologies | MOR implementations | M4 SBC implementations |
| Documentation | MOR documentation | M4 SBC documentation |
| Statement of Account | ✔️ | ❌ |
| Auto-Dialer | ✔️ | ❌ |
| Callback | ✔️ | ❌ |
| Calling Cards | ✔️ | ❌ |
| Spy real-time calls | ✔️ | ❌ |
| Resellers | ✔️ | ❌ |
| Vouchers | ✔️ | ❌ |
| PBX Functions (IVR, Ring Groups, Voicemail, Music on Hold, Call Queues) | ✔️ | ❌ |
| Recordings | ✔️ | ❌ |
| SRTP support | ✔️ | ❌ |
| LCR Time Periods | ✔️ | ❌ |
| Rate Notifications | ❌ | ✔️ |
| NPA-NXX rates / billing | ❌ | ❌ |
Wondering where to start?
Here are some useful resources:
|