PSTN vs PBX: What Is the Difference and Which One Do You Need?
Understanding the difference between PSTN (Public Switched Telephone Network) and PBX (Private Branch Exchange) is essential for enterprise organizations evaluating their telephony infrastructure. PSTN is the global network of traditional telephone lines, while PBX is a private telephone system within an organization that routes calls internally and connects to the PSTN for external calling. With Microsoft Teams Phone System emerging as a dominant cloud-based alternative, organizations must understand how these technologies compare and integrate to make informed decisions about their communications infrastructure.
What Is PSTN?
The Public Switched Telephone Network (PSTN) is the worldwide network of circuit-switched telephone infrastructure that has connected voice calls for over a century. It encompasses the physical copper lines, fiber optic cables, switching centers, and signaling protocols that enable any telephone to call any other telephone anywhere in the world.
- Infrastructure: Physical network of copper pairs (last mile), fiber optic trunk lines, central offices, and tandem switches operated by telecommunications carriers (AT&T, Verizon, Lumen)
- Technology: Circuit-switched technology that dedicates a physical circuit for the duration of each call, ensuring consistent voice quality but inefficient bandwidth usage
- Numbering: Uses the E.164 international numbering plan with country codes, area codes, and subscriber numbers (e.g., +1-888-381-9725)
- Regulation: Regulated by the FCC in the United States, with mandatory E911 service, Universal Service Fund contributions, and interconnection requirements
- Reliability: Historically the most reliable communications network with 99.999% uptime ("five nines"), powered independently from commercial electrical grids at central offices
- Transition: Carriers are actively migrating PSTN infrastructure to IP-based networks. The FCC has authorized carriers to discontinue traditional copper-based service in many areas
What Is PBX?
A Private Branch Exchange (PBX) is a private telephone system that serves an organization by providing internal extension dialing, call routing, voicemail, auto attendant, and other business telephony features. PBX systems connect to the PSTN through trunk lines (analog, digital/PRI, or SIP) for external calling.
- On-premises PBX: Hardware-based systems (Cisco UCM, Avaya Aura, Mitel) installed in the organization's server room with physical phones connected via structured cabling
- IP PBX: Modern PBX systems that use VoIP (Voice over IP) for internal calls and can connect to the PSTN through SIP trunks rather than traditional analog or PRI lines
- Hosted/Cloud PBX: PBX functionality delivered as a cloud service (RingCentral, 8x8, Vonage), eliminating on-premises hardware and shifting to subscription-based pricing
- Core features: Extension dialing, call transfer, conference calling, auto attendant (IVR), voicemail, call queues, hunt groups, call recording, and caller ID management
- Advanced features: Unified communications (voice, video, messaging), presence information, CRM integration, call analytics, and compliance recording
Key Differences: PSTN vs. PBX
PSTN and PBX are not competing technologies but rather complementary components of a complete telephony system. The PSTN provides connectivity to the outside world, while the PBX provides internal call management and business features.
- Scope: PSTN is a public network connecting all telephone subscribers globally. PBX is a private system serving a single organization's internal communications needs
- Ownership: PSTN is owned and operated by telecommunications carriers. PBX is owned or leased by the organization (on-premises) or provided as a service (cloud PBX)
- Cost model: PSTN charges per-line fees and usage charges for long-distance/international calls. PBX involves capital equipment costs (on-premises) or per-user subscription fees (cloud) plus PSTN connectivity costs
- Features: PSTN provides basic calling, caller ID, and call waiting. PBX provides advanced business features including auto attendant, call queues, voicemail-to-email, conference bridges, and unified communications
- Scalability: Adding PSTN lines requires carrier provisioning (days to weeks). Adding PBX extensions can be done in minutes for IP/cloud systems or requires physical wiring for legacy analog systems
- Call quality: PSTN provides consistent, high-quality voice using dedicated circuits. VoIP-based PBX quality depends on network bandwidth, latency, jitter, and QoS configuration
Microsoft Teams Phone System: The Modern Alternative
Microsoft Teams Phone System is a cloud-based PBX replacement that provides enterprise telephony features within the Teams platform. It can connect to the PSTN through Microsoft Calling Plans, Operator Connect, or Direct Routing (SIP trunking), providing a complete replacement for traditional PBX systems.
- Microsoft Calling Plans: Microsoft acts as the PSTN carrier, providing phone numbers and calling minutes directly. Simplest deployment but limited geographic availability and calling plan options
- Operator Connect: Microsoft-certified carriers (AT&T, Verizon, BT) provide PSTN connectivity that integrates directly into the Teams admin center. Balances simplicity with carrier choice
- Direct Routing: Connect your existing SIP trunk provider to Teams through a Session Border Controller (SBC). Maximum flexibility, supports any carrier, enables gradual migration from existing PBX
- Teams Phone features: Auto attendants, call queues, voicemail with transcription, call transfer, call park, shared line appearance, delegation, compliance recording, and Power BI call analytics
- Integration advantages: Native integration with Teams chat, meetings, presence, SharePoint, Outlook calendar, and Dynamics 365 CRM for click-to-call and screen pop
Which Solution Do You Need?
The right telephony solution depends on your organization's size, existing infrastructure, Microsoft 365 investment, compliance requirements, and total cost of ownership considerations.
- Small businesses (under 50 users): Microsoft Teams with Calling Plans provides the simplest, most cost-effective solution with no on-premises infrastructure required
- Mid-market (50-500 users): Teams Phone System with Operator Connect or Direct Routing provides enterprise features with carrier flexibility and competitive PSTN pricing
- Large enterprise (500+ users): Teams Phone System with Direct Routing using existing SIP trunk contracts, potentially with Survivable Branch Appliances for branch office resilience
- Contact centers: Teams-certified contact center solutions (Five9, NICE, Genesys) integrate with Teams Phone System for combined UCaaS and CCaaS deployment
- Compliance-heavy industries: Healthcare, financial services, and government organizations need Teams Premium or certified compliance recording solutions for MiFID II, HIPAA, or Dodd-Frank requirements
- Hybrid scenarios: Organizations with existing PBX investments can use Direct Routing for gradual migration, routing some users through Teams and others through the existing PBX during transition
Why Choose EPC Group for Enterprise Telephony
EPC Group has over 28 years of experience implementing Microsoft communications solutions for enterprise organizations. As a Microsoft Gold Partner, our team specializes in Microsoft Teams Phone System deployments with Direct Routing, Operator Connect, and Calling Plans across healthcare, financial services, government, and manufacturing. Our founder, Errin O'Connor, has authored 4 bestselling Microsoft Press books, and our Teams practice has delivered telephony migrations for organizations with thousands of users across multiple locations.
Ready to Modernize Your Phone System?
Let EPC Group's Microsoft Teams telephony experts design and implement a modern communications solution that replaces your legacy PBX, reduces costs, and integrates voice with your Microsoft 365 ecosystem.
Frequently Asked Questions
Is the PSTN being shut down?
The traditional copper-based PSTN is being gradually decommissioned by carriers worldwide. In the U.S., the FCC has authorized carriers to discontinue legacy copper services in areas where fiber or wireless alternatives exist. However, PSTN connectivity itself is not disappearing -- it is transitioning from circuit-switched copper to IP-based fiber infrastructure. Phone numbers, calling capabilities, and E911 service continue to function, but the underlying technology is modernizing. Organizations should plan for this transition by adopting SIP trunking or cloud-based calling plans rather than relying on analog or PRI lines.
How much does Microsoft Teams Phone System cost?
Microsoft Teams Phone System licensing is included in Microsoft 365 E5 ($57/user/month) or available as an add-on to E1/E3 plans ($8/user/month for Teams Phone Standard). PSTN connectivity adds: Domestic Calling Plan ($12/user/month for 3,000 minutes), International Calling Plan ($24/user/month), or Pay-As-You-Go Calling Plan ($0/user/month base + per-minute charges). Direct Routing requires an SBC (one-time $2,000-$20,000 or cloud-hosted) plus SIP trunk costs ($15-$25/channel/month from carriers). For most enterprise deployments, Direct Routing provides the lowest per-user PSTN cost at scale.
Can I keep my existing phone numbers when switching to Teams?
Yes, number porting is a standard process when migrating to Microsoft Teams Phone System. You can port existing phone numbers (DIDs) from your current carrier to Microsoft (for Calling Plans), to an Operator Connect carrier, or maintain them with your existing SIP trunk provider (for Direct Routing). Number porting typically takes 2-4 weeks depending on the losing carrier. During migration, calls can be temporarily forwarded to ensure no disruption. EPC Group manages the number porting process as part of every Teams telephony migration to ensure zero downtime.
What happens if the internet goes down with a cloud phone system?
Internet outages affect cloud-based phone systems because calls are routed over IP networks. Mitigation strategies include: redundant internet connections (dual ISP with automatic failover), SD-WAN for intelligent path selection, Survivable Branch Appliances (SBAs) that provide local PSTN connectivity during Teams outage, mobile Teams app over cellular data as a fallback, and call forwarding rules that redirect to mobile phones during outages. For mission-critical environments like hospitals or 911 centers, EPC Group designs architectures with on-premises SBC failover to local PSTN circuits as the ultimate backup.
How long does it take to migrate from a PBX to Microsoft Teams?
A typical PBX-to-Teams migration takes 3-6 months for organizations with 100-1,000 users and 6-12 months for larger enterprises. Key phases include: assessment and planning (3-4 weeks), SBC deployment and SIP trunk configuration (2-4 weeks), auto attendant and call queue design (2-3 weeks), pilot group migration (3-4 weeks), phased production migration (4-12 weeks based on user count), and legacy PBX decommission (2-4 weeks after final migration). EPC Group recommends a parallel operation period where both systems are active to ensure seamless transition with zero disruption to business operations.