A VoIP gateway port is one concurrent call channel: a 16-port gateway carries up to 16 simultaneous external calls, regardless of how many extensions sit behind it. The port tier you need is decided by the measured peak of concurrent external calls, with headroom, not by user count, which is why the same gateway tier can serve a small office or a busy call center.
This guide explains the capacity math, walks through the port tiers, shows how to size from real numbers, and covers how ports, SIMs, and codecs interact on a VoIP gateway.
The Capacity Math
One port equals one concurrent call channel: when a call is active, it occupies a port for the whole conversation, and the gateway can start a new call only when a port is free. That is the entire capacity model, and everything else in this guide is an application of it.
The math starts with the peak, not the average. A business with one hundred extensions and ten people calling at once needs at least ten ports, and a business with twenty extensions and a call center that peaks at fifteen needs fifteen; the extension count is irrelevant to the port count.
The sizing formula is simple: measure the busiest hour of external calls, count the maximum simultaneous calls in five-minute buckets, take the peak, and add headroom of 1.5 to 2 times. The headroom absorbs retries, transfers, and the day the traffic surprises everyone.
Transfers and conferencing change the math: a call transferred between trunks can occupy two ports briefly, and a conference with three legs uses three, so operations that transfer heavily need more headroom than a straight in-and-out call pattern. Add the transfer behavior to the peak measurement rather than assuming one call equals one port.
The peak measurement should be repeated over time, because call patterns change with the business: a new campaign, a seasonal spike, or a reorganized front desk all move the number. Re-measure quarterly and keep the record, because the gateway tier is a decision that should track the business.
The Tiers
| Tier | Concurrent calls | Typical deployment |
|---|---|---|
| 4-port | Up to 4 | Small office, low volume |
| 8-port | Up to 8 | Small business, modest traffic |
| 16-port | Up to 16 | Active office, small call center |
| 32-port | Up to 32 | Busy call center, multi-team site |
| 64-port | Up to 64 | Larger operations, high concurrency |
The 4-port tier fits the smallest deployments: a reception desk, a branch office, or a business that makes a handful of external calls at once. It is also the natural pilot tier for a team learning the gateway.
The 8 to 16-port tiers cover most small and mid-size businesses, where the peak of simultaneous external calls stays in single digits or the low teens. The 32 and 64-port tiers serve call centers and larger sites where concurrency is the business.
The tier names describe capacity, not quality: a 32-port gateway does not make better calls than an 8-port one, it carries more of them. Choosing the tier is a capacity decision, and the quality decisions are SIMs, signal, and codecs.
The tier choice also sets the upgrade path: a business on a 16-port gateway that outgrows it must either replace the unit or add another, so the growth plan belongs in the tier decision. The price difference between tiers is smaller than the cost of a mid-life replacement, which is why buying one tier up is often the cheaper long-term choice.
The 4-port tier deserves respect for what it does: a reception desk or branch office with one or two simultaneous calls does not need more capacity, and the smaller unit saves cost and power. Buy the tier the peak demands, no more and no less.
Sizing from Real Numbers
The reliable input is the PBX's call detail records: export the busiest month, count concurrent external calls in five-minute buckets, and take the peak with a date and hour. That single number is the specification the gateway must carry.
Seasonality belongs in the measurement. A business with month-end peaks, event days, or seasonal call centers should size from the busy season, not the average month, because a gateway that handles the quiet months fails exactly when the business is busiest.
The worked example: a business peaks at 11 concurrent external calls during the morning rush; with 1.5 times headroom, the target is 17, which lands on a 32-port gateway if the growth plan needs the room, or a 16-port unit if the peak is stable. The headroom factor is the judgment call between the two.
Include the queues and hunt groups in the measurement: calls waiting in a queue still occupy ports when they connect, and a hunt group that dials several destinations can hold two ports per attempt. The measured peak already includes these effects if it is taken from real traffic, which is why the record matters more than a model.
When the PBX has no call detail records, run a measurement week: ask staff to log busy moments, or instrument the router for call traffic, and treat the measured week as the baseline. A measured approximation beats a guessed number every time.
Ports, SIMs, and Codecs
Ports are not SIMs: a gateway may carry more SIM slots than concurrent ports, because SIMs rotate and share channels, and the SIM count should cover carrier diversity rather than equal the port count. Confirm both figures on the spec sheet before assuming the numbers match.
Codecs affect the port's work but not its count: a gateway converts audio between codecs on every call, and the codec choice changes bandwidth and quality, not concurrency. A call is a call for port purposes, and codec settings are a quality tuning lever, not a capacity one.
The interaction that matters is SIM health under load: sixteen concurrent calls on sixteen ports still share the SIM pool's carrier limits, so a site with poor signal or throttled SIMs will see call failures before the port tier is the issue. Monitor SIM health with the same attention as port usage.
Bandwidth belongs in the deployment plan: each concurrent call consumes network bandwidth according to the codec, and a 32-port gateway on a saturated office link will produce poor audio even with free ports. Confirm the uplink capacity and QoS settings as part of the gateway rollout.
The dashboard should show both sides of the equation: ports in use and SIM health per channel, because a gateway that fails on a full port tier and one that fails on a dead SIM look identical from the caller's side. The two views together are the diagnosis.
Telarvo Expert Views
The sizing mistake we see most is counting users instead of calls: a two-hundred-user office that peaks at eight external calls does not need a 64-port gateway. Measure the peak of concurrent calls, add headroom, and let the growth plan pick the tier, not the user count.
— Voice Solutions Engineer, Telarvo Store
Validation note: port counts and SIM-slot figures vary by model; confirm the configuration for the tier you evaluate.
Conclusion
Port tiers are concurrent-call capacity: measured by the peak of simultaneous external calls with headroom, chosen by tier, and tuned with SIM diversity and codec settings rather than by user count.
Key Takeaways for B2B Buyers
Measure the peak concurrent external calls in five-minute buckets, add 1.5 to 2 times headroom, size from the busy season, and confirm SIM slots and codec support on the spec sheet.
Questions to Ask Before Committing
Ask how many concurrent ports and SIM slots the model supports, how the peak was measured in the reference deployment, which codecs are supported, and how the unit reports SIM health under load.
Ask Telarvo Store which VoIP gateway tier matches your measured peak before you quote.
FAQs
How many calls can a 16-port gateway handle?
Up to 16 simultaneous external calls; total daily calls can be much higher because each port carries many calls over a day.
Do I count extensions or calls when sizing?
Calls. Extensions are a PBX matter; the gateway is sized by the peak of concurrent external calls.
Can I add ports later?
Only by buying a larger gateway or adding a unit; choose the tier with your growth plan in mind.
Why do calls fail on a gateway with free ports?
Usually SIM or carrier issues, not port capacity; check signal, SIM health, and carrier throttling first.
What does a port cost per month?
The port itself is hardware capacity; the recurring cost is the SIM plan or trunk behind it, which is why SIM selection is part of the gateway budget.