4 ms·

Analog Phones

38 points by DanAtC 4y ago

madengr 4y ago
D13Fd 4y ago
This is a weird article that imagines that businesses skipped straight from analog -> IP. They mostly didn’t. Mid-size and larger businesses had been running digital phones and PBX systems for years and years prior to IP phones.
- don-code 4y ago
  There's an awkward, intermediate step, sort of like what we had with 1G cellular: while the signalling was all digital (but not IP), the actual voice payload was carried on a dynamically-provisioned analog channel. We had Merlins at my parents' store when I was growing up, and an interesting artifact of the analog channel was that some analog data was possible. For instance, we hung a fax off one of the Merlins (14.4k was fine); I likewise got get 33.6k off it when I plugged in my modem, but could never get 56k. In hindsight, that's because 56k actually requires the line to support digital signalling, which the Merlin did not.
- jcrawfordor 4y ago
  This was sort of a terminological failure on my part... When I say analog I am including typical digital PABXs. Now that's somewhat fair because a number of small and medium business "digital" PABXs used digital signaling and analog audio, especially key systems. But there were plenty of entirely digital systems, and of course ISDN had decent popularity in large institutional contexts. I'm not sure what a great term is to encompass all of these systems besides "non-IP." But on the small business end, most businesses are doing just that right now... Going from one or two analog lines to a cloud managed IP solution.
samcheng 4y ago
It seems like "hard" IP phones are becoming obsolete at this point. I definitely haven't included them in any new office I've spun up in the past five years. WFH during the pandemic really sealed the deal - it's not like everyone went around installing new work phones at home. Video conferencing replaced conference phone calls for almost every corporate use case. Consumer business-wise, outbound phone use cases are easily (and better!) handled with a software solution, and inbound phone use cases can be handled with e.g. Twilio or something like Amazon Connect. On the small business side, something like Grasshopper works just fine.
- Nextgrid 4y ago
  This is a huge shame. I wish I could use a hardware phone or at least a SIP client. While there's technically no reason why a computer can't do just as well as a dedicated phone (after all, a phone is just a low-powered computer), in practice, modern computer-based communications software is terrible. Protocols are all proprietary and are often centralized - there is no P2P, not even optionally. This is something Skype used to do brilliantly over a decade ago (on much slower hardware), preferring P2P if possible. The clients themselves are absolute trash. Hardware phones still have CPU speeds measured in megahertz and are faster & more responsive than modern communications software on multi-core, multi-gigahertz CPUs and gigabytes of RAM. Teams is the worst offender here, but even Zoom is not that great. Again, this is a problem that was solved decades ago, I remember having perfect calls on TeamSpeak 2 back in the days on machines much slower than now and sub-megabit DSL connections, and yet it's no longer something I can take for granted nowadays. I can establish and answer a SIP call between 2 hardware phones faster than the Slack takes to load. At least if they were using a standard (or at least documented) protocol I could write my own client, but since the objective is often "growth & engagement" that's not possible either because the annoyances of the official client are considered a feature by the original developer.
ghoul2 4y ago
On a slight tangent: is there a "modern" (single-chip?) landline telephone design available anywhere? Everything I search for ends up being about cellular phones. I find old circuits built around opamps, and thats fine - I just expected to see a single-chip solution handling ring tones, keypad, caller-id etc - but haven't found one. On that topic, is there an (available) DECT-based solution as well?

38 points by DanAtC 4y ago

This is a weird article that imagines that businesses skipped straight from analog -> IP. They mostly didn’t. Mid-size and larger businesses had been running digital phones and PBX systems for years and years prior to IP phones.

don-code 4y ago
There's an awkward, intermediate step, sort of like what we had with 1G cellular: while the signalling was all digital (but not IP), the actual voice payload was carried on a dynamically-provisioned analog channel. We had Merlins at my parents' store when I was growing up, and an interesting artifact of the analog channel was that some analog data was possible. For instance, we hung a fax off one of the Merlins (14.4k was fine); I likewise got get 33.6k off it when I plugged in my modem, but could never get 56k. In hindsight, that's because 56k actually requires the line to support digital signalling, which the Merlin did not.
jcrawfordor 4y ago
This was sort of a terminological failure on my part... When I say analog I am including typical digital PABXs. Now that's somewhat fair because a number of small and medium business "digital" PABXs used digital signaling and analog audio, especially key systems. But there were plenty of entirely digital systems, and of course ISDN had decent popularity in large institutional contexts. I'm not sure what a great term is to encompass all of these systems besides "non-IP." But on the small business end, most businesses are doing just that right now... Going from one or two analog lines to a cloud managed IP solution.

samcheng 4y ago

It seems like "hard" IP phones are becoming obsolete at this point. I definitely haven't included them in any new office I've spun up in the past five years. WFH during the pandemic really sealed the deal - it's not like everyone went around installing new work phones at home. Video conferencing replaced conference phone calls for almost every corporate use case. Consumer business-wise, outbound phone use cases are easily (and better!) handled with a software solution, and inbound phone use cases can be handled with e.g. Twilio or something like Amazon Connect. On the small business side, something like Grasshopper works just fine.

Nextgrid 4y ago
This is a huge shame. I wish I could use a hardware phone or at least a SIP client. While there's technically no reason why a computer can't do just as well as a dedicated phone (after all, a phone is just a low-powered computer), in practice, modern computer-based communications software is terrible. Protocols are all proprietary and are often centralized - there is no P2P, not even optionally. This is something Skype used to do brilliantly over a decade ago (on much slower hardware), preferring P2P if possible. The clients themselves are absolute trash. Hardware phones still have CPU speeds measured in megahertz and are faster & more responsive than modern communications software on multi-core, multi-gigahertz CPUs and gigabytes of RAM. Teams is the worst offender here, but even Zoom is not that great. Again, this is a problem that was solved decades ago, I remember having perfect calls on TeamSpeak 2 back in the days on machines much slower than now and sub-megabit DSL connections, and yet it's no longer something I can take for granted nowadays. I can establish and answer a SIP call between 2 hardware phones faster than the Slack takes to load. At least if they were using a standard (or at least documented) protocol I could write my own client, but since the objective is often "growth & engagement" that's not possible either because the annoyances of the official client are considered a feature by the original developer.

ghoul2 4y ago

On a slight tangent: is there a "modern" (single-chip?) landline telephone design available anywhere? Everything I search for ends up being about cellular phones. I find old circuits built around opamps, and thats fine - I just expected to see a single-chip solution handling ring tones, keypad, caller-id etc - but haven't found one. On that topic, is there an (available) DECT-based solution as well?