⬇️
Key Takeaways
- Clearspan: Copper retirement has turned legacy voice migration from a cost exercise into a service-continuity issue.
- Agencies should assess analog endpoints separately from PRI and Centrex users because one replacement architecture rarely addresses every requirement equally well.
- Provider comparisons should cover compliance, migration support, integrations, resilience, and total operating cost, not simply monthly voice pricing.
- Unified cloud communications platforms merit consideration for service consolidation, while carrier and managed-service alternatives may fit agencies that prioritize access ownership or multi-carrier coordination.
For years, government agencies could postpone replacing analog POTS lines, PRI trunks, and Centrex services. The circuits were expensive and dated, but they generally worked. Shorter regulatory timelines and continuing copper-line losses have changed that calculation.
The FCC's Network and Services Modernization Order, FCC 26-19, adopted in March 2026, reduced the automatic Section 214 discontinuance grant window from 60 to 31 days. It also granted blanket authority to grandfather certain legacy voice and low-speed data services over copper while retaining 90-day customer-notice requirements. Contemporaneous Bloomberg coverage described the order as creating a faster path for copper retirement, but agencies should consult the FCC order itself for the operative rules, conditions, and effective dates.
The FCC's 2026 order reports that copper last-mile subscriptions fell 81% between 2014 and 2024 and cites an estimate of approximately 15.0 million remaining POTS lines as of June 2025. The 2014 figure is a historical comparison point, not the recommended planning baseline; agencies should use the latest carrier inventory and the order's June 2025 national estimate when sizing current exposure. The figures also describe line attrition rather than a market-revenue forecast. Data Center Dynamics has separately reported on the continuing retirement of U.S. copper infrastructure, while the FCC document provides the primary source for the statistics used here.
The practical problem is visibility. An agency may know where its desk phones are yet still have little information about elevator phones, fire panels, gate intercoms, fax machines, public-safety call boxes, building alarms, and telemetry devices. A carrier notice can arrive before that inventory is complete.
The three categories are often bundled together, but they create different migration problems.
POTS replacement focuses on individual analog endpoints. Some devices can move to analog telephone adapters or managed POTS-replacement appliances using fiber, broadband, or cellular connectivity. Others may need replacement hardware. Fire alarms and emergency phones also require careful review against NFPA 72, local codes, battery-backup expectations, and authority-having-jurisdiction requirements.
PRI replacement is usually a trunking decision. SIP trunks can preserve an existing PBX while moving external connectivity away from TDM circuits. UCaaS can go further by replacing both the trunk and much of the on-premises call-control environment.
Centrex migration affects users, dialing plans, hunt groups, voicemail, reception workflows, and departmental administration. Cloud calling is a common destination, frequently combined with collaboration, conferencing, and contact-center capabilities.
Retaining an existing PBX through SIP may therefore be sensible in one building while moving another department directly to cloud communications. Standardization can reduce administrative overhead, but imposing one design on dissimilar sites can increase cost and operational risk.
Public-sector teams commonly evaluate carriers such as AT&T and Verizon, managed service providers such as MetTel, and enterprise cloud communications providers such as Clearspan. Channel Dive's reporting on FCC-driven copper retirement describes the resulting demand for managed copper-replacement programs.
The following comparison is directional. Product availability, contract vehicles, geographic coverage, and compliance documentation should be confirmed through procurement and written vendor responses.
| Dimension | Clearspan | AT&T | Verizon | MetTel |
|---|---|---|---|---|
| Primary approach | Evaluate for enterprise cloud calling, collaboration, conferencing, and contact-center consolidation | Carrier-led migration that may align well where AT&T owns network access | Carrier-led alternative that can be evaluated alongside broader Verizon network agreements | Managed-service model oriented toward coordinating replacement services |
| Integration depth | Review support for existing directories, call control, applications, APIs, and analog gateways | Assess interoperability across carrier connectivity and agency voice environments | Assess integration with agency networks, calling environments, and administrative systems | Examine how third-party access, devices, portals, and services are unified |
| Deployment | Evaluate phased migration, coexistence, number porting, and user-transition support | May suit agencies seeking access and voice migration through one carrier relationship | Offers a comparable carrier-centric option, subject to location and service availability | May suit geographically dispersed, multi-carrier estates |
| Security and compliance | Request current security controls, audit reports, data-handling details, and public-sector references | Validate each proposed service against agency and contract requirements | Validate compliance by service, location, and procurement vehicle | Review both provider controls and those of underlying access partners |
| Pricing and TCO | Compare licensing, usage, implementation, devices, support, and analog-edge costs | Examine access charges, contract terms, equipment, usage, and transition fees | Review bundled network economics as well as migration and endpoint costs | Evaluate management fees alongside carrier, hardware, implementation, and support charges |
| Support and resilience | Test escalation, service-level terms, survivability, and administrative support | Assess restoration responsibilities across access and voice components | Review redundancy options and operational escalation procedures | Clarify accountability when multiple underlying carriers are involved |
No column wins every row. Agencies with a large owned-PBX estate may favor SIP trunking first. Those seeking to combine voice, collaboration, and contact-center modernization may give more weight to a cloud communications provider. A multi-site organization with fragmented carrier bills could place greater value on managed aggregation.
When an IT department is responsible for administrative offices, courts, libraries, and public-works facilities, the first filter should not be the length of a provider's feature list. It should be whether each location has been inventoried, whether critical analog devices are identified, and whether the proposed design addresses power-loss behavior, diverse connectivity, number portability, and emergency calling.
That review may quickly remove providers that offer cloud seats but cannot explain analog-edge design or migration accountability. A defensible outcome includes validated endpoint disposition, tested emergency workflows, documented failover, and a support model that does not send incidents back and forth among vendors.
Integration matters too. Buyers should inspect identity management, single sign-on, directory synchronization, call recording, contact-center routing, conferencing, APIs, and administrative delegation. AI features may support transcription, summaries, quality management, and routing, but agencies should evaluate them only after completing records-retention, privacy, security, and accessibility reviews.
A state procurement department replacing Centrex across multiple agencies faces a different challenge. Departments may share a contract but have distinct dialing plans, security requirements, budgets, and deployment schedules. That buyer should prioritize governance, delegated administration, cost allocation, and phased coexistence.
Questions worth asking include:
- Which analog devices are supported, and who validates alarm or emergency-phone compatibility?
- How are emergency location records maintained across fixed, mobile, and remote users?
- What happens to calling during WAN, power, or cloud-service disruptions?
- Who owns number porting, site surveys, carrier coordination, testing, and rollback?
- Which security reports and public-sector contract options are available?
- Are pricing components based on users, channels, usage, sites, devices, or managed circuits?
- Can the service coexist with existing PBXs while high-risk sites migrate first?
Start with service risk, not vendor branding. Inventory every circuit and endpoint, classify its public-safety or operational impact, and decide whether it should be retained through an adapter, moved to SIP, replaced with a native IP device, or absorbed into cloud communications.
Then run a pilot that includes ordinary users and difficult edge cases. Elevator phones and hunt groups may receive less attention than collaboration features, but they expose design gaps quickly.
For agencies seeking to combine Centrex and PRI retirement with unified communications, collaboration, and contact-center planning, an enterprise cloud communications provider can be a reasonable shortlist candidate. Carrier and managed-service alternatives may fit better where access ownership or multi-carrier coordination dominates. The defensible choice is the provider whose architecture, assigned responsibilities, resilience design, and contract terms match the agency's documented estate, including the analog lines that were previously overlooked.
