How to Choose an IP-PBX Model: A Practical Sizing Guide

Choosing an IP-PBX model comes down to two numbers: how many calls happen at once (concurrent calls), and how many sites and gateway ports you need — not the total headcount. Get those right and you buy a platform that fits today and has room to grow, without overpaying for unused capacity.

Definition: IP-PBX sizing is the process of matching a phone-system model to your real load — concurrent call capacity, users, gateway ports, and sites — so performance, features, and budget all fit.

Size by Concurrent Calls, Not Users

A 300-person company rarely makes 300 simultaneous calls. Real peak concurrent usage is typically 15–30% of users for general offices, higher for support centers. Count the peak simultaneous internal-plus-external calls you expect, then add headroom for campaigns, seasonality, and growth.

Count Your Gateway Ports

Factor in Sites and Survivability

• Single site: one appliance sized for peak calls plus gateway ports
• Multi-site: a core model plus edge nodes; total model must cover the largest site's load
• Survivability: edge nodes need enough local capacity to run the branch if the link drops

A Simple Sizing Worksheet

1. Peak concurrent calls = users × usage factor (0.15–0.30) + headroom
2. Gateway ports = analog phones + analog lines + E1 channels + GSM
3. Sites = core model + one edge node per branch
4. Recording / IVR / contact-center features — confirm the model supports them
5. Future: can the same family scale 2–3x via license, not hardware swap?

Common Sizing Mistakes

• Buying for raw user count instead of concurrent calls
• Forgetting gateway ports until cut-over reveals analog devices
• Picking a model whose max is near today's load (no headroom)
• Ignoring local survivability for branch sites

How Newrock's OM Series Is Organized

Newrock's OM-series IP-PBX is sized by concurrent-call capacity and ships in models spanning small offices to large multi-site deployments, with integrated FXS/FXO, E1/T1, and GSM gateways so you size ports and calls in one platform. UMS manages the fleet as it grows.

FAQ

How many concurrent calls do I actually need?

Estimate users times a 15–30% usage factor, then add headroom for peaks; support and sales teams sit at the higher end of that range.

What gateway ports will I need?

Count analog phones (FXS), analog/POTS lines and alarms (FXO), any E1/T1 trunk (E1/T1), and whether you want cellular failover (GSM).

Can one model cover several branches?

A central model plus edge nodes per site scales across branches; size the core for total load and each edge for its local load plus survivability.

What if we grow beyond the model later?

Choose a family that scales by license rather than a full hardware swap, so adding users or capacity is a configuration change.

Bottom line: size an IP-PBX by concurrent calls and gateway ports, plan for sites and survivability, and leave headroom — the right model fits now and still fits after you grow.