Glossary · PBX

What is a PBX?

A PBX (Private Branch Exchange) is a business phone system that manages call routing between internal extensions and external phone lines. Historically PBX was on-premises hardware that switched analog phone lines between internal desks and the Public Switched Telephone Network. Today most PBX functions run in the cloud as hosted PBX or UCaaS platforms, eliminating the need for on-premises hardware, dedicated phone lines, and telephony technicians.

How a PBX works

Traditional PBX:

Phone lines from the telephone carrier terminate at the PBX hardware
Internal phones connect to the PBX via analog or digital extensions
PBX routes inbound calls to the right extension via DID, auto-attendant, or operator
PBX lets internal extensions call each other without going through the public network
PBX bridges internal calls to the carrier for external dialing

Cloud PBX (hosted PBX / UCaaS):

Phone lines are replaced by VoIP connections over the internet
Extensions are software (softphones, mobile apps, web) or IP desk phones
Routing logic runs in the provider’s cloud
No on-premises hardware to manage

PBX key features

Extensions: internal numbers (3–5 digits) assigned to users or departments
Trunks: outbound connections to the PSTN
Auto attendant: automated routing menu (“press 1 for sales”)
IVR: multi-level call flows with prompts and customer input
Call transfer, hold, park, pickup: move live calls between extensions
Ring groups / hunt groups: route inbound calls to a group of extensions
Voicemail: voicemail box per extension, often with transcription
Call recording: recorded conversations for compliance or QA
Conference bridges: multi-party calls
Fax-over-IP: fax transmission through the PBX

Traditional PBX vs. cloud PBX

Dimension	Traditional PBX	Cloud PBX / UCaaS
Hardware	On-premises PBX appliance + phones	No hardware (or optional IP phones)
Phone lines	Analog / digital / PRI trunks	VoIP or SIP trunking
Capital expense	$10,000–$500,000+ upfront	None
Operating expense	Carrier lines + maintenance contract	Per-user subscription
Setup time	Weeks to months	Minutes
Maintenance	IT staff or contractor	Provider handles
Scaling	Hardware upgrades required	Add users online
Mobile + remote	Limited	Native
AI features	None	Included in modern platforms
Failover	Depends on redundant hardware	Geographic redundancy in provider cloud

Legacy PBX still exists in large enterprises and regulated environments. Most small and mid-market businesses have moved to cloud PBX.

PBX vs hosted PBX — what is the difference?

A traditional PBX is on-premises hardware: the call-routing appliance sits in your server closet, wired to copper PSTN or PRI trunks, owned and maintained by you. A hosted PBX runs in the provider’s cloud — you rent a per-user seat, the vendor owns the media servers and handles updates, redundancy, and security patches.

The practical contrasts: hardware vs cloud (capex appliance vs zero hardware), $10K–$500K upfront vs $15–$60/user/month, hardware refresh and IT specialist needed vs add or remove users in a portal, and no native AI on legacy PBX vs bundled AI receptionists, transcription, and SMS drafting on modern hosted PBX. Hosted PBX wins for 95% of new 2026 deployments.

Who still uses traditional PBX

Regulated industries requiring specific on-premises control (some financial services, defense)
Large enterprises with major investments in Cisco CUCM, Avaya Aura, or Mitel that aren’t ready to fully migrate
Organizations in remote regions with unreliable internet connectivity
Facilities with complex analog integrations (elevators, alarm systems, legacy devices)

Most of these deployments use SIP trunking to bridge the on-premises PBX to modern cloud services rather than pure traditional PBX.

Why cloud PBX wins for most businesses

No capital expense: subscribe per user instead of buying hardware
Faster deployment: minutes vs. months
Mobile-first: works from any device, anywhere using a softphone or mobile app
AI features included: transcription, SMS drafting, virtual receptionist
Integrations: native CRM and helpdesk connections
Security: provider handles patches, encryption, compliance
Predictable cost: flat per-user pricing vs. hardware + carrier + maintenance — see transparent pricing →
Built-in redundancy: provider cloud has geographic failover

Example

A 25-person design agency had a 12-year-old Cisco PBX with 8 analog lines from the carrier. Monthly cost: approximately $400 for lines + $800/year PBX maintenance contract + $4,000 every few years in hardware replacement parts. They replaced it with DialPhone Advanced at $34/user × 25 = $850/month, and gained AI transcription, business SMS, video meetings, and HIPAA fax they didn’t have before. Setup took 6 hours across two evenings. PBX went in the dumpster.

PBX types: traditional vs IP vs hosted vs virtual

The label “PBX” covers four distinct architectures with very different cost, control, and operational profiles. Picking the wrong one in 2026 is the single most expensive telecom mistake a growing business can make.

Traditional analog PBX. Hardware-based TDM (time-division multiplexing) switch sitting in a server closet, wired to copper PSTN lines via PRI or analog trunks. Pros: works without internet, predictable behavior, fully owned. Cons: capex of $10K-$500K, requires a telecom technician on call, no native mobile, no AI, and most carriers are sunsetting copper PRI by 2027-2030. Dying technology — buy spare parts now or migrate.

IP PBX (on-premises). Software PBX (Asterisk, FreePBX, 3CX, Cisco CUCM, Avaya Aura) running on a company-owned server, terminating SIP trunks instead of analog lines. You own the SIP stack, dial plans, and recordings. Pros: full control, lowest per-seat cost at 200+ seats, air-gappable for security. Cons: requires in-house VoIP admin, you patch your own CVEs, hardware refresh every 5-7 years, and disaster recovery is your problem.

Hosted PBX / cloud PBX. The vendor runs the entire PBX (media servers, SBCs, redundancy, updates) in their cloud — see hosted PBX. You rent a seat for $15-$60/user/month and get a web admin, mobile apps, and IP phones that auto-provision. Pros: no capex, no maintenance, geographic failover, AI features included, deploys in hours. Cons: per-seat cost compounds at scale, vendor lock-in risk, requires reliable internet.

Virtual PBX. A stripped-down hosted PBX — usually mobile-app-only, no desk phones, no extensions, no IVR depth. Effectively a shared business number with voicemail routing. Pros: $10-15/user, set up in 10 minutes. Cons: not a real PBX once you exceed 5-10 users or need departmental call flows.

In 2026, 95%+ of new business deployments are hosted/cloud — see VoIP for the underlying transport. Traditional and on-premises IP PBX only justify themselves in two narrow cases: extreme security requirements (air-gapped government, defense contractors) and very large enterprises (1,000+ seats) with sunk capex in Cisco/Avaya/Mitel that hasn’t fully depreciated.

Best PBX phone systems in 2026

The hosted PBX market consolidated around seven serious vendors. Below are the ones worth shortlisting, with honest strengths and weaknesses. Pricing is list rate per user per month, billed annually, and excludes number porting, premium add-ons, and international minutes.

DialPhone — Hosted PBX with a native AI layer (AI receptionist, real-time transcription, AI call summaries, SMS drafting). Pro plan at $24/seat, Enterprise at $54/seat. Strengths: integrated AI receptionist that actually handles intent (not just menus), native business SMS with 10DLC compliance handled, and mobile apps that match desktop feature parity. Best fit: 5-500 seat US-based teams that want AI without bolting on a second vendor — see pricing.
RingCentral RingEX — The category incumbent. $20-$35/seat depending on tier. Strengths: deepest integration catalog (300+ apps), strong contact center upsell path (RingCX), mature global presence. Weaknesses: UI shows its age, AI features feel bolted on, and the cheapest tier limits SMS and video.
8x8 X Series — $24-$85/seat. Strengths: best-in-class international coverage with unlimited calling to 14-48 countries depending on tier, strong compliance posture (HIPAA, FINRA, FedRAMP), and a real contact center on the high end. Weaknesses: complex SKU stack, sales-led pricing on top tiers.
Nextiva — $18.95-$32.95/seat. Strengths: bundled CRM and helpdesk modules on higher tiers, US-based 24/7 support that consistently rates well, simple feature naming. Weaknesses: international calling is weaker than 8x8, AI tools are newer.
Dialpad — $15-$25/seat. Strengths: historically the strongest AI roadmap in the category — real-time transcription and coaching shipped years before competitors, plus a clean modern UI. Weaknesses: desk phone support is an afterthought, lower-tier feature gating is aggressive.
3CX — Free tier (self-hosted, up to 10 users) + paid tiers from $175/year flat (not per seat). Strengths: lowest TCO at scale because you bring your own SIP trunk and host on your own VM, no per-seat fee. Weaknesses: you are the IT department — patching, certificates, SBC tuning are all on you. Best fit: 50+ seat teams with a competent VoIP admin who want to escape per-seat economics.
Vonage Business Communications — $19.99-$39.99/seat. Strengths: solid mobile apps, strong developer API (inherited from Nexmo/Vonage API), good for hybrid voice + programmable use cases. Weaknesses: feature tiering is steep and middle-tier value is thin.

If you want the shortest honest summary: DialPhone for AI-first teams, 3CX for self-hosted TCO, 8x8 for international, Dialpad for AI roadmap depth, RingCentral for integration breadth.

On-premises vs hosted PBX: total cost of ownership over 3 years

The capex-vs-opex argument gets muddied by sales decks on both sides. Below is a clean 25-seat, 3-year comparison using current 2026 vendor list prices and typical channel install costs.

Cost component	On-premises IP PBX (25 seats)	Hosted PBX (25 seats)
PBX hardware / appliance	$12,000-$25,000 (capex)	$0
IP desk phones (25 × ~$180)	$4,500	$4,500 (optional)
Professional install + config	$3,000-$8,000	$0-$500
SIP trunk / DID fees	$15-$30/line/month × 8-12 lines	Included
Annual maintenance contract	$3,000-$5,000/year	$0
In-house admin time	4-8 hrs/month at loaded cost	Under 1 hr/month
Per-seat subscription	$0	$24-$54 × 25 × 36 = $21,600-$48,600
Hardware refresh reserve	~$5,000 set aside for year 4-5	$0
3-year total	~$50,000-$80,000	~$25,000-$50,000

Hosted PBX saves 50-70% over a 3-year horizon at 25 seats, and the gap widens once you factor in churn risk: on-premises capex is sunk whether you grow, shrink, or pivot. Hosted scales linearly with headcount.

On-premises starts to look reasonable in three specific cases: (1) 200+ seats where per-seat fees compound past the break-even line, typically around year 4-5; (2) regulated air-gapped deployments where cloud is disallowed; (3) you have unamortized sunk capital in a recent Cisco/Avaya refresh that can’t be redeployed elsewhere. Outside those, the math doesn’t work.

PBX migration checklist: 7-step move from legacy to cloud

Most failed cloud PBX migrations fail in the first two weeks, not at cutover. Follow this order.

Audit current usage. Pull 90 days of CDRs from your existing PBX. Capture inbound vs outbound volume, peak concurrent calls (sizes your SIP channels), top 20 destinations, integration touchpoints (CRM, helpdesk, fax), and a full hardware inventory (phones, SBCs, ATAs, headsets). You can’t migrate what you haven’t measured.
Map extensions and call flows. Diagram every IVR, ring group, and after-hours rule on paper. Don’t blindly recreate — most legacy PBXs accumulated 5-10 years of dead routes. Cut what no one uses. Simplify menu depth from 3-4 levels to 1-2.
Plan number porting. Open port-out requests with your current carrier early. Toll-free numbers port via RespOrg in 4-7 business days; geographic DIDs take 5-15 business days and require a recent bill plus a Letter of Authorization. Port toll-free and DIDs as separate batches so a single rejection doesn’t block everything.
Order or keep handsets. Most cloud providers support Polycom VVX, Yealink T-series, and Cisco SIP phones via auto-provisioning. Confirm your phones aren’t locked to the old PBX. If they are, factory-reset and re-flash with the new provider’s config URL — or buy new at $80-$200/phone.
Train pilot users. Roll out to IT/admin staff plus one customer-facing department first (typically sales or support). Give pilot users two weeks to surface gaps before expanding.
Cut over by department, not all at once. Big-bang cutovers fail. Migrate one department per week. Keep the old PBX answering its remaining extensions until each department is stable.
Decommission legacy hardware only after 30-day overlap. Don’t unrack the old PBX until 30 days post-final-cutover. You will discover at least one forgotten dependency — a fax line, an alarm panel, a contractor’s ring group.

PBX frequently asked questions

What’s the difference between a PBX and VoIP?

A PBX is the system that routes calls inside a business. VoIP is the transport protocol that carries voice as IP packets over the internet. They’re not alternatives — they work together. A modern hosted PBX uses VoIP as its underlying transport, while a traditional analog PBX uses copper PSTN lines. You can have a PBX without VoIP (legacy analog) and you can have VoIP without a PBX (consumer apps like Skype), but business deployments in 2026 are almost always both: a cloud PBX delivered over VoIP.

What is the difference between PBX and hosted PBX?

A traditional PBX is on-premises hardware you buy, install, and maintain — typically $10K–$500K upfront plus annual maintenance contracts and an in-house or contracted telecom admin. A hosted PBX lives in the vendor’s cloud — you pay $15–$60 per user per month, the vendor handles patching, redundancy, and uptime, and you scale by adding or removing users in an admin portal instead of buying hardware.

Do I need a PBX if I’m using a cloud phone system?

Yes — your cloud phone system is a PBX. The term “cloud phone system,” “business phone system,” “hosted PBX,” and “UCaaS” all describe products that include PBX functionality (extensions, routing, IVR, voicemail). Vendors avoid the word “PBX” in marketing because it sounds dated, but the underlying call-routing engine is the same private branch exchange concept, just hosted in the vendor’s cloud instead of your closet.

Can I run a PBX on my own server?

Yes. Open-source options like Asterisk, FreePBX, and FusionPBX are free to download. Commercial self-hosted options include 3CX and Cisco CUCM. You’ll need a Linux server (8GB RAM and 4 cores handles 25-50 concurrent calls), a SIP trunk from a provider like Twilio, Bandwidth, or Telnyx, an SBC if you have multiple locations, and someone who can patch CVEs and tune Asterisk dial plans. TCO can beat hosted at 50+ seats if you already have the admin headcount.

How much does a business PBX cost in 2026?

Hosted PBX runs $15-$60 per user per month depending on features and tier. For a typical 25-seat business, expect $500-$1,500/month all-in including SMS, video, and basic AI. On-premises IP PBX runs $12,000-$25,000 upfront for hardware plus $3,000-$5,000/year in maintenance. Self-hosted 3CX starts at $175/year flat for the license (you provide hardware and SIP trunk). Traditional analog PBX is no longer worth pricing — carriers are sunsetting the copper lines that feed it.

Will my existing desk phones work with a new PBX?

Probably, if they’re SIP-based. Polycom VVX, Yealink T-series, Cisco 7800/8800, Grandstream, and Snom phones are supported by almost every hosted PBX vendor — you point them at a new provisioning URL and they auto-configure. Phones locked to a specific vendor (some older Cisco SPA models, proprietary digital phones from legacy PBX systems) won’t port and need to be replaced at $80-$200/phone. Confirm before you sign — vendors publish supported handset lists, and unsupported phones become e-waste.

Is on-premises PBX more secure than hosted?

Not by default. On-premises gives you control over security, not security itself. A self-hosted PBX is only as secure as the admin who patches it — and unpatched Asterisk instances are a favorite target for toll-fraud bots that rack up $50,000 international call bills overnight. Reputable hosted PBX vendors (DialPhone, RingCentral, 8x8) carry SOC 2 Type II, HIPAA BAAs, and run 24/7 SOCs that most SMBs can’t afford in-house. Hosted is more secure for 95% of businesses. On-premises wins only when you have a dedicated security team and a regulatory requirement that mandates air-gapping.

See DialPhone’s cloud PBX

AI business phone system (cloud PBX) → · Small business phone system → · Enterprise phone system →

Hosted PBX vs. cloud phone: what’s the difference
How to choose a business phone system
Hosted PBX — the cloud-hosted evolution of PBX
VoIP — the protocol that powers modern cloud PBX
SIP trunking — bridging on-premises PBX to the cloud
DialPhone pricing