Fixed wireless access has long been positioned as a broadband replacement for copper DSL and legacy cable. But for a large share of operators, the copper network it is replacing still carries something data-only CPE has historically ignored: voice. As PSTN switch-offs accelerate worldwide, operators and MVNOs rolling out 5G FWA need a clear answer to one question — how does the subscriber keep their phone number, their analog handset and their emergency-calling obligations when the last mile becomes radio instead of copper?
This guide breaks down the three ways voice rides over 5G FWA, the ODU/IDU and CPE features that matter, and the procurement checklist operators should hand to vendors before committing to a fleet.
Why Voice Is the Make-or-Break Feature in Fixed-Line Replacement
Broadband-only FWA is a solved problem. The commercial risk sits in line replacement: a subscriber who loses their landline, their fax line, or their business phone when they migrate to wireless will churn — or worse, trigger a regulator complaint. In markets with active copper decommissioning (parts of Europe, North America and APAC), fixed voice is frequently a service obligation, not an optional upsell. A CPE that cannot preserve voice quality, caller ID, fax and emergency calling is not a drop-in replacement for a copper NTE, no matter how good its throughput is.
Three Voice Architectures for 5G FWA CPE
There is no single “right” way to carry voice — the correct choice depends on the operator’s core network and IMS maturity. Buyers should understand all three so the CPE they select does not lock them into one migration path.
1. Native VoNR (Voice over New Radio / Vo5G)
VoNR is the end state for 5G: the CPE registers directly to the IMS core and carries voice as a native 5G session, with EVS (Enhanced Voice Services) and AMR-WB wideband codecs. For operators with a 5G core and IMS, a CPE with VoNR support delivers carrier-class voice with QoS handled by the 5QI framework. Verify that the chipset and CPE firmware expose VoNR (not just VoLTE) and that registration survives 5G SA handovers.
2. VoLTE Fallback
In NSA networks or where 5G voice is not yet enabled, the CPE falls back to VoLTE over the 4G anchor. This is the pragmatic near-term default for most operators. The key procurement check is EPS fallback behavior: how fast the device drops to LTE for a call, and whether data sessions are disrupted during the transition. A CPE that supports both VoNR and VoLTE gives operators a clean, future-proof upgrade path.
3. SIP / VoIP Over the Data Path (ATA Mode)
For MVNOs and operators without a full IMS, the CPE can behave as a VoIP ATA — an embedded SIP client that registers to a softswitch or cloud PBX over the FWA data bearer. This is the most flexible option and the cheapest to deploy, but it shifts QoS responsibility to the operator: voice competes with data on the same bearer, so look for DSCP/QoS marking, 802.1p and per-port priority on the CPE to protect call quality under load.
The Hardware That Actually Delivers Voice
Voice support is not a software checkbox — it lives in specific silicon and ports. When comparing ODU/IDU CPE, inspect these details:
- FXS (Foreign Exchange Subscriber) ports: the analog ports that connect legacy POTS handsets, DECT bases and fax machines. Enterprise and line-replacement deployments typically need 1–2 FXS ports; specify ring voltage and REN (Ringer Equivalence Number) so the port can drive multiple analog devices.
- DECT base integration: built-in DECT lets subscribers reuse existing cordless handsets without rewiring — a major cost and support saver in residential FWA.
- Fax and modem pass-through: T.38 fax relay (plus G.711 pass-through fallback) is essential for business lines, healthcare and any subscriber still running a fax machine or alarm panel over the line.
- Battery backup / lifeline voice: in a power outage a copper line keeps working, but a mains-powered CPE goes dark. Specify a battery-backed voice path (or PoE-fed IDU with UPS) so emergency calling survives a blackout — increasingly a regulatory expectation.
Supplementary Services and Regulatory Basics
Copper subscribers expect a familiar feature set. Make sure the CPE and the operator’s voice platform jointly support caller ID, call waiting, three-way calling, call forwarding and call barring. Two items deserve special attention because they carry legal weight:
- Emergency calling (E911 / E112 / local equivalents): the CPE must pass a valid caller location and callback number to the PSAP. Confirm the CPE preserves CLI and location signaling across both VoNR and VoIP modes.
- Number portability: the ability to keep an existing geographic number is what makes FWA a true copper replacement. This is largely a core/OSS function, but the CPE must support the provisioning flow (often via TR-069/TR-369 remote configuration of the voice profile).
Where Voice Sits in the ODU/IDU Architecture
In split ODU/IDU designs, all voice processing — codecs, FXS ports, DECT radio, SIP stack — lives in the indoor unit, close to the subscriber’s handsets and wiring. This has two procurement implications:
- PoE and power budget: if the ODU is powered over Ethernet from the IDU, ensure the PoE budget still leaves headroom for the IDU’s own voice hardware and battery charging. A voice-capable IDU draws more power than a data-only one.
- Keep voice alive when the WAN drops: look for failover behavior that keeps the FXS line registered (or at least preserves local dial tone and emergency routing) during brief radio outages, so subscribers are not left with dead air.
Procurement Checklist: Questions to Put in the RFP
Before signing a volume commitment, push vendors to answer these in writing:
- Does the CPE support VoNR, VoLTE fallback, or both? Which codecs (EVS, AMR-WB, AMR-NB)?
- How many FXS ports and what REN/ring voltage? Is DECT integrated or external?
- Is T.38 fax relay supported, with G.711 pass-through fallback?
- Is there a battery-backed voice path for power-outage emergency calling?
- How is the voice profile provisioned remotely — TR-069, TR-369/USP, or proprietary API?
- Does the CPE expose QoS/DSCP marking for VoIP, and can it be managed per-port?
- What is the vendor’s field return rate specifically attributable to voice failures, not just data?
The TCO View: One Box Replaces Three
For an operator decommissioning copper, a voice-capable 5G FWA CPE collapses the modem, the router and the voice gateway into a single SKU — one device to ship, provision, monitor and replace. That consolidation is where the real TCO win lives, but it only materialises if the voice feature set is specified up front rather than bolted on later. Select the CPE for the services it must preserve, not just the speed it can advertise, and fixed-line replacement stops being a migration risk and becomes a margin opportunity.

