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.

Ooma built their solution on 2600hz open source. They also acquired OnSiP On the investors call; They see 2600hz as the solution for the future. They want to invest more into development of the platform core and applications. There are significant savings in development for Ooma through the acquisition (2M/year). The recognize the revenue model of 2600hz, and list the open source market as an opportunity, though how was not discussed. They also mentioned that the GP% of 2600hz is lower than Ooma, and they hope to increase it to match Ooma's ~60% GP within 6 months (or at least EBIT positive) When asked about the developer community, its size and opportunities there, they mentioned that there "is a community" but was not really elaborated on. The acquisition is largely around the technology stack and the operational benefits it brings, control over the roadmap, new opportunities to reach large carriers, and not just the existing customer base. in closing remarks, it was said by Eric Stang that they are committed to the 2600hz community and the open source version

You can try setting "ignore_early_media" on your offnet/carrier, which may solve your problem. This will send ignore_early_media to freeswitch, both 180 and 183 will trigger your fake ringing from FS to the handset.

@mc_ appreciate the input. I'm personally happy to pay 2600hz, especially for apps. However, a small operation like mine tried to get a quote and it was all USA hosting for a lot considering our small customer base. I did suggest that 2600hz could host the kazoo apps nodes only, keeping the IP protected without having to run a full cluster, which seemed to garner some positive feedback from 2600hz, but I don't think it went anywhere. Its probably what the app exchange is targeted for. I'm happy to contribute to docs, for v5. But it has felt like a wasted effort to write docs for v4 since it seems the change to v5 would be drastic. I personally would love to hear what would be most helpful to contribute. I'm only one person and I'm extremely time poor, so knowing where my efforts would be most impactful would be good to know. I will add, I do try to contribute from time to time, but my PR from 3 years ago is still open (and still fixes an active issue)

I also get why they don't want to release v5 as per a previous statement that people tend to "jump right to it" without testing themselves, then probably cause a bunch of complaints/support requests. But if we are anywhere near an open-source release, I would love if some of us could gain access to or sign up for the v5 open-source release for testing. But as @Chris Labonne stated, we are in that process of deciding to stick with Kazoo or not. And I'd love to do another Kazoo Community Training video with the updated v5. I've kinda held off creating anything as I don't want it to be outdated.

Do we even know if we will get a new version in time so we can get off Centos7 before it hits EOL?

One day, I might do a part 2, or even an updated version for more recent versions of couchDB :) If only I had more hours in the day to do all the things I wanted to do :/

This is not the forums for Kazoo Pro (which I believe are knock-offs of the official 2600hz.com licensed apps). I doubt you will find any help here.

I this for the hosted platform only?

Token restrictions will allow you to block "CREATE" "DELETE" operations for certain endpoints, though I've not implemented this myself yet; https://docs.2600hz.com/integrator/applications/crossbar/doc/token_restrictions/ Not sure how to handle the CLID without writing your own app at this stage (though this is something I will be looking in to myself soon)

@kazte, yes, what you are after is possible. You can have pre-paid or post-paid accounts. You can apply a limit to post-paid accounts too. In the event an account exceeds its limit, it will terminate calls. You simply need to set an account to be pre-post paid and set the limit. You also need to ensure the Jonny5 app is running. By default, limits are per-month (though you could use the API to "top up" an account or change its limit on a more frequent interval). Limits apply to resellers also. When an account underneath a reseller account makes a call, the reseller account is also charged for that call. Likewise the root/superadmin account by default is also charged for the resellers calls (charges all the way up the chain). Each account may be charged a different rate (based on their ratedeck). You can choose NOT to charge a specific account (useful for the root/superadmin account) by using "flat rate trunks". Ratedecks can be at the system, reseller or account level. Hotornot is the app in charge of figuring out how much to charge for a call (it does the call rating) Jonny5 enforces the limits (it does limiting). I personally do not know how often Jonny5 checks limits/credit.