Solution by Product · IP Telephony

How big an IP-PBX do you actually need?

Extension count is the marketing number. Concurrent calls, trunk channels and the network are what decide whether your phones work at 11 am on a Monday. This page shows you how to size all three, choose phones by user, connect legally — and avoid the six mistakes that make calls break up.

Step 1 · Sizing

IP-PBX sizing calculator

Enter your numbers. This sizes on busy-hour traffic with Erlang B — the same method telecom operators use — rather than a flat percentage, which under-sizes for peaks.

IP-PBX sizing calculatorErlang B at 1% blocking — indicative, confirmed on site survey
Desk, cordless and softphone users together
General office 10–15% · sales and support 25–35% · call centre 70–90%
These need a trunk channel; internal calls do not
60%
G.711 sounds best; G.729 uses about a third of the bandwidth
PBX concurrent-call capacity14 calls
SIP trunk channels to order10 channelsfrom a BTRC-licensed operator
Internet bandwidth for voice0.9 Mbps each wayreserved for voice, on top of your data traffic
PoE budget for the phones420 Wat 7 W per phone (802.3af Class 2) — size the switches to this

Indicative only. Busy-hour traffic = extensions × share on call (Erlangs); capacity is the Erlang B channel count at 1% blocking, the standard grade of service. Bandwidth per call from Cisco (20 ms packets over Ethernet). Add 30% for growth.

Short answer. Multiply your extensions by the share of the busy hour each person spends on the phone — that is the average number of calls at once. Then size for peaks with the Erlang B formula at 1% blocking, the industry-standard grade of service. A 60-person office on the phone 12% of the busy hour averages about 7 calls at once, so the PBX should handle 14 concurrent calls, with about 10 SIP trunk channels if 60% of calls go outside. Order the trunk from a BTRC-licensed operator, put voice on its own VLAN, and budget PoE for every phone.
Step 2 · Scope

What a complete IP telephony system actually includes

The PBX box is the cheap part. These are the parts that decide call quality — and the ones left out of budgets.

RequiredIP-PBX

Sized on concurrent calls with growth room. Ask for the concurrent-call limit in writing.

RequiredIP phones by user type

Entry phones for general staff, colour or touch for executives and reception, cordless or Wi-Fi for staff on the move.

RequiredOutside-line connection

SIP trunk from a licensed operator, or a gateway with FXO ports to bring existing analog lines in.

RequiredPoE switches

Power and network to every phone from one cable. Sized on the PoE budget, not the port count.

RequiredVoice VLAN and QoS

Voice separated from data and prioritised. Not optional — without it a file download breaks every call.

OptionalFXS gateway

Keeps analog phones, fax machines and lift emergency phones working on the new system.

OptionalCall recording storage

Sized against a retention period in months — about 0.5 MB per recorded minute at 64 kbps.

OptionalUPS

For the PBX, gateways and PoE switches together — protecting the PBX alone still loses every phone.

OptionalIntegration

CRM, hotel PMS or SIP door intercom — named and tested during evaluation.

Step 3 · Selection

Which PBX approach fits your organisation

Four ways to run your phones, and the honest trade-offs.

ConsiderationOn-premise IP-PBXHybrid IP-PBX (IP + analog ports)Cloud-hosted PBXLegacy analog PABX
Internal and inter-branch callsFree over your networkFree over your networkFree, over the internetFree inside the building only
Works if the internet goes downYes, internallyYes, plus analog linesNoYes
Keeps analog phones, fax, lift phoneNeeds a gatewayYes, built inNeeds a gateway on siteYes
Recording, IVR, mobile appYesYesYesLimited
Where call data is keptYour premisesYour premisesProvider's serversYour premises
Cost patternOne-time hardwareOne-time hardwareMonthly per userMaintenance of old stock
Typical useOffices, factories, hospitalsSites migrating from old linesSmall distributed teamsReplace when it fails
Extension count is the most misleading number on a PBX quotation. A box licensed for 200 extensions may carry only 30 calls at once — and that is the number that fails at 11 am on a Monday. Ask every bidder for the concurrent-call capacity in writing, and size the trunk channels on your outside calls, not on headcount.
Step 4 · Site readiness

What your site needs before installation

Structured cabling. Cat6 to every desk position, terminated on a patch panel. One cable can serve the phone and the PC through the phone's built-in switch.

Rack and power. PBX, gateway and PoE switches in a ventilated rack with a UPS sized for all of them, on a dedicated circuit.

Network design. A voice VLAN with QoS (DSCP EF) end to end, DHCP options for phone provisioning, and a fixed IP for the PBX.

Internet link. Enough upstream bandwidth for the trunk channels at your codec, on a stable connection — preferably a second link for failover.

Operator and numbers. Start the SIP trunk order or number porting with your licensed operator first — it takes longer than the installation.

Step 5 · Running cost

What it costs after you buy it

An IP-PBX cuts call costs, but it is not free to run. Over five years:

Trunk and call charges. Monthly SIP channel or line rental plus outgoing call charges from your operator. Internal and inter-branch calls cost nothing.

Power. A few watts per phone plus the PBX and switches, continuously — and the UPS batteries every 3–5 years.

Phones. IP phones typically last 5–7 years. Handsets and cords are the parts that wear.

Licences and support. Confirm whether recording, apps or extra extensions carry licences, and who maintains the dial plan.

The cost nobody budgets: an unsupported PBX. A grey-market box with no firmware updates is a security risk — toll fraud through an unpatched PBX can cost more in one weekend than the hardware. Genuine stock with local support is the real answer.

Step 6 · Mistakes

Six mistakes we see repeatedly

Sizing the PBX on extension count

A 200-extension licence on a box that handles 30 simultaneous calls fails at exactly the wrong moment.

Size on concurrent calls with Erlang B. Get the limit in writing.
Voice on the same VLAN as everything else

One large download and calls break up.

Separate voice VLAN with QoS, end to end.
No PoE planning

A switch sized on ports, not watts, drops phones under load.

Budget 7 W per phone and buy switches against the total.
Starting before number porting

You commission a system nobody can call.

Begin the operator order and porting first.
UPS on the PBX only

The PBX survives, every phone goes dark with the switch.

Protect PBX, gateways and PoE switches together.
Using SIM gateways to carry outside calls

Routing calls through SIM cards to bypass licensed operators is illegal termination; BTRC fines and blocks it.

Connect only through a BTRC-licensed operator's SIP trunk or PSTN lines.
Step 7 · Supply

Hardware we supply

Authorized Distributor of OpenVox, ZYCOO and FlyingVoice — genuine stock, firmware support and local service.

CoreIP-PBX

OpenVox UC series and ZYCOO CooVox, from small offices to multi-site.

PhonesDesk, executive and wireless

FlyingVoice desk and touch-screen phones; cordless and Wi-Fi handsets.

LinesGateways

FXO and FXS gateways for existing lines, analog phones, fax and lift phones.

NetworkPoE switches and power

Sized on the watt budget. See our PoE network guide.

Reference

Buyer & installer guide

The design figures engineers ask for, with the reason each one matters.

Concurrent calls
Erlang B at 1% blocking on busy-hour traffic

Standard grade of service; flat percentages under-size

Trunk channels
Erlang B on external traffic only

Order channels, not DID numbers

Bandwidth per call
G.711 87.2 kbps · G.729 31.2 kbps

Cisco, 20 ms packets over Ethernet

Voice quality
≤150 ms one-way · jitter <30 ms · loss <1%

ITU-T G.114 delay guidance; loss above 1% is audible

QoS marking
Voice VLAN, DSCP EF (46)

Prioritises voice over data end to end

PoE
7 W per phone (802.3af Class 2) + 20% headroom

Size switches on watts, not ports

Recording storage
≈ 0.5 MB per minute at 64 kbps

Size against retention in months

Outside lines
BTRC-licensed operator (SIP trunk / PSTN)

SIM-gateway termination is illegal

Selection guide

How to decide, and what to avoid

The PBX is the easy part. Extensions, concurrent calls and how you connect to the outside world are what decide the design.

1. How many extensions, and how many talk at once?
Under 50 extensionsA compact IP-PBX. Concurrent calls are rarely the constraint at this size.Size on concurrent calls, not extensions. A 50-person office rarely exceeds 10 simultaneous calls.
50–200 extensionsMid-range IP-PBX with room for growth and proper call recording storage.Ask for the concurrent-call limit in writing. It is the number that actually limits you.
Over 200, or multi-siteModular or clustered PBX, with per-site survivability.If a branch loses the WAN, can it still make local calls? That is the question that separates designs.
2. How do you connect to the outside line?
SIP trunk from an operatorCleanest and cheapest per channel. Confirm the operator supports it and how many channels you need.Concurrent channels, not DIDs, is the number to order.
Existing PSTN / analog linesGateway with FXO ports to bridge the old lines into the PBX.Count the lines you actually use, not the lines you pay for — they are often different.
Mix during migrationBoth, with a cut-over plan and number porting timeline.Porting takes longer than the install. Start it first.
3. What has to keep working when something fails?
Nothing criticalSingle PBX, standard backup.Acceptable for an office where the mobile network is the fallback.
Calls are the business — support desk, sales floor, hospitalRedundancy, UPS on PBX and switches, and a documented failover.Specify what happens to an in-progress call during failover. Most quotations do not say.
Multi-siteLocal survivability per branch, so a WAN outage does not silence a whole office.This is a real differentiator and it is rarely in a basic quotation.
4. What else must it do?
Calls onlyStandard PBX feature set.Do not pay for a contact-centre licence you will not use.
Call recording and reportingStorage sized for the retention period, and a clear legal position on recording.State the retention in months. Recording storage is the line most often under-sized.
Integration with CRM or door intercomConfirm the integration during evaluation, with your actual systems."API available" is not an integration. Test it before purchase.

Do not buy it this way

Do not size the PBX on extension count

Concurrent calls is the real limit. A 200-extension licence on a box that handles 30 simultaneous calls will fail at exactly the wrong moment.

Do not put voice on the same VLAN as everything else

Voice is latency-sensitive. One large file transfer and calls break up. Separate the VLAN and apply QoS — this is not optional.

Do not run IP phones without PoE planning

Each phone draws power. A switch sized without counting the phones drops them, and every drop is a dropped call.

Do not start the install before number porting is underway

Porting is the long pole. Begin it first or you commission a system nobody can call.

Do not skip the UPS on the PBX and the switches

A PBX on battery with the switch unprotected still loses every phone. Protect the whole path.

Do not under-size call recording storage

State the retention period in months and size for it. Discovering the limit means discovering deleted recordings.

For procurement & tender

Specify it correctly

What a ip telephony tender must state for quotations to be comparable instead of merely cheap.

SectorWhat to specifyTypical scaleThe clause bidders exploit
Corporate officeExtensions AND concurrent calls; SIP channels; voicemail; reports50–500 extensionsConcurrent calls stated separately from extensions
HospitalWard dial plan; emergency call handling; redundancy; 24/7200–1,000 extensionsWhat happens to a live call during failover
HotelRoom billing; wake-up calls; front-desk and PMS integrationPer roomPMS integration named and tested
Call centre / support deskQueues, recording and agent reports; peak concurrent calls20–200 agentsPeak concurrent calls and recording retention in months
Multi-branchPer-site survivability; central dial plan; inter-branch callingVariesLocal survivability is rarely quoted unless specified
GovernmentRecording retention; audit logs; on-premise hostingVariesState whether cloud hosting is permitted

BOQ line items — copy this into your tender

  1. IP-PBX with extension count AND concurrent-call capacity stated
  2. IP phones by model and quantity, per user type
  3. Gateways for analog lines or analog phones, with port count
  4. SIP trunk channels required at peak, from a licensed operator
  5. PoE switches sized on the watt budget
  6. Voice VLAN and QoS configuration
  7. Call recording storage sized to a retention period
  8. Number porting with timeline
  9. UPS covering PBX, gateways and switches
  10. Integrations (CRM, PMS, door intercom) named and tested
  11. Dial plan design, user training, warranty and local support
  12. Commissioning and handover: test 20 simultaneous calls at peak and listen for quality; verify voice vlan and qos marking on every switch; pull mains power and confirm phones stay up on ups
Why this matters commercially. A BOQ that omits power backup, civil works or commissioning invites a bidder to quote only the headline device and win on a number that is not comparable to yours. Listing every line makes the cheap quotation obviously incomplete rather than obviously cheaper.
FAQ

Questions buyers ask before specifying

Multiply extensions by the share of the busy hour each person is on the phone to get average calls at once, then size for peaks with Erlang B at 1% blocking. A 60-person general office averages about 7 calls at once and needs capacity for about 14. Use the calculator above.

Only enough for calls to and from outside the company — internal calls never use a trunk. For the same 60-person office with 60% of calls external, about 10 channels keep blocking under 1%. Order channels from a BTRC-licensed operator.

Usually yes. Either port the numbers to a SIP trunk provider, or keep the analog lines and bring them into the PBX through an FXO gateway. Start porting first — it takes longer than the installation.

Yes, through an FXS gateway or the analog ports on a hybrid PBX. Test the lift phone at handover; it is a safety line.

For calls over the internet, about 87 kbps per call with G.711 or 31 kbps with G.729, each way, reserved on top of your data. Ten G.711 channels need about 0.9 Mbps each way. Keep one-way delay under 150 ms and packet loss under 1%.

Using SIM-based gateways to route outside calls and bypass licensed operators is illegal call termination in Bangladesh, and BTRC fines and blocks it. Connect outside lines through a BTRC-licensed operator's SIP trunk or PSTN lines.

No. Run the new PBX alongside the old system, move one department at a time, and cut the outside lines over last, once number porting is complete.

Figures as of October 2026. Confirm with a quotation. Related solutions: PoE Network · Public Address · Conference System · Power Backup

Send us your extension count — we will size it properly

Free site survey across Dhaka and Chattogram. Our engineers check cabling, switches, the internet link and your existing lines before anything is quoted.