Mooseable

You can use couchdb v3 fine on 4.3. it's more about couchdb zoning, which is well documented. This is the discord invite again for another 7 days. It's not a support channel though, it's for those wanting to contribute to efforts in maintaining 4.3. https://discord.gg/r77hSf89

There's also the 4.3 build that has been done for 4.3 via the kazoo-classic repo. https://github.com/kazoo-classic/kazoo/releases/tag/v4.3-1-alpha I'd like to thank the others in the Discord for their monumental effort to getting 4.3 running on newer OS's and updated dependencies.

For anyone in the same situation, wanting to continue to run 4.3 but on a supported OS, it's been hard forked to https://github.com/kazoo-classic as I'm going to assume 2600hz/ooma won't want to maintain or accept PRs for 4.3. Repos will be updated as we test fresh deployments of 4.3 with installation instructions. That said, I'd rather put efforts into contributing to v5, but its closed source so I'm doing what I can :)

Update on 4.3 on a newer os; Not all stress tested yet, but everything is working across a mix of Debian 11+/Alma 8+, external calls working fine, just faxing and notifications/emailing to go next

As a quick update, we have Kazoo 4.3 running on a mix of Debian 11, Debian 12 and Alma/Rocky 8. Haven't yet stress tested it, but we can at least place internal calls (not yet connected with CTS trunks), nor have all apps/features been tested. @mc_ - are the rpms for Rocky8/9 for Kamailio/Freeswitch for Kazoo v5 only? For everyone else, here's the "cliff notes" on versions needed to run 4.3. Once the installations are stress tested, I will work on documentation that others can follow. 🛋️ CouchDB [Version: 3.2.3] [OS: Debian 12] ☑️ Running and working. Requires special HAPROXY config to reroute port 5986 🛜 Freeswitch [Version: 1.10.9] [OS: Debian 11] ☑️ Running and working. Anything later than 1.10.9 fails to work with legacy messaging from kazoo-applications on the AMQP bus and crashes freeswitch. Requires a signalwire personal access token to access the repo 🔐 Kamailio [Version: 5.5.7] [OS: Debian 11] ☑️ Running and with a phone registered. Requires use of PostgreSQL instead of KazooDB. Config exists thanks to a fork from ruhnet. ⚙️ Kazoo-Applications [Version: 4.3 with OTP 19.3] [OS: Alma Linux 8] ☑️ Running and working. Requires separate RabbitMQ node/docker image. 🐇 RabbitMQ [Version: 3.13.7] [OS: Docker] ☑️ No notes other than its best to be run inside a docker container on the same node as your kazoo-applications node. 👾 Monster-UI [Version: 4.3] [OS: Alma Linux 9] ✅ Working. Had to "compile" it on an older machine, then just tarballed the result and copied to Alma 9 due to issues with node package versions and GULP. Since this only needs to run a web server, you can run this on any OS.

If anyone wants to chat in discord which I find easier, join the server here. https://discord.com/invite/842WnGkH Expires in 1 week I'll share my WIP of my efforts so far over there and when I manage to get it all running, I'll post back here and offer an update to the docs

So far the challenge with Kamailio is the KazooDB binary (which is a wrapper for SQlite). Have either of you had Kazoo-Kamailio running off something like postgres instead? Also, drop me a DM if you want to collab over something like discord/whatsapp instead.

So Kazoo-Applications and RabbitMQ builds can be done on Rocky/Alma 8. On 9, I can't get Erlang OTP 19.3 working, and kazoo won't build with Erlang OTP 20.3 or higher. I have a freeswitch node up using Debian12, but I haven't tried sending calls to it yet as I need to get Kamailio working first. If anyone wants to collab on the efforts to build on Rocky/Alma 8 or 9, let me know.

It was about 6 months ago, so I don't remember off the top of my head. I still have all my notes for Kazoo core, kamailio, rabbitmq, couchdb, etc. I'll see if I kept any notes on the freeswitch install.

I did get almost everything in 4.3 running in Rocky linux. Just not Kazoo's modules for freeswitch.

What I meant was, alma 9 will be end of support in under 3 years. If it's 6 years before a distro update let alone a version update available, running kazoo open source is a massive risk. Only way to go is commercial but then, I never would have even heard of Kazoo if not for the open source community version.

Even IF v5 comes out, you now know you'll have to run EOL operating systems in the future, when the v5 branch stagnates for 6+ years. I love kazoo, I submitted bug fixes (which never were approved because work was being done on v5) created community content, videos, community support. I even tried to buy commercial Kazoo but we are "too small" for it to be viable financially (under 1000 extensions) in today's competitive market. I'd love to continue with open source until we hit the threshold where I can hand off the system management to a commercial contract. But, it is what it is. I thank the kazoo Devs for building a fantastic system and I wish v5 was out before CentOS EOL

I'm eagerly looking forward to it. It's my favorite project. I'd love to host my own cluster like I do, but just license the apps. It would then make financial sense for us being that we are so small. Biggest thing is to get off older versions of Linux :/

Just because I picked "other", I've integrated real-time caller-id, account setup and automated billing with HaloPSA. Looking to grow it by adding call notes to tickets and audio recordings/transcripts and sentiment analysis.