At 9:30 on a Tuesday in March 2024, three managers were standing in my office doorway. The phones in our warehouse had started doing that thing where callers fade out unless you stand on one leg by the window. We'd just upgraded to a top-rated cordless phone system, and it was somehow worse than the eight-year-old system it replaced.

I'm the office administrator for a 140-person wholesale distribution company. I manage roughly $180,000 a year in purchasing across 25 vendors, and I report to both ops and finance. Telecom hardware is one of those "small" categories that becomes a big headache when it fails. So when our old Panasonic DECT phones started dying, I did what any sensible buyer would do: I read six "best cordless phone" roundups.

Every list I read said the same thing. For a budget-friendly DECT 6.0 system, the Panasonic KX-TG3310 was the best cordless phone under $100. It had good call quality, expandable handsets, and call blocking. I ordered four sets. That should have been the end of it.

The Upgrade That Wasn't

Delivery went fine. Setup was easy. Then the complaints started. Static on line one. "Base No Link" messages on line two. A manager in the receiving bay said the handset would ring but as soon as she answered, the call was gone. I did what any purchaser does when the shiny new thing fails: I blamed the product.

I returned the first four boxes and ordered another model from the same best cordless phone article. It had a slightly different model number and a "new and improved" tag. Same problems.

Full disclosure: I'm not an IT person. I'm the person who buys the IT stuff. There's a difference, and that difference was on display for three weeks.

At that point I was out about $1,800 in credit-card holds and return shipping, and I still didn't have working phones.

Two Different Networks

Here's where I need to be honest. Earlier that year, I had upgraded our warehouse Wi-Fi to a router powered by the Qualcomm IPQ4019. I picked it because it handles a lot of devices—802.11ac Wave 2, MU-MIMO, and enough range for our barcode scanners. It's been great. The mistake was assuming that a strong Wi-Fi network meant strong phone coverage.

I finally called a friend from a previous job—he works at the Qualcomm Raleigh office. He's not in procurement, so I expected some good-natured gloating. Instead, he asked a question that stopped me: "What network are the phones on?"

I said, "The phone network?"

He laughed. Then he explained that DECT 6.0 phones use the 1.9 GHz band in the US. They don't run over Wi-Fi. The handset connects to the base unit over DECT, and the base unit connects to your phone system over the LAN. It's a separate wireless network. If the base is sitting on a cheap switch, behind a metal shelf, and sharing a power strip with a printer, no handset will save you.

"You're comparing two different networks," he said. "The IPQ4019 is a Wi-Fi SoC. It's great at what it does. But your cordless phones are their own wireless network."

That conversation changed how I think about office technology. It took me two failed orders and about three weeks to understand that the KX-TG3310 wasn't defective. The network around it was.

What I Actually Changed

We kept the phones. We changed almost everything else. First, we moved the base units out of the metal server closet and closer to the areas where people actually use them. Second, we plugged them into a proper PoE switch with QoS enabled, instead of the old unmanaged switch behind the filing cabinet. Third, we set up VLANs so SIP traffic didn't have to compete with large print jobs and backup uploads.

The Qualcomm IPQ4019 router stayed where it was. That router was never the problem. It does Wi-Fi. The phones don't use Wi-Fi. The two networks are separate, but they both end up in the same Ethernet jack. If the LAN isn't healthy, both suffer.

Once we fixed the LAN, the same handsets worked. Calls stopped dropping. The warehouse coverage came back. The managers stopped visiting my office in groups.

What I'd Do Differently

Everything I'd read about cordless phones told me to compare handsets. My experience says compare the network first, handset second. The conventional wisdom is "buy the best cordless phone and it'll just work." That may have been true in the analog era. It is not true for modern DECT 6.0 and VoIP systems.

So now I use a checklist before any telecom purchase:

  • Walk the space and test the base station placement before buying extra handsets.
  • Check what switch the bases will connect to. Does it support PoE and QoS?
  • Count the devices on that network. A router like the Qualcomm IPQ4019 can handle a lot of Wi-Fi clients, but the switch and uplink also need headroom.
  • Ask whether you're buying a product or a network with a handset attached.

Five minutes of verification beats five days of correction. In my case, it was more like three weeks and a few rounds of return-authorization paperwork. The good news is that the KX-TG3310 is actually a good phone—once you build the right network around it.

If you're shopping for a cordless phone for an office, I'm not going to tell you not to read reviews. Read them. But before you order, look at your network. That's the part the roundups don't cover.

For telecom planning, the article should be read with protocol context in mind: 3GPP TS 38.xxx for radio behavior, IEEE 802.3bt for high-power PoE, ITU-T G.652.D for optical fiber assumptions, insertion loss in dB for link budget, and PIM in dBc for passive RF quality.