Our conference room phone beeped three times, went dark, and showed "Reconnect handset to base." That was the third time that week. I reset the handset, followed the instruction sheet, and it worked for two hours. Then it beeped again.
I'm the office administrator for a 90-person manufacturing company. I manage supplies and equipment ordering—roughly $120k a year across maybe eight vendors. In early 2023, that included replacing cordless phones in the warehouse. The project taught me more about TDK-Lambda power supplies and cables than I expected.
The phone that would not stay reset
The old phones were old enough that the warehouse manager had stopped complaining and just used sticky notes. I ordered a set of DECT cordless phones. The office tech installed them, and within a week, warehouse staff said calls were dropping. Not all calls, but enough that one supervisor started taking messages on his personal cell.
I did what anyone does: I searched "how to reset cordless phone." The manual said to unplug the base, remove the battery from the handset, wait thirty seconds, put the battery back, and let the phone re-register. I followed it exactly. The phone behaved for two days. Then the same error appeared. A second reset lasted an afternoon.
(Note to self: a reset only works when you've fixed what caused the error.)
At the same time, we had installed new workstations in a room behind the warehouse. Each station used a TDK-Lambda CUS250M AC-DC power supply to feed a small monitoring device on the bench. Our engineer asked for TDK-Lambda specifically—she had used them before and trusted them. The name was familiar because TDK makes ferrites and components, but I didn't realize Lambda was part of the TDK group until those boxes arrived.
Then the phone errors started. I blamed the TDK-Lambda power supplies. I even drafted a complaint email with the subject line "TDK lamda noise problem" (I typed "lamda," with an a—I didn't know the official spelling was Lambda until the distributor corrected it).
The distributor asked a better question
The distributor's support person was patient. She didn't argue with my theory. She asked me what cable connected the power supply to the monitoring device.
I said, "The one that came with it."
It did not come with it. I had specified a custom DC extension cable from a third-party seller because adding one to the TDK-Lambda order would cost $28 per workstation, and the third-party version was $11. It was unshielded, it was longer than needed, and it ran along the metal shelf right next to the cordless phone base.
She explained that the problem was probably common-mode noise on the cable. The cable was radiating, the phone base was picking it up, and the handset kept losing its connection. That's why the reset worked temporarily: it forced the handset to re-register, but the noise didn't care. It came right back.
I was skeptical. In my experience, when something fails after a new power supply is installed, the power supply is usually the suspect. But I followed her advice. We ordered clip-on ferrite cores—the kind TDK has made for decades—and snapped one onto the DC cable near the device end. Then I reset the cordless phone one more time. That was around 10 a.m. By the next morning, the phone was still on. I only believed the cable theory after I saw the ferrite fix the problem. A week later, it was still on.
(I really should have taken a photo of that cable before I hid it behind the shelf.)
So the TDK-Lambda power supply was not defective. The phone was not defective. The problem was a $12 cable selected by price alone. I had ignored shielding and routing because I assumed the power supply would clean everything up. That assumption cost us about four days of phone trouble and a little credibility with the warehouse manager.
If your cordless phone keeps resetting
First, resetting a cordless phone is a real troubleshooting step. For our DECT phones, the manual procedure is:
- Unplug the base station from AC power.
- Remove the battery from the handset.
- Wait at least 30 seconds.
- Put the battery back in the handset.
- Plug the base back in.
- Place the handset on the base and let it re-register.
It works. It clears the "Reconnect handset" error. But if the error keeps coming back, the reset isn't your problem. Look at what changed in the environment, not just the device.
People often think a phone interference problem means a power supply is failing. The reality can be the opposite. A power supply that meets its EMC requirements can still have its cable behave like an antenna if the cable is unshielded or routed badly. In our case, the power supply was fine; the cable was the radiator and the phone base was the receiver.
After the distributor's email, I found a TDK-Lambda application note by searching for "TDK power supply Lambda EMC," and it explained the simple stuff I'd never thought about—cable placement, ferrite clamps, grounding. If you're searching "how to reset cordless phone" because the same error keeps returning, try the reset. Then check the cables near the base. Is there a long DC cable lying across the same shelf? Move it. Add a ferrite clamp if you can. That might be your fix.
As of January 2025, the TDK-Lambda CUS250M units in our building are still running. The one on my bench has been fine since day one. What wasn't fine was my decision-making about cables. That's a reminder I keep in my procurement notes: the most expensive component isn't always the weak link. Sometimes it's the $11 piece of wire.
