PBX stands for private branch exchange. It is the call-control system an organization uses to route calls among internal users and connect those users with outside telephone networks. A PBX can run on equipment at a business location, on a server or virtual machine, or as a service hosted by a provider.
The letters describe the original role: a private telephone exchange for one organization, rather than the public carrier exchange. The technology has changed, but the core job remains call control. A modern PBX may manage extensions, direct numbers, auto attendants, call queues, transfers, voicemail, business hours, forwarding rules, and connections to carriers or other calling platforms.
What does a PBX do?
Cisco defines a conventional small-business PBX as a telephone switching system that manages incoming and outgoing calls for internal users, connects to the public phone system, routes calls to extensions, and shares outside lines. That definition is a useful starting point, but current systems do not all use conventional phone lines or live at the customer site.
A business PBX typically performs several related jobs:
- Internal dialing: It gives users extensions and routes calls among those users.
- Incoming call routing: It sends a call to a direct number, receptionist, auto attendant, call queue, hunt group, voicemail box, or other destination.
- Outgoing call routing: It applies dialing and routing rules, then hands eligible calls to a carrier or other Public Switched Telephone Network (PSTN) connection.
- Call features: Depending on the platform and license, it can provide transfer, hold, park, forwarding, business-hours schedules, caller ID, voicemail, recording, conferencing, and reporting.
- Administration: It gives authorized administrators a place to manage users, numbers, devices, call flows, policies, and service settings.
Not every PBX includes every feature. Contact-center functions, compliance recording, analytics, mobile clients, CRM integrations, fax support, paging, and analog-device support may require different products, licenses, gateways, or service agreements.
PBX vs. VoIP vs. PSTN
These terms describe different parts of a business calling environment:
- PBX describes the business call-control function.
- VoIP describes carrying voice using Internet Protocol networks. An IP PBX or cloud PBX commonly uses VoIP, but the terms are not interchangeable.
- PSTN is the public telephone network used to reach outside phone numbers. A PBX needs an appropriate carrier or PSTN connection if its users must call or receive calls from that network.
- SIP trunking is one method used to connect compatible IP-based call-control systems with a service provider. Requirements vary by PBX, carrier, session border controller, and deployment design.
- Unified communications combines calling with some mix of messaging, meetings, presence, video, file sharing, or collaboration. A unified-communications platform may include PBX capabilities, but that does not make every collaboration feature part of the PBX itself.
Microsoft makes the distinction visible in Teams Phone. Microsoft documents separate Teams Phone PSTN connectivity models, including Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing. The right connection depends on available carriers, licensing, geography, existing equipment, emergency calling, resiliency, and administrative ownership.
Traditional PBX, IP PBX, and cloud PBX
| Model | Where call control runs | What to verify |
|---|---|---|
| Traditional PBX | Usually on customer-owned premises equipment, often using legacy digital or analog interfaces. | Vendor support, available replacement parts, carrier interfaces, licensing, maintenance skills, power, and migration constraints. |
| IP PBX | On an IP-based appliance, server, or virtual system managed by the organization or a provider. | Network readiness, security, voice quality requirements, SIP and carrier compatibility, upgrades, redundancy, and administration. |
| Hosted or cloud PBX | In infrastructure operated by the service provider, with phones and apps connecting to that service. | Provider responsibilities, service availability, internet and power dependencies, feature and device support, number ownership, data handling, support, and exit terms. |
“Hosted PBX” and “cloud PBX” are often used loosely. Buyers should compare the actual architecture, contract, support boundaries, and failure modes rather than deciding from the label alone. Hybrid designs also exist, especially when a business must retain analog devices, paging, elevators, alarms, a contact center, a preferred carrier, or a legacy PBX during migration.
How a PBX routes a business call
For an incoming call, the carrier or calling service presents the call to the business platform. The PBX checks the called number, time schedule, user state, and configured call flow. It can then ring a user, play an auto-attendant menu, place the caller in a queue, route to a group, forward to another number, or send the call to voicemail.
For an outgoing call, the PBX receives the digits entered by the user, applies the dial plan and calling permissions, selects an eligible route, and sends the call through the configured provider or interconnection. Internal calls may remain inside the platform and never use the public telephone network.
That routing logic is why a phone-system project starts with call flows, not handset shopping. Document departments, main numbers, direct numbers, extensions, business hours, queues, transfer rules, voicemail, after-hours behavior, recording needs, remote workers, emergency locations, and escalation paths before configuring the platform.
What should a business compare before choosing a PBX?
- Users, sites, and working patterns. Count employees, shared-area phones, remote users, mobile users, common-area devices, locations, and expected changes.
- Call flows and capacity. Record current numbers, concurrent-call needs, auto attendants, queues, hunt groups, conference use, contact-center needs, and seasonal demand.
- Carrier and number requirements. Confirm who owns each number, which numbers must port, the supported PSTN options, contract terms, toll-free services, and the rollback plan.
- Network and power readiness. Review internet circuits, switching, cabling, Wi-Fi, firewalls, quality-of-service settings, Power over Ethernet, battery backup, latency, jitter, packet loss, and alternate connectivity.
- Devices and integrations. Verify desk phones, headsets, mobile and desktop apps, analog adapters, paging, fax, door systems, CRM, recording, and identity integrations against the exact platform and license.
- Security and administration. Define administrator roles, multifactor authentication where supported, secure provisioning, change records, logging, fraud controls, patching, device lifecycle, and provider escalation.
- Continuity and support. Ask what happens during a local power failure, internet outage, carrier incident, cloud-platform interruption, device failure, or administrator lockout. Document the parties responsible for each layer.
- Total contract scope. Compare licensing, calling plans, taxes and fees, implementation, devices, support, number porting, integrations, training, adds and changes, renewals, and termination or number-release terms.
There is no universal “best PBX.” A platform is suitable only when its verified features, dependencies, support model, and cost structure match the organization’s call flows and risk requirements. Rivell’s guide to choosing a business VoIP provider provides a related vendor-evaluation checklist.
Emergency calling needs its own plan
Do not treat 911 as an ordinary feature checkbox. Emergency-calling behavior depends on the service, connection model, device location, user mobility, provider configuration, and applicable requirements. The FCC’s dispatchable-location summary describes location obligations for covered services and notes that non-fixed and outbound-only interconnected VoIP scenarios have specific requirements.
Before cutover, identify each service location and calling scenario, confirm who maintains emergency addresses and dispatchable-location data, understand how remote users are handled, validate provider instructions, and perform authorized tests using the provider’s process. Also document the impact of power and broadband failures and any required alternate means of calling.
Can a business keep its existing phones and numbers?
Sometimes, but compatibility must be checked. A phone may use vendor-specific firmware, a particular signaling method, or a provisioning service that is not supported by the new platform. Analog devices may need adapters or may require a different service. Phone-number portability depends on provider records, service area, number type, account status, and porting procedures. Inventory every number and device before making commitments.
Planning a PBX replacement
A controlled replacement normally includes discovery, design, provider and licensing confirmation, network remediation, number-port validation, configuration, pilot users, emergency-location review, user training, cutover testing, and a documented rollback or temporary-routing path. See Rivell’s business phone system installation process for the project sequence and its VoIP phone services page for ongoing platform and support considerations.
If you are comparing the underlying transport, read VoIP vs. traditional telephone service. Organizations considering Microsoft calling can also review the Teams Phone comparison guide. To document requirements for an existing or replacement PBX, contact Rivell for a phone-system readiness review.
