Introduction
Cloud PBX and PSTN are not competing phone systems—though they’re often treated that way. PSTN is the public telephone network that connects any call to landlines and mobile numbers. Cloud PBX is the system that manages how your business handles those calls internally.
Plenty of US companies are replacing aging landlines or on-site PBX gear right now. The hard part is keeping your existing business numbers, reliable outside calling, and support for remote or hybrid teams—without a messy cutover.
This guide explains what each term means, how they work together, the real trade-offs between cloud and on-premises setups, and a practical migration checklist for US businesses.
Key Takeaways
- PSTN reaches external landlines and mobiles; PBX handles extensions, routing, and voicemail
- Cloud PBX runs off-site over internet and reaches the PSTN via carrier, SIP trunk, or Teams calling
- Cloud cuts hardware needs, but quality still depends on internet, power, and network setup
- Match architecture to user count, equipment, compliance needs, and IT capacity
What Cloud PBX and PSTN Mean
The Public Switched Telephone Network (PSTN)
PSTN is the interconnected public telephone infrastructure that lets any device reach any other phone number, whether it's a mobile phone, a landline, or emergency services. TechTarget defines PSTN as the world's collection of interconnected, traditionally circuit-switched voice networks.
Here's the key distinction: PSTN is a network and a calling destination. It's not a business phone system. It has no extensions, no auto attendant, no call queues.
What a PBX Actually Does
A private branch exchange (PBX) manages internal call traffic and shares external calling resources across your team, so you don't need a separate outside line for every employee. Typical PBX functions include:
- Extension dialing between employees
- Auto attendants and inbound call routing
- Ring groups and call transfers
- Voicemail and call forwarding
- Conference calling and call reporting
Cloud PBX vs. On-Premises PBX
A Cloud PBX delivers those same call-control functions from a provider-hosted platform instead of equipment sitting in your server closet. TechTarget's comparison notes that cloud deployments typically require no on-site PBX hardware, with updates handled remotely rather than by an on-site technician.
Public Telephone Company's hosted VoIP business phone service is built on that model. It runs over your existing high-speed internet connection, includes equipment with no upfront cost, and supports wireless extensions for faster installation.
Related Terms, Placed in Context
These terms aren't interchangeable. Each one is a different layer of the same architecture:
- VoIP: carries voice over internet networks instead of analog lines
- SIP trunking: connects a PBX or phone system to external telephone networks
- PSTN calling: dialing public telephone numbers from your business platform
What Cloud PBX Doesn't Replace
A Cloud PBX reduces reliance on on-site hardware, but it still needs PSTN access for calls to external public phone numbers. Analog devices like fax machines, alarm systems, door phones, and elevator lines often need separate adapters or gateways during migration.
How Cloud PBX and PSTN Work Together
The Outbound Call Path
When an employee dials an external number from a desk phone, softphone, or mobile app, the Cloud PBX applies calling rules first, then hands the call to a carrier or PSTN connection.
Along the way, the system handles:
- The assigned business caller ID
- Dialing permissions (blocking international calls, for example)
- Call recording policy
- Emergency (E911) location settings
The Inbound Call Path
A customer call enters on your public business number and reaches the Cloud PBX through your provider or carrier. From there it routes to an employee, ring group, auto attendant, or voicemail box.
In a small clinic, one main number can send new-patient calls to the front desk, billing questions to a separate queue, and after-hours calls to voicemail—no separate phone line for each function.
Common PSTN Connectivity Models
Microsoft's Teams ecosystem illustrates the three common ways to connect PSTN calling to a hosted platform:
| Model | Who Manages PSTN | SBC Required? |
|---|---|---|
| Calling Plan | Microsoft | No |
| Operator Connect | Certified third-party operator | No |
| Direct Routing | Customer-selected carrier | Yes (customer-side SBC) |
Microsoft's PSTN connectivity documentation confirms that Direct Routing generally requires a Session Border Controller, while a managed provider can run that SBC and carrier integration on your behalf. Match the model to how much carrier control you want to keep versus how much you want the provider to own.
Why Connectivity Choice Matters
The model you pick shapes day-to-day operations, not only install work:
- Number availability and porting timelines
- Domestic vs. international calling needs
- Existing carrier contracts you're still under
- How much routing control your team wants to retain
- Device compatibility with analog or legacy equipment
Infrastructure and Resiliency
Even the right connectivity model fails if the network underneath cannot carry voice cleanly. Microsoft's monitoring guidance for Teams sets these typical audio targets:
- Roundtrip time under 200 milliseconds
- Jitter under 30 milliseconds
- Packet loss under 2%
Microsoft Support's call quality guidance recommends testing every site against these thresholds before cutover, not just checking overall internet speed. Build in mobile failover, forwarding rules, and a documented escalation path for outages, since a single unprotected internet connection can take down every phone line at once.
Cloud PBX vs. Traditional PSTN and On-Premises PBX
These aren't three competing options. PSTN is the connectivity layer. On-premises PBX and Cloud PBX are two ways to manage call control. Here's how they stack up:
| Factor | On-Premises PBX | Cloud PBX |
|---|---|---|
| Infrastructure | Physical hardware, on-site wiring | No on-site PBX hardware required |
| Maintenance | Manual updates, local troubleshooting | Provider-managed updates |
| Scaling | New physical lines per expansion | Add or remove users on demand |
| Remote work | Difficult to extend off-site | Routes to office, home, or mobile |
Features and Day-to-Day Administration
Basic line-based calling gives you a dial tone. Cloud PBX adds auto attendants, call queues, business-hour rules, voicemail-to-email, and analytics, all managed through a portal instead of on-site equipment. Adding a user often takes minutes, not a service call.
Cost Categories Worth Comparing
Don't compare a single monthly number. Research every category:
- User licenses and PSTN usage minutes
- Phone numbers, taxes, and regulatory fees
- Handsets, installation, and SIP trunk costs
- Internet service and managed support
- Migration and number porting fees
A 2013 No Jitter study comparing 23 vendor responses for a hypothetical 2,000-seat enterprise found five-year total cost of ownership ranging from $1.85 million to $6.62 million across on-premises, hosted, and overlay solutions. Cloud wasn't automatically the cheapest option in every scenario studied. The math depends entirely on scope and time horizon.
Which Fits Your Business?
Basic PSTN lines can still work for isolated, low-complexity needs. Cloud PBX generally fits better when you need shared call handling, remote access, or flexible scaling. Consider on-premises or hybrid designs if you have specialized analog equipment, strict local survivability needs, or unusual compliance requirements.
Benefits, Use Cases, and Practical Considerations
Cloud PBX features show up in day-to-day operations across many industries:
- Local shops replacing copper lines with one hosted number and wireless extensions
- Law firms routing calls by partner or department with call recording
- Clinics managing appointment calls and after-hours coverage
- Property managers coordinating calls across scattered sites and on-call staff
Everyday benefits include:
- Consistent business caller ID on every outbound call
- Faster transfers and structured call queues
- Centralized admin from anywhere with internet access
US Compliance Considerations
Those operational gains still depend on meeting U.S. telecom rules. Before you migrate, check these points:
- E911: FCC rules under Kari's Law and RAY BAUM'S Act require direct 911 dialing, on-site notification, and dispatchable location for covered multi-line systems
- Number porting: You can generally keep your number when switching providers; porting fees may apply
- Caller ID authentication: Providers must implement STIR/SHAKEN on IP voice networks
- Call recording: Laws vary by state—some require all-party consent
Validate current rules with your provider and legal counsel before switching off legacy lines.
How to Choose and Migrate to a Cloud PBX
A solid Cloud PBX choice starts with a clear inventory of what you run today, then a controlled cutover—not a rip-and-replace on day one.
Pre-Purchase Checklist
Before requesting quotes, document:
- Current phone numbers, extensions, and call volume
- All locations, users, and device types
- Analog services (fax, alarms, door phones) needing separate handling
- Integrations with your CRM or business applications
- International calling destinations and emergency addresses
- Internet performance at every site
What to Compare Beyond Price
- PSTN coverage in your operating regions
- Number porting support and timelines
- Redundancy and security commitments
- 24/7 technical support and escalation procedures
- Implementation ownership and training
A Practical Migration Sequence
- Document your existing system: numbers, extensions, and call flows
- Design new call flows: match business hours and departments
- Test network and devices: validate every location before cutover
- Run a pilot group: prove the setup before full rollout
- Port numbers: keep a contingency forwarding plan ready
- Train users: coach the team and monitor call quality after cutover Always document fallback procedures for internet outages, power failures, and failed number ports before disconnecting legacy lines entirely. Public Telephone Company guides businesses through this migration to cloud-hosted phone systems. Plans include unlimited calling, 35+ features, wireless extensions, and 24/7 technical support, with equipment included at no upfront cost. Services scale from one user to more than 100,000. Confirm the fit for your user count, device mix, and PSTN requirements before you commit.
Conclusion: Cloud PBX and PSTN Are Complementary
PSTN gives you reach into the public telephone network. Cloud PBX gives you the business logic: routing, voicemail, and queues that shape how those calls get handled.
Before you request a migration assessment, inventory what you already have:
- Phone numbers and lines
- Devices and handsets
- Call flows
- Internet connectivity
That groundwork is the difference between a smooth cutover and a scramble.
Frequently Asked Questions
Can Microsoft Teams be used with PSTN calling?
Yes. Teams supports external PSTN calling through Microsoft Calling Plans, Operator Connect, or Direct Routing. Availability depends on licensing, regional coverage, and your chosen carrier configuration.
What is PSTN vs PBX?
PSTN is the public telephone network that connects calls to external numbers. PBX is a private system that manages internal extensions and call routing. A PBX connects to the PSTN to complete outside calls.
What is a Cloud PBX?
A Cloud PBX delivers PBX functionality, including extensions, routing, voicemail, and auto attendants, from a provider-hosted platform over an internet connection, rather than on-site equipment.
Does a Cloud PBX need PSTN connectivity?
Yes, for calls to ordinary external phone numbers. Internal calls between users on the same platform can stay entirely on the provider's IP network without touching the PSTN.
Can a business keep its existing phone numbers when moving to a Cloud PBX?
Generally, yes, through number porting. Confirm eligibility and timelines with your new provider, and keep a tested temporary forwarding plan in case the port takes longer than expected.
