Fax, POS & ATM Lines: Migrating Off Copper POTS

The last copper holdouts: fax, POS, and ATM

When facilities and IT teams inventory their copper lines, voice and life-safety circuits get the attention. But there are other analog endpoints discovered during that inventory — and they’re frequently the ones that fail first when copper gets shut down:

• Fax machines — still the default for signed documents, healthcare records, legal paperwork and order confirmations in industries where a faxed page is the system of record.
• Point-of-Sale (POS) terminals — older and backup payment terminals that dial out to authorize card transactions over an analog line.
• ATMs — cash machines that connect to the transaction processor over a dial-up modem.

What these three share is the thing that makes them fragile: they don’t carry a voice — they carry critical data over modem tones. And modem data is far less forgiving of the network changes that come with copper retirement.

Why data endpoints break when copper retires

The FCC is accelerating copper decommissioning nationwide. While that plays out, the copper lines that remain keep getting more expensive and less supported.

For a person on a phone call, a little latency or a brief dropout is annoying but survivable. For a fax, a POS swipe, or an ATM transaction, it isn’t:

• Modem handshakes are timing-sensitive. Fax and POS/ATM modems negotiate a connection with precise tones. Jitter, latency, and packet loss — normal characteristics of a generic VoIP path — corrupt that handshake, producing failed faxes and dropped authorizations.
• A “dropped packet” can mean a declined sale. A voice call glitches and recovers. A card authorization that times out mid-transaction fails — and at the register that’s a lost sale or a frustrated customer.
• Compression and codecs mangle data. VoIP codecs tuned for human speech can distort the modem tones that fax machines and payment terminals depend on, even when voice sounds fine on the same line.

This is why dropping a fax line or a POS terminal onto a cheap VoIP adapter so often “works in the demo” and then fails in production — generic VoIP is well documented as unreliable for fax and modem data. The line carries a dial tone — but not clean data.

What’s actually at risk

• Compliance and records. In healthcare and legal settings, fax is still a documented, auditable channel. A fax line that silently fails breaks a workflow people assume is reliable.
• Revenue at the register. Backup and dial-up POS terminals are the fallback when the primary network is down, and telephone-based payment card data carries its own compliance requirements. If that fallback is sitting on dead copper, the “backup” is an illusion.
• Cash access and uptime. An ATM that can’t reach its processor can’t dispense — and off-premise units are exactly the ones most likely to be on aging analog lines in hard-to-service locations.

The compliant path: a drop-in POTS Replacement

DataRemote’s POTS IN A BOX® replaces the copper landline feeding the fax, POS terminal, or ATM with an enterprise-grade broadband connection — while keeping the existing analog device exactly as it is.

Because the device keeps the original analog interface and carries the modem data over a managed cellular path, the fax keeps faxing, the terminal keeps authorizing, and the ATM keeps dispensing — the copper underneath is simply gone.

Appliances like the 90X1 and 90X2 provide multiple RJ-11 FXS ports for exactly this kind of multi-line data migration, and the plug-and-play VAB-1 is a fit for single-line fax or POS replacements — see the full POTS IN A BOX® lineup to compare options. Every appliance is provisioned and monitored through the Ara platform, so IT teams get line-status alerts the moment a fax, POS, or ATM connection drops.

What each endpoint actually needs — and how to prove it

The most common migration mistake is testing the wrong thing. A technician picks up the line, hears a dial tone, and marks the cutover complete. But dial tone is a voice test, and none of these three devices makes a voice call. Each one needs its own acceptance test, run against the real destination it talks to in production:

Endpoint	What it actually needs	How to verify before you consider it done
Fax machine	A clean modem-tone path with consistent timing end to end	Send a multi-page document to a real destination and confirm every page arrives complete and legible — not just that the transmission “connected”
POS terminal (dial/backup)	A fast, reliable handshake with the payment processor	Run a live test authorization and a batch settlement, since the two use the connection differently
ATM	A sustained modem session for the full transaction	Complete an end-to-end cycle — balance inquiry plus an actual dispense — rather than confirming the unit dials out
Analog modem / building controls	Continuous, supervised data with no silent drop	Confirm the host system sees the device and that a deliberately induced fault raises an alert

Two habits make this go smoothly. First, test at the busiest hour rather than after close: a path that behaves on an idle network may not behave under load. Second, keep the copper line active in parallel for a short overlap where the carrier still allows it, so a failed acceptance test is an inconvenience instead of an outage.

Why “it worked yesterday” isn’t reassurance

Analog data endpoints tend to fail gradually rather than all at once, which is what makes them so easy to under-manage. A fax that loses one page in twenty, or a terminal that declines one transaction in fifty, rarely gets escalated as a network problem — it gets written off as a paper jam or a bad card. By the time the pattern is recognized as a connectivity fault, the workflow has been quietly unreliable for weeks.

This is the strongest practical argument for migrating these lines onto a managed, monitored path rather than the cheapest one available. When each port’s status is visible in a platform like Ara, a degrading line announces itself as an alert. On a copper line — or on an unmonitored VoIP adapter — the same degradation is invisible until someone happens to correlate a stack of small failures.

It is also why the migration order matters. Fax, POS and ATM lines are frequently treated as the low-priority tail of a POTS project, behind fire panels and elevator phones. They should be: life-safety comes first. But they should not be treated as afterthoughts, because they are the endpoints most likely to be quietly broken by a well-intentioned VoIP swap that nobody tested with real data.

What to do before your wire center shuts down

1. Inventory every data line, not just voice. Walk the building for fax machines, dial-up and backup POS terminals, and ATMs — and identify the POTS line behind each one.
2. Flag the modem endpoints. These are the lines most likely to fail on a generic VoIP swap, so they need a data-capable replacement from the start.
3. Migrate before the deadline, not after the outage. Wire-center shutdowns are scheduled — but once copper is cut, the line is gone. Get ahead of the notice instead of losing data or sales.

For the regulatory timeline driving these deadlines, see our guide to the FCC’s 2025 copper retirement rules, and for a broader migration primer read the complete guide to POTS line replacement. Retailers migrating POS and back-office lines can also see how POTS IN A BOX® transforms retail communications.