FusionPBX automation
The problem
Running SIP PBX systems for multiple tenants by hand doesn't scale past a handful of customers — every new tenant, every backup, every health check is another chance to forget a step, and count7's 200+ FreePBX/FusionPBX installs made that obvious early.
What I built
FusionPBX on FreeSWITCH as the base, with PHP and PostgreSQL handling tenant data and the parts of provisioning that need to live close to the database, and Azure Functions running the scheduled and event-driven side: new tenant creation, nightly backups, and health checks that page me before a customer notices anything's wrong.
Where it landed
A platform I still run and extend today (see office.pbx.shadikur.com) — the same automation patterns from this project are what I lean on whenever I need to explain, concretely, what 'infrastructure as code' meant to me before AWS CDK gave it a name.