A childcare center in Chicago's western suburbs called after a storm. The lights came back, the internet came back, and the phones did not. Their system was a Panasonic KX-NS700 — a common small-business PBX, and a good one — and it was completely dead. No lights on the system unit, no dial tone on any handset, and a front desk that takes calls from parents all day suddenly couldn't.
It's an ordinary failure, and the recovery has a shape that repeats: some of the system was gone for good, more of it was fine than you'd expect, and the part that hurt most was the part nobody had backed up.
What actually failed
The KX-NS700 is a modular system. There's a main system unit that holds the CPU and the programming, and there are cards that plug into it — station cards that connect the desk phones, trunk cards for outside lines, and so on. When we opened it up, the system unit itself was dead. But the digital station card, a DLC16 (Panasonic part KX-NS5172), tested fine. That card is what all sixteen digital handset ports hang off of, and it's not cheap to replace, so it mattered that it survived.
We had a tested replacement KX-NS700 system unit in stock. We installed it, moved their DLC16 card into it, and reconnected the existing station wiring and handsets. Physically, the system was back within the first visit.
What was not recoverable
The programming. Extensions, names, ring groups, the auto-attendant greetings, voicemail boxes and their messages, time-of-day routing — all of that lives on the system unit, and the system unit was the thing that died. There was no backup on hand, so there was nothing to restore. We rebuilt it from scratch: extension plan, voicemail, ring groups, greetings, and then reprogrammed 14 handsets one by one so keys and displays matched what the staff were used to.
That is where the hours went. Across two visits it was roughly four hours on-site in total. The hardware swap was the fast part; re-entering a small business's call flow from memory and interviews is the slow part.
The lesson, in one sentence
Keep a current backup of your phone system's programming somewhere that is not inside the phone system.
The NS700 supports backing up its configuration to an SD card, and that backup can be restored onto a replacement unit. If a current one had existed, this would have been one visit: swap the unit, move the card, restore, done. The greetings, mailboxes, and ring groups would have come back exactly as they were. Instead the staff had to describe how their phones used to work while their phones weren't working, which is not the best time to be asked.
If you have a Panasonic system and don't know when it was last backed up, that is the thing to fix this week. It's a small job that pays for itself the first time you need it.
Which parts tend to survive a surge
Every event is different, but there is a pattern to what we see after storms and power problems:
- Station cards, trunk cards, and handsets are often fine. They're on the far side of the system's own power and protection, and the failure tends to stop at the main board.
- Power supplies frequently survive, or fail in an obvious way that's cheap to fix.
- The main board or CPU — the system unit itself — is the most likely casualty, and it's the part that carries your configuration.
That's backwards from what you'd want: the component that carries the irreplaceable part is the one most likely to go. It's the argument for the backup, and for not discarding the cabinet before someone tests the cards.
Protect the KSU
The system unit (some people still call it the KSU, from older key systems) should be on a proper surge protector, and ideally on a small UPS — not so much to ride through a long outage as to keep dirty power and the leading edge of a surge away from the board. A UPS with decent surge suppression is cheap next to what happened here. If you still have analog trunks entering on copper, surge can come in that way too.
What to check first
If your Panasonic system goes quiet after a storm, before you call anyone:
- Power. Is the system unit's power light on? Is the outlet live? Has a breaker or the surge protector tripped?
- The obvious reset. Power the unit off, wait, power it back on. Note whether any lights come up at all.
- One handset. Do any handsets show anything on the display? A blank display everywhere points at the system unit; some working and some not points at a card or wiring.
- The internet. If your trunks are SIP, confirm the router and internet are actually back — a dead router looks a lot like a dead phone system.
- Backups. Find out whether an SD-card backup exists and where it is. Even if you can't restore it yourself, knowing it exists changes what the recovery looks like.
- Don't discard anything. Cards and handsets should be tested before anything is replaced.
Repair it, or move to hosted VoIP?
Every owner asks this in the middle of an outage. The honest answer: it depends on the building, not on the age of the equipment.
We install and support both on-premises systems like the NS700 and hosted VoIP. The decision has less to do with "old versus new" and more to do with:
- How many handsets you have and whether they're digital sets that only work with the PBX, or IP phones that could move to a hosted service.
- What your wiring looks like. Digital handsets run on ordinary station wiring; IP phones need Ethernet to every desk. If the desks aren't cabled for data, that's real cost.
- How the desk is staffed. A single front desk that needs to ring, hold, transfer, and page reliably is well served by a small PBX. A team that's split across locations or works from home is usually better served by hosted.
If the hardware is repairable and the building is wired for it, repairing a system like this one is a perfectly good decision — especially with a backup in place going forward. If you're already fighting the wiring, or the staff are rarely at the desks, the outage is a reasonable moment to make the move.
Either way, back up the programming. That's the part nobody regrets.