Comparing live pricing and terms from 400+ carriers and platforms
Ohio multi-site plants, warehouses, and offices: a copper or POTS notice is not a seat-count problem. We build one analog register across sites, split fire and elevator from people phones, and compete compliant replacements—contracts in your name.
The letter lands. Someone asks, “Can’t we just put these on VoIP?” That instinct fixes the office phones and gambles the certificate of occupancy.
Buckeye’s line on this is simple: the copper notice is 90 days; the fire panel is not a VoIP seat. We inventory every remaining analog pair by site and function, split office voice from life-safety and specialty endpoints, then replace what can move before the window closes—as an owner-led advisor since 2003, not a box vendor and not the fire contractor.
This page is the multi-site walkthrough. For a general Ohio POTS / analog replacement overview, see POTS replacement in Ohio. Here we stay on life-safety sequencing, the estate register, and what to do when Site A gets a notice and Site B has not.
The plant that feeds those pairs is leaving, getting harder to support, or both. Rates and lead times usually get worse before dial tone dies. The notice is a project clock, not an IT ticket.
In plain English, carriers use different labels—grandfathering, discontinuance, facility retirement—but the buyer outcome is the same: you cannot assume those analog lines will be cheap, supported, or available on your timeline. Read your letter for the date you must act and which telephone numbers / facilities are in scope. Do not invent certainty from a blog post; verify the wording on your notice and with counsel if the stakes are high.
Ohio multi-site note: notices follow wire centers and carrier plant, not your org chart. One warehouse can get a letter while the plant across town on a different wire center stays quiet for months. Treat the first notice as a signal to inventory every other address on that carrier’s copper estate—not as proof the rest of the company is safe.
Service may still work while pricing and support degrade. Same compliance problem on a slower clock.
A hard date is coming. Procurement, AHJ, and elevator vendor calendars have to fit inside it.
Site A’s letter is an early warning for Site B on the same copper plant. Build one register, not fourteen separate scrambles.
Desk VoIP and generic ATAs fail the life-safety conversation. Supervision, listing, pathway, power, and the AHJ are the tests—not call quality on the sales floor.
Usual endpoints that confuse inventories: fire DACTs, elevator emergency phones, burglar/alarm dialers, plus specialty fax, gate, postage, and M2M lines that share a bill with people phones. They share copper. They do not share a replacement.
| Office voice | Life-safety & specialty analog | |
|---|---|---|
| Examples | Desk phones, hunt groups, auto-attendants | Fire DACT, elevator phone, area of refuge, alarm dialer |
| Typical path | Hosted VoIP / SIP / Teams Phone | Listed cellular or dual-path; purpose-built POTS replacement / MFVN-class where required |
| Who signs off | IT / ops | AHJ + monitoring company + elevator / fire contractor |
| Cutover rule | Port and train | Dual-run, test, document—then release copper |
The phones people talk on usually move to hosted voice, SIP, or Teams Phone. Port numbers cleanly. Check network readiness (bandwidth, QoS, failover) without turning this into a feature list. That workstream can run in parallel with life-safety—it cannot replace it. See hosted voice & UCaaS and, lightly, business internet when the WAN is the constraint.
Categories only—not a product catalog: listed cellular / dual-path communicators; purpose-built POTS replacement or analog emulation (MFVN-class where the AHJ requires it); panel upgrades where the approved path is IP-native. Before copper cut: AHJ, monitoring company, and elevator vendor must be in the loop. Dual-run, test, and document. Buckeye will not put a fire panel on RingCentral, Teams Phone, or any other office voice platform, and we do not claim hosted VoIP is NFPA 72.
Shopping adapters without a register is how estates buy the wrong seats. One page across plants, offices, and warehouses is the control document.
Fields that belong on the register: site address; telephone number; demarc / closet notes; endpoint type; who owns the device (facilities vs security vendor); monitoring account; last inspection; carrier of the copper pair; monthly cost. Rank by risk: life-safety first, business-critical next, convenience last.
How Buckeye starts: send a few invoices per carrier—often three is enough to begin—and we turn them into one estate page. That ties to the multi-site operating model. Nobody needs a perfect CMDB on day one; they need every RJ11 job labeled before anyone orders seats.
Ninety days is often the customer-notice floor under copper-retirement framing—not a comfortable runway for life-safety. Start earlier when you can; triage hard when the letter already arrived.
Every analog line by site and function. Nothing assumed from the carrier notice alone.
Office voice vs life-safety vs specialty. Rank life-safety first.
Get approval paths moving before you buy hardware for the panel.
Compete replacement categories and carriers address by address.
Dual-run, document, then cut copper so it stops billing.
If the notice already arrived: do not bulk-order ATAs. Triage life-safety first. Parallel billing through a dual-run is usually cheaper than a failed inspection—conceptually and operationally. We will not invent dollar claims here.
Independent advisor in Columbus since 2003. Jonathan Eubanks still takes the first call. We own no network and no fire truck.
Invoices and a demarc walk become one page. Every pair gets a job.
Compare approaches and platforms that actually serve each address. Not the same quote twice.
Project-manage the cutover. Remain the escalation path after. You sign in your name.
Facilities owns the panel. Security owns the monitoring account. IT owns the WAN. The elevator vendor owns the car phone. Procurement owns the contract. Nobody owns the estate until you name them on a register.
That split is why multi-site copper projects stall. A 90-day letter arrives at one warehouse. IT opens a VoIP quote. Facilities forwards the letter to the fire vendor. The fire vendor waits on the AHJ. The AHJ waits on a listed path. Meanwhile another plant on the same carrier’s copper plant has not received a letter yet and assumes it is fine. Buckeye’s job is to force the register first, then sequence the workstreams so office voice does not steal the calendar from life-safety.
We are not the Authority Having Jurisdiction and we do not install the fire panel or the elevator phone. We will orchestrate carrier and platform options, keep contracts in your name, and stay through parallel test and copper release. Licensed fire and elevator contractors do the listed work. Your AHJ signs off. Pretending otherwise is how buyers get a polished VoIP cutover and a failed inspection.
If you already bought ATAs for every pair, stop and reclassify before you cut copper. ATAs that are fine for a postage meter are not a life-safety strategy. If the letter is already inside 90 days, triage: life-safety paths and AHJ outreach this week; office voice on a parallel track; convenience lines last. Parallel billing through a dual-run is usually cheaper than gambling the certificate of occupancy.
Cross-link discipline matters here. Use the general POTS replacement page for the three-way estate split. Use this page when the buyer moment is multi-site life-safety under a notice clock. Use multi-site when the pain is inventory ownership across all services, not only analog.
Book a call with Jonathan, or email the carrier letter and a few analog invoices. No deck, no discovery engagement, no obligation.