How MOR pricing is calculated: own server or hosted

Operators ask for one Class 5 softswitch price. A reseller selling SIP trunks and a virtual PBX does not buy the same system as a carrier pushing wholesale minutes, so Kolmisoft does not publish one public figure.

The living reference is the Pricing structure page. If a factor, a layout, or a limit changes, Kolmisoft updates that page and leaves this post alone. Read the page for the current detail. Decide these four factors before you open the form.

The choice is a first Class 5 switch, or a replacement for A2Billing, a FreePBX box plus billing scripts, ASTPP or Magnus, or a commercial switch whose updates have stopped. The same four factors apply to M4. MOR is the switch retail and reseller businesses start with.

The four factors

Kolmisoft builds each quote from four factors, in the same order as the Pricing structure page:

Owners expect the price to climb with the customer list. The price does not depend on:

• the number of customers
• the number of SIP accounts
• the number of DID numbers
• the number of carriers
• the number of routes

The Pricing structure page keeps that list under “What Does NOT Affect the Price.” Kolmisoft does not cap those items to push you into a higher plan. A short route table and a large one follow the same license logic. Kolmisoft changes the quote when the product, the modules, the hosting model, or the traffic capacity changes.

Factor 1: MOR or M4

MOR is the Class 5 switch for retail VoIP, SIP trunking, a virtual PBX, resellers, and calling cards. End users and the resellers who sell to them sit here. IVR, ring groups, voicemail, call queues, recordings, and a reseller login belong on MOR.

M4 Class 4 softswitch is for wholesale transit, carrier interconnect, and high calls per second. One account can buy and sell. The work is routing and carrier billing, not a subscriber portal full of PBX menus.

A shop that sells SIP trunks and a virtual PBX to small businesses, with a separate login for each reseller, is an MOR shop. A shop that interconnects carriers and depends on attempt rate is an M4 shop. A mixed business still names one primary product. Retail customers with a side of wholesale minutes start on MOR. A transit business that also wants voicemail for a few desks is an M4 case when the busy hour is carrier traffic.

The MOR and M4 comparison lists the feature split. Class 4 and Class 5 covers the two jobs in more detail.

The wrong product wastes more than the hosting choice. A hosting change moves the same software onto another machine. The wrong product means a second migration: dial plan, rates, and reseller logins. Pick the switch that matches the service you sell, then pick where it runs.

If you are leaving A2Billing, what replaces it is the migration note. If you are comparing Kolmisoft with another platform, the comparison page is the short list.

Factor 2: Add-ons

The base platform is the switch, the billing, and the routing. Add-ons are optional modules. Kolmisoft adds a module to the quote when you take it. Leave a module out and it stays out of the quote.

On MOR the active list includes recordings, PBX functions, resellers, multi-level resellers, calling cards, callback, call shop, an auto-dialer, a payment gateway, automatic tariff import, advanced routing, the Monitorings addon, mobile number portability, and provider billing. Order from the MOR add-ons page. That page also marks modules Kolmisoft no longer develops, so an old SMS or Skype addon stays off a new quote.

M4 has a shorter list: automatic tariff import, mobile number portability, a payment gateway, and inbound DIDs. Those names sit in the M4 manual add-ons section.

Take the modules you will use. A virtual PBX operator needs PBX functions. Add recordings when customers must play calls back. A calling-card shop needs the calling-card module. A SIP-trunk reseller who does not sell cards, call shops, or a dialer leaves those modules out.

For the product workflows behind those quote factors, see VoIP billing software for retail and wholesale and multi-tenant PBX on MOR, including which modules are add-ons.

A full bundle of the current modules exists. Ask for that bundle on the pricing form if you want every active module. The figure for the bundle is on the quote.

Factor 3: Own server or hosted

Your own server

You provide the virtual machine or the bare-metal server, in your own rack or in a cloud account you already run. Kolmisoft licenses the software and supports it. You keep the operating system, the backups, and the network card.

The recommended hardware page is the spec Kolmisoft keeps current: Rocky Linux, the clock set to UTC, disk and CPU guidance, and which network cards struggle under load. A virtual machine is a normal own-server install. For a multi-server layout, several virtual machines on one physical host do not give you several servers of capacity. The stronger multi-server result is dedicated hardware, or virtual machines that each sit on their own dedicated host.

Own server fits a team that already runs a fleet. Patching, backups, and a failed disk are work that team does for the rest of the business.

Hosted

Kolmisoft runs the infrastructure. You skip the OS build, the backups, and the high-availability setup. Go-live comes sooner because you are not building the server. Hosted VoIP billing means the softswitch and the billing stay on Kolmisoft’s side. You still own the customers, the rates, and the carriers.

Hosted fits a company with no one for Rocky Linux, backups, and network cards. The team can sell trunks and PBX seats while Kolmisoft keeps the machine up.

A lifetime license is a third path some buyers ask about. The public pages do not set those terms. Ask Vilius on the pricing form.

Factor 4: Capacity and architecture

Concurrent calls and calls per second set the layout, and they measure different things. Concurrent calls are how many conversations are up at once. CPS counts new attempts each second, including attempts that never connect. A dialer can show a modest concurrent-call count and a heavy CPS. An office PBX full of long calls can show the opposite. Send the peak, not a quiet Tuesday.

A single server runs calls, the database, and the web interface on one machine. A multi-server layout splits that work. Redundancy adds standby servers, a database replica, or a load-balanced node so one failure does not stop the switch. Redundancy raises reliability, and it raises cost. A standby server takes over if the active server fails. It does not add call capacity.

Read the current figures on three pages:

• Softswitch performance for concurrent calls, CPS, and the split between capacity and a standby server
• MOR implementations for Class 5 layouts
• M4 system architecture for Class 4 layouts

Kolmisoft marks some one-server layouts for testing, because that machine has no spare. Read the layout that matches your peak before you treat a single server as production.

Two limits sit side by side. One is what the hardware can carry. The other is what the license allows. The license can allow fewer concurrent calls than the servers could handle. The license and the hardware both have to cover the peak you send.

Codec conversion, call recording, a busy web interface, and invoice jobs use the same CPU the calls need. Tell Vilius if you record calls or convert codecs on the switch. That workload belongs in the capacity note.

What to send when you request pricing

The form collects the contact. The note that makes the quote accurate is short:

• Retail, wholesale, or mixed. Name the main service.
• Peak concurrent calls and peak CPS, from last month’s graph or from a forecast.
• Your own server, or hosted.
• The add-ons you will use, by name. A full bundle is a clear request.
• Where traffic should be in 12 months.
• What you run today: A2Billing, FreePBX and scripts, ASTPP, Magnus, another commercial switch, or nothing yet.

A useful note looks like this: MOR, hosted, retail SIP trunks and a virtual PBX, recordings and PBX functions, peak concurrent calls and peak CPS from the current trunk graph, similar traffic in 12 months, moving off A2Billing.

If you have a server, add CPU, RAM, disk, and the operating system. The hardware page is the checklist.

Get a quote

Send the pricing form. Vilius follows up by email and builds the quote from the four factors above.

For a direct email, use the contact page or b2bsales@kolmisoft.com.

If this post and the Pricing structure page disagree, follow the Pricing structure page. Kolmisoft updates that page when a factor changes.