PBX multi-tenant

PBX multi-tenant on Kolmisoft is the hosted-PBX and reseller setup on MOR Class 5. Tenants share one MOR platform. Each tenant gets its own users, numbers, and PBX features. The PBX feature set is the Add-on per le funzioni del PBX. M4 does not run these PBX features (MOR contro M4).

Is this suitable for our business?

This page is for voice service providers and resellers who sell hosted PBX or SIP trunks to many companies on one system. It is not a page for a single office buying a hosted PBX for itself.

• Hosted PBX operators who need IVR, queues, ring groups, voicemail, and DIDs per customer company.
• SIP-trunk providers who bill many PBX customers and may keep the customer PBX outside MOR.
• Retehändler who sell under their own brand and bill their own tenants, when the Reseller add-on is enabled.

White-label reseller billing on one invoice is described in the October article white-label hosted PBX, one invoice.

Does it support our required workflows?

Tenant and reseller billing

Each end customer is a MOR user (or a set of users) with prepaid or postpaid balance rules (Balance and Credit). Outbound calls, inbound DID charges, and packages are rated on that account. A reseller owns a group of those customers: the reseller balance gates their traffic, and the reseller can use its own tariffs when the Addon per rivenditori is active. Admin decides which add-ons each reseller group may configure under Autorizzazioni per i rivenditori.

What the operator manages vs what the tenant manages

• Operator (admin): platform, trunks to carriers, global tariffs, which PBX functions exist, which reseller groups may use them, DID stock, and invoices at the admin layer.
• Reseller (when enabled): its own customers, its tariffs, and the PBX features its permission group allows.
• Tenant user: the PBX tools turned on for that user—extensions-side features such as voicemail or phone book—within Permissioni degli utenti.

PBX features through daily work

With PBX Functions enabled, MOR provides External DIDs, Ring Groups, VoiceMail, PhoneBook, Music On Hold, Call Queues, PBX Pools, BLF, and IVR (Funzioni del PBX). In practice:

• A new company gets a DID from your inventory and an IVR that routes callers to a queue or ring group.
• Agents in a queue hear Music On Hold; missed callers land in VoiceMail.
• PBX Pools group devices for a tenant so one company does not see another company’s phones (PBX Pools).

Basic PBX items can be opened per user. Advanced items for resellers are opened per reseller group.

Customer billing, upstreams, portals, DIDs

Customer billing is MOR prepaid/postpaid plus DID owner and reseller rates (MOR DID Billing). Multiple upstream carriers are LCR providers on the same MOR. Customer self-care and portal work use the MOR user GUI and, where you build more, the MOR API—your developers own the custom portal code. DID management is the DID inventory and billing pages linked above.

How does it fit our infrastructure?

Multi-tenant PBX runs on MOR. Size the server for concurrent calls and CPS using Recommended hardware e Softswitch performance. Recording, queues, and IVR add load beyond plain termination.

If tenants already run FreePBX, 3CX, or VitalPBX, you can keep that PBX and use MOR only for billing and trunks. The PBX registers to MOR or is allowed by IP; MOR bills each phone by CallerID (PBX connection to MOR). Written guides exist for 3CX outgoing calls e VitalPBX inbound DIDs and outbound billing. FreePBX uses the same SIP trunk pattern; there is no separate FreePBX page.

What will our technical team manage?

• Standard MOR: users, devices, tariffs, LCR, invoices, CDR.
• Add-on: PBX Functions for the multi-tenant feature set; Reseller / Reseller PRO when partners sell under their brand (accessori).
• Your side: tenant onboarding process, which permissions each reseller gets, DID supplier contracts, and any external PBX you leave in place.

What does implementation involve?

Enable PBX Functions, set User Permissions and Reseller Permissions, import or create DIDs, create the first tenant with a ring group or IVR, connect at least one carrier trunk, and rate a test call before onboarding paying tenants. Add-on pricing follows the same quote factors as other MOR modules—see how MOR pricing is calculated. No EUR or USD figures are listed on this page.

Why should we trust Kolmisoft?

The behaviour above is what the MOR wiki and the PBX Functions documentation describe.

What should we do next?

1. Send the pricing form and say you need multi-tenant PBX / PBX Functions on MOR.
2. Or contact b2bsales@kolmisoft.com.
3. Read the Class 5 overview on the MOR product page if you still need the full softswitch scope.