Oh, definitely a good example, I'm embarrassed I forgot that! I was part of the core FreePBX development team for a few years (before RasPBX was a thing), and e

Oh, definitely a good example, I'm embarrassed I forgot that! I was part of the core FreePBX development team for a few years (before RasPBX was a thing), and eventually moved my home PBX setup to a Pi 1 running RasPBX, which I used for 4+ years. Sadly, as our usage of the IP phones dwindled (cell phones, texting, and now conference software taking over), my significant other began evicting them from around the house ("too big and ugly"). A couple years ago, my instance was at the point I needed to do some major OS upgrades to it, and considering it was basically my office phone and a cordless left, I ended up retiring the Pi and PBX. Now I just register my last couple phones directly to my VoIP provider. It looks like a Pi 4 can handle "dozens" of simultaneous channels (though depends on codecs used), and that would be my starting point if I got back into doing PBX work or deploying a system today -- though I'd probably run it from an SSD instead of SD card. This is a great example of the benefits of the Pi hardware, too: People don't tolerate PBX downtime. With the Pi, it's incredibly cheap to have hardware for a failover server (try pricing that out on a commercial PBX!), and in an emergency you can run out and buy one locally or have it shipped overnight.