An IP PBX is the call brain that manages extensions and features, and a VoIP gateway is the trunk layer that connects the system to the public phone network; they are complementary systems, not alternatives. A business usually needs both: the PBX inside the network for call logic, and the gateway at the edge for external trunks such as SIM channels or fixed lines.
This guide explains the roles, what each system actually does, how they work together in a real deployment, and how to select the right combination, with the VoIP gateway as the trunk reference.
The Roles
| Layer | System | Job |
|---|---|---|
| Call logic | IP PBX | Extensions, features, routing |
| External trunks | VoIP gateway | Connect to public network |
| Endpoints | Phones and softphones | User devices |
The three layers are independent: the PBX can run without a gateway by using a hosted provider, and a gateway can sit in front of a legacy system without a full PBX migration. The separation is what makes each component replaceable.
The confusion between the two systems comes from all-in-one products that bundle both roles in one box. When the hardware does both, the sizing rule still applies separately: extensions and features scale on the PBX side, while trunks scale on the gateway side.
The terms matter in procurement because vendors blur them: a sales page calling a gateway a PBX leads buyers to compare the wrong specifications, sizing the gateway by users when it should be sized by trunks. Keep the two job descriptions in mind and the specification sheets become readable.
What the IP PBX Does
The IP PBX manages everything inside the phone system: extensions, voicemail, auto-attendant, call queues, call recording, and the dial plan that decides where each call goes. It is the system users touch every day, through their phones and the features they rely on.
The PBX also carries the integrations: CRM click-to-dial, presence, and API-driven call control live at the PBX layer. When a business says its phone system does something smart, the PBX is usually where that capability lives.
PBX capacity is measured in users, extensions, and concurrent calls, and its sizing follows the number of people and the features they use. A PBX that is too small for the user count degrades daily; one that is too large wastes license and hardware cost.
The PBX also owns the phone numbers' internal mapping: extensions, DIDs, and routing rules live there, so the gateway simply delivers calls to and from the outside. That division is why adding a new extension is a PBX task and adding a new trunk is a gateway task.
Modern PBX options include software-only platforms that run on servers or in the cloud, which changes the hardware picture but not the role: the PBX still manages the system, and a gateway still connects it to trunks. The deployment model is a choice within the architecture, not a change of the architecture itself.
What the VoIP Gateway Does
The VoIP gateway connects the phone system to the outside: it terminates trunks, converts signaling and audio, and carries calls to and from the public network. On a GSM gateway, the trunks are SIM channels with local mobile numbers; on an FXO or trunk gateway, they are analog lines or carrier trunks.
The gateway is where outside-call quality is decided: codec selection, trunk routing, and failover rules live here, and a misconfiguration shows up as echo, dropped calls, or failed routing rather than as a feature problem.
Gateway capacity is measured in concurrent external calls and ports, sized by the peak call load rather than the user count. A gateway for two hundred users may need only eight to sixteen trunks, which is why sizing starts with the measured peak.
The gateway also handles the media path for external calls: audio transcoding, echo cancellation, and jitter handling happen at the trunk edge. For international or mobile calls, the codec the gateway negotiates often decides whether callers notice the connection at all.
How They Work Together
In a typical deployment, the phone calls the PBX first: the PBX applies the dial plan, and when the destination is external, it routes the call to the gateway over SIP. The gateway selects a trunk, and the call continues on the public network; inbound calls follow the reverse path.
The split of responsibilities is clean: the PBX decides, the gateway connects. That separation makes troubleshooting faster, because a call that never rings out is a PBX routing issue, while a call that rings and sounds bad is a gateway or trunk issue.
Billing and reporting follow the split too: the PBX records call detail per extension, and the gateway records the trunk usage, SIM, or line per call. Together they answer the two questions operations care about: who called, and what did the trunk cost.
The handover between PBX and gateway should be tested as a flow: an outbound call, an inbound call, a call during a trunk failure, and a call during high load, with the quality checked on each. A deployment that tests these four flows before going live finds its integration problems while they are cheap to fix.
Selecting the Right System
Start with the PBX if you have none: choose it by user count, features, and integrations, because it is the system the business lives in. Then choose the gateway by trunk type and capacity, matching the external network to the calls the business actually makes.
For most businesses, the practical combination is an IP PBX for call logic and a GSM VoIP gateway for SIM-based external trunks, which replaces fixed-line dependence with local mobile numbers and flexible capacity.
If a business already has a PBX, the selection is only the gateway: confirm the PBX's SIP compatibility, choose the trunk type, size by peak concurrent calls with headroom, and verify the management and failover features before purchase.
Budget separation helps the decision: the PBX license and hardware follow the user count, and the gateway and trunk costs follow the call volume, so each line can be reviewed and optimized on its own. A business that bundles the budget cannot tell which side is driving cost.
Future growth belongs in the selection: a PBX with room for extensions and a gateway with spare trunk capacity let the business grow without a forklift upgrade. The extra capacity at purchase is cheaper than the replacement later.
Telarvo Expert Views
The question is never gateway or PBX; it is which PBX and which gateway. Buy them as separate, interoperable components, size each on its own metric, and confirm the integration in the quotation, because the pairing is where most voice deployments succeed or fail.
— Voice Solutions Engineer, Telarvo Store
Validation note: port counts and PBX compatibility vary by model; confirm integration and carrier terms for your markets.
Conclusion
The IP PBX and the VoIP gateway play different roles: the PBX runs the phone system, and the gateway connects it to the outside, and a well-designed deployment uses both, sized on separate metrics and integrated over SIP.
Key Takeaways for B2B Buyers
Buy the PBX by users and features, buy the gateway by trunk type and peak concurrent calls, confirm SIP compatibility, and keep the two layers separate so each can be upgraded independently.
Questions to Ask Before Committing
Ask which PBX integrations the gateway is tested with, how many concurrent calls and trunks the model supports, how failover works, and what the call detail records contain.
Ask Telarvo Store which VoIP gateway pairs with your PBX before you build the deployment.
FAQs
Do I need both a PBX and a gateway?
For external calling with your own trunk, yes: the PBX manages the system and the gateway provides the trunk; some hosted setups replace the gateway with a provider connection.
Can one device do both jobs?
Some all-in-one products do, but the sizing rules remain separate, and separate components are easier to upgrade and troubleshoot.
How do I know which gateway type I need?
Choose by the network you need to reach: SIM trunks for mobile numbers, FXS for analog devices, FXO for existing lines, and trunk gateways for carrier capacity.
Does the gateway affect call quality?
Yes; codec conversion, trunk routing, and failover settings on the gateway decide what callers hear, so configuration and monitoring matter.
Can I replace my PBX with a gateway?
No; the gateway provides trunks, not call logic. You can replace the PBX with a hosted or software PBX, but the gateway stays the trunk layer.