Revive a Dead Payphone with a Raspberry Pi Zero 2 W: Full Build Walkthrough

To turn an old payphone into a working phone with a Raspberry Pi, gut the original electronics but keep the handset and hook switch, mount a Raspberry Pi Zero 2 W inside the case, wire the hook switch and keypad to GPIO pins, route handset audio through a small USB or I2S sound interface, and run a SIP softphone (Baresip, PJSIP, or Linphone) that registers with a VoIP provider or a self-hosted PBX such as Asterisk or FreePBX. The Pi handles call setup, audio routing, and ringer control; the original chassis just becomes a beautiful shell.

The appeal of payphone revival and who actually attempts it

Payphone conversion projects have been quietly building momentum since 2023, and as of 2026 the surplus market is still flooded with decommissioned Western Electric, Protel, and GTE units from the 1980s and 1990s. A working chrome Bell System single-slot phone listed for $40 in 2019 now sells for $90 to $180 on eBay and at hamfests, and the supply of rough "needs work" units in the $30 to $60 range is the sweet spot for makers. The appeal is twofold. First, the mechanical engineering is gorgeous: the hook switch alone is an over-engineered armored micro-switch built to survive thousands of cycles a day in subway stations and truck stops, and the handset is a piece of acoustic design that consumer cordless phones never matched. Second, the build is a beginner-to-intermediate electronics project that produces a real, useful object — a working phone that prank-calls your friends or answers your home VoIP line — rather than a blinking-LED novelty.

The community is split between three camps. The first wants pure aesthetic restoration with a Pi only as a hidden controller; the handset works, the keypad dials, and the coin slot is mechanical theater. The second camp builds smart-assistant phones: ask the handset a question, get a synthesized answer from a local LLM or a cloud assistant. The third camp builds dedicated security or family lines — the phone hangs in the kitchen, registers to a family SIP trunk, and rings at scheduled times. All three flavors share the same hardware backbone. The reason the Raspberry Pi Zero 2 W became the default choice in 2023 and remains the right pick in 2026 is documented in the Raspberry Pi product brief: a 1 GHz quad-core Cortex-A53, 512 MB of LPDDR2 RAM, and 2.4 GHz Wi-Fi all on a 65 mm × 30 mm board that slips behind the original PCB cradle in almost every payphone chassis ever made.

This walkthrough is editorial synthesis aimed at people who have soldered before, can read a GPIO diagram, and are comfortable with a Linux shell — but you don't need RF engineering background or a CCNA. The trickiest parts are mechanical (mounting and grounding) and acoustic (handset impedance and bias), and both are solvable with cheap parts.

What you'll need: the short checklist

Before you spend an evening tearing the housing apart, line up these eight categories of parts and tools. Skip any one of them and you'll stall halfway through:

• A donor payphone with intact handset, hook switch, and keypad. Single-slot Western Electric 1D2 and Protel 8000-series are the most common 2026 finds.
• A Raspberry Pi Zero 2 W or a Zero W starter bundle such as the Vilros Raspberry Pi Zero W Basic Starter Kit for the case, power adapter, and microSD card.
• A class A2 microSD card, 16 GB minimum; an SSD like the Crucial BX500 1TB SATA SSD over USB is overkill for the phone itself but useful if you intend to run a local PBX, call recordings, or a small voicemail archive on the same box.
• A USB sound interface or I2S audio HAT. Cheap CM108-based USB dongles work; for cleaner audio, a WM8960 or PCM5102 I2S HAT is preferred.
• A USB microphone for setup, calibration, and testing — a desk mic like the Logitech Blue Yeti USB Microphone makes A/B comparison against the handset trivially easy.
• A small 5 V 2.5 A power supply. The Pi Zero 2 W draws under 1 A even under SIP load, but transient current spikes during Wi-Fi association are real.
• A SIP account: either a commercial provider (VoIP.ms, Twilio Programmable Voice, Anveo) or a self-hosted Asterisk/FreePBX/3CX instance on your LAN.
• Hand tools: a fine soldering iron, hookup wire in three colors, heat shrink, and a multimeter. A logic analyzer helps but is not required.

Key takeaways

• The Pi Zero 2 W's quad-core SoC and tiny footprint make it the default 2026 brain for payphone conversions; the original Zero W still works for call-only builds but struggles with concurrent SIP plus wake-word.
• Reuse the handset and hook switch; treat the keypad as a GPIO matrix; treat the coin mechanism as cosmetic unless you want a software-defined unlock.
• Audio is the hard problem. Plan for a USB or I2S sound card, bias the handset mic correctly, and budget time for echo and impedance tuning.
• SIP over Wi-Fi works inside a metal case if you route the antenna near a slot or opening, or run an external antenna pigtail.
• Thermals are not usually an issue at idle and call load, but ventilation and clean cable routing inside a sealed enclosure prevent intermittent reboots.
• Budget $80 to $150 in parts plus the donor phone, and roughly 6 to 10 hours for a first build.

Why the Pi Zero 2 W fits a payphone enclosure better than larger boards

The internal cavity of a typical single-slot payphone is generous by hobby-electronics standards, but the mounting points and the metal cradle that held the original electromechanical PCB constrain board choice in unobvious ways. A full-size Raspberry Pi 5 or 4 fits dimensionally but creates two real problems. First, the GPIO header sits perpendicular to the case wall, which means ribbon cables have to wrap awkwardly around the keypad PCB. Second, the Pi 5's 5 V 5 A USB-C demand is more than most repurposed wall warts will deliver cleanly, and the board's higher idle draw produces heat that the steel chassis happily traps. Per the Raspberry Pi product page, the Zero 2 W's 65 mm × 30 mm footprint and lower thermal envelope sidestep both issues, and the integrated 2.4 GHz Wi-Fi means there's nothing extra to mount.

A Pi 3 A+ or 4 model B compute module is a viable alternative if you intend to run a local assistant alongside the SIP stack — running a quantized small language model on a Zero 2 W is possible but slow, while a Pi 5 with 8 GB can host a 3B-parameter model with quality voice latency. For the basic "make and receive calls" project, the Zero 2 W's quad Cortex-A53 at 1 GHz is comfortably enough headroom: a Baresip or PJSIP softphone with the Opus codec uses roughly 5–15 percent of one core on this class of chip during an active call, leaving plenty of slack for ringer logic, GPIO polling, and an SSH session for debugging.

The form-factor argument also matters for repairs. Field-stripping a payphone to swap a dead Pi takes ten minutes if the board is on standoffs aligned with the original PCB holes. If you used a Pi 4 with a custom mounting bracket epoxied to the case, it takes an hour and risks the chassis paint.

Bill of materials table

A representative bill of materials for a Zero 2 W payphone conversion in mid-2026, with current SpecPicks featured SKUs noted where relevant. Prices reflect typical US street pricing as of June 2026 and may vary.

Donor payphone costs vary widely. A working chrome Western Electric 1D2 with original handset and keypad runs $90 to $180 on eBay in 2026; a rough-condition shell with intact mechanicals can be had for $30 to $60. Total project budget for a first build, excluding tools you already own, lands between $80 and $250.

How do you wire the handset hook, keypad, and audio to the Pi?

Three subsystems need attention: the hook switch, the keypad matrix, and the audio path. The hook switch is the easiest. Original payphone hook switches are armored SPDT or DPDT switches rated for the 48 V loop current of the analog phone network. For a Pi build, you only need one pole. Connect one terminal to a GPIO pin (GPIO 17 is convenient because it's far from the I2C and SPI pins you might use later), the other to ground, and configure the pin as an input with the internal pull-up enabled. When the handset lifts, the switch opens and the pin reads high; when it sits in the cradle, the pin reads low. Debounce in software with a 30–50 ms ignore window; the mechanical switch is clean but the long original wire runs can pick up induced noise. The Raspberry Pi documentation covers GPIO configuration in raspi-gpio and the gpiozero Python library, both of which handle pull-up and edge detection cleanly.

The keypad is more interesting. A standard 12-key telephone keypad in a payphone is wired as a 4 × 3 matrix, with each key bridging one row line to one column line through a contact pad. You scan the matrix by driving the columns one at a time and reading the rows. Seven GPIO pins handle the whole keypad: four columns as outputs, three rows as inputs with pull-downs. The Adafruit Learning System publishes a clear walkthrough of matrix scanning for telephone keypads at the Adafruit Learn site under their "Matrix Keypad" tutorials, including code samples in CircuitPython and bare GPIO. A clean scan loop runs at 100 Hz and consumes negligible CPU. Map each key to a DTMF tone in software using a small Python or C wrapper around dtmf generation, or feed the scan results directly to the SIP softphone as in-band DTMF events.

Audio is where most first-time builds get bogged down. The original handset microphone in a Western Electric payphone is a carbon button mic that expects a DC bias current; modern electret and MEMS replacements expect a small bias voltage but no current. If you keep the original carbon mic, you need a small bias circuit — a 4.7k resistor from 5 V to the mic, with a 10 μF DC-blocking capacitor on the signal side — feeding a USB sound card's mic input. If you replace the carbon mic with a $2 electret capsule, most USB sound cards provide bias on the mic ring automatically. Either way, plan for a USB sound interface or an I2S HAT; the Pi Zero 2 W has no audio output and no analog input.

For output, the original handset speaker is a low-impedance dynamic driver, typically 50–150 Ω. A small Class D amplifier between the USB sound card's line out and the handset speaker delivers clean audio. The PAM8403 board, available for under $3, works fine; set the gain conservatively, because over-driving a vintage handset speaker produces a tinny, distorted sound that will ruin every call.

How do you make and receive calls over SIP/VoIP?

The software stack on the Pi is conceptually simple. Install Raspberry Pi OS Lite (a 32-bit Bookworm or 64-bit Bookworm image works), update, and install a SIP client. Three good choices as of 2026: Baresip (command-line, scriptable, low memory), PJSIP via the pjsua CLI (mature, well-documented), or Linphone (more user-friendly, larger footprint). Baresip is the default community pick for headless payphone builds because it consumes about 12 MB of RAM at idle and binds cleanly to a specific ALSA device.

Configure the softphone with credentials from a SIP provider. For a US-based build in 2026, VoIP.ms is the most popular choice for hobbyists: an account costs around $0.85 per month for the DID plus per-minute call rates of $0.009 outbound to the US. Twilio Programmable Voice is more expensive but better-documented. For self-hosters, FreePBX on an old laptop or a separate Raspberry Pi 4 gives you full PBX features (extensions, voicemail, ring groups) without per-minute fees. Whichever you pick, the SIP credentials go into the softphone's config file along with the ALSA device name for your USB sound card.

The integration glue between the GPIO events and the softphone is a small Python script. When the hook switch goes high (off-hook), the script sends a command to the softphone to seize the line and start collecting DTMF. As the user presses keys on the matrix keypad, the script either sends DTMF tones in-band or buffers digits and sends a single dial command when the user pauses for two seconds. When the hook switch goes low (on-hook), the script sends hangup. For incoming calls, the script monitors the softphone's event stream; when an INVITE arrives, it triggers the ringer GPIO (driving the original mechanical bell through a relay or MOSFET, or playing a synthesized ring tone through the handset speaker if the hook is up).

A complete reference daemon in Python lands under 200 lines. Several open-source projects on GitHub provide drop-in starting points; search for "raspberry pi payphone baresip" and you'll find at least three active repos as of 2026.

Power, heat, and reliability inside a metal enclosure

Steel and aluminum payphone enclosures present three reliability risks. The first is Wi-Fi attenuation. A Pi Zero 2 W's PCB antenna inside a sealed steel cabinet loses roughly 10 to 20 dB of signal strength, which often translates to dropped associations or intermittent SIP registration timeouts. The fix is one of three: position the Pi near a coin return slot or handset port where the antenna can "see" outside, run an external antenna pigtail through the back of the cabinet to a small flat antenna, or step up to a Pi with U.FL connectors. For most builds, slot placement is enough.

The second risk is heat. Per the Raspberry Pi documentation, the Zero 2 W's BCM2710A1 SoC throttles at 80 °C, and the chip idles at roughly 50 °C in still air at room temperature. A SIP call adds 3 to 6 °C; a sealed payphone in a hot kitchen can push that to 70 °C. The fix is a 5 mm aluminum heatsink on the SoC (under $2) and at least one ventilation slot. Some builders cut a 30 mm fan opening in the back panel and add a quiet Noctua NF-A4x10 5 V fan; this is overkill for call-only loads but recommended if you plan to run a local LLM or voice assistant.

The third risk is power. The original payphone power supply (if any survives) is rarely usable; replace it with a quality 5 V 2.5 A regulated brick. Cheap unbranded supplies cause Pi Zero 2 W under-voltage warnings (visible as the yellow lightning bolt in dmesg) under transient Wi-Fi current spikes, and the resulting brownouts corrupt SD cards over weeks of operation. The official Raspberry Pi power supply or any reputable USB-C adapter rated for 5 V 3 A is cheap insurance. If you plan to leave the phone running 24/7, also enable read-only root or use an overlay filesystem to extend SD card life — easier still, boot from USB if your USB sound card and a small USB SSD share a hub.

Common mistakes and how to avoid them

Five mistakes account for the majority of first-build failures. The single most-missed step is grounding. The Pi GPIO ground, the USB sound card ground, the handset shield, and any external relay coil ground all need a common reference. Skipping a single ground wire produces hum on the audio path, false hook-switch triggers, or both. Star-ground every subsystem back to a single point on the Pi's 0 V rail.

The second mistake is using an underpowered or wrong-impedance speaker driver. A Class A op-amp running off 5 V drives a 50 Ω handset speaker poorly; a small Class D amp does the job for $3. Test the audio path with the Logitech Blue Yeti USB Microphone plugged into the Pi's USB and the original handset speaker on the output before you ever touch SIP. If the audio chain works for a recorded loopback, it'll work for a call.

The third mistake is not debouncing the hook switch in software. Mechanical switches, especially decades-old ones, produce 5 to 30 ms of contact chatter. Without debounce, your softphone receives an off-hook/on-hook event sequence in 20 ms and either dials twice or hangs up immediately.

The fourth mistake is in-band versus out-of-band DTMF confusion. SIP providers vary in whether they accept DTMF digits inside the RTP audio stream or as separate SIP INFO messages. If your softphone is configured for SIP INFO and the provider expects RFC 2833 RTP, the digits never reach the called party. Check your provider's docs, then set the softphone's dtmf_mode accordingly. Baresip's default is RFC 2833, which works with most US providers including VoIP.ms.

The fifth mistake is over-engineering the coin slot. Some builders spend two weekends building a coin-detection circuit and an Asterisk dial plan that requires "quarters" before unlocking a call. By the time it works, the novelty has worn off. Treat the coin mechanism as cosmetic, or wire it as a single GPIO-triggered "fun mode" toggle, and move on.

When not to do this build

Not every household needs a working payphone. If your goal is a desk phone for SIP calls, a standard SIP handset like a Grandstream GXP1610 or a refurbished Polycom IP 335 costs $25 to $45 and gives you better audio out of the box. If your goal is a smart-assistant phone with a wake word and an LLM backend, a Pi 5 with 8 GB and a proper microphone array is a better hardware choice than a Pi Zero 2 W in a sealed metal box. If you don't already have a SIP account or a willingness to learn the basics of telephony — RTP, SIP registration, NAT traversal — the project will frustrate you halfway through.

The right buyer for this build is someone who wants the aesthetic and the maker satisfaction, has a few weekends to spend, and treats the resulting phone as both an art object and a working tool. If that sounds tedious rather than fun, buy a desk SIP phone and a vintage payphone shell separately; mount them as a sculpture and skip the wiring.

Bottom line

A Raspberry Pi Zero 2 W payphone revival is a 6-to-10-hour weekend build that delivers a real, working phone in a beautiful vintage chassis for $80 to $250 in parts on top of the donor phone. The hard parts are mechanical (mounting, grounding, antenna placement) and acoustic (mic bias, speaker drive, echo); the software stack of Raspberry Pi OS plus Baresip or PJSIP is well-trodden and documented. For a first build, start with the Vilros Raspberry Pi Zero W Starter Kit for the board, power, and SD card, add a $6 USB sound dongle, and pick a VoIP provider before you start writing code. The result is the rare maker project that family members actually use.

Related guides

• See our retro PC parts buying guide for vintage cases and PSUs.
• Browse all Raspberry Pi projects for similar builds.
• For SIP server hosting, see self-hosted PBX builds on small SBCs.
• For a wake-word smart assistant variant, compare Pi 5 vs Pi Zero 2 W for voice projects.
• Need audio reference gear? Read our USB microphone roundup.

Citations and sources

• Raspberry Pi Zero 2 W product page — quad-core specs and physical dimensions.
• Adafruit Learning System — matrix keypad and GPIO tutorials cited throughout.
• Raspberry Pi documentation — GPIO, power, and thermal guidance referenced in wiring and reliability sections.

This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.