All Activity

Well the intent is to keep it as it was with 4.3. So the core of the platform remains open source as it was before. Some things are changing though. An example is we are porting over a management interface we built for our Ooma Enterprise platform (Voxter acquisition which was built on OS) but that'll be closed source for commercial customers since we spent a lot of development time building it. So y'all can do whatever you want with Monster UI (we will deprecate that eventually for commercial customers and we've rebuilt a good portion of that into a more modern UI). The foundational code should be the same for the repo we manage. We've largely gotten to a point where most of the development effort is around ancillary closed-source applications. 5.4, for our commercial customers, is a LTS release and Ooma is going to move there (we are on 5.3 currently) later this fall/winter. I can imagine in the future we do release further updates but they are likely to be minimal (things like certain FS, Kamilio, CouchDB, etc. updates) that constitute a dot release for us. I hope that helps. It's a great foundational platform to build off and for FWIW, we solely interact with the platform via all the APIs. We built all of our own IP all around that foundation with the use of the closed-source modules to help with scaling the platform and getting access to some of the new features (e.g. Qubicle - which is the refactored ACDC that was closed source before we acquired 2600hz).

@Chris Burgy I really appreciate the transparent explanation—it helps clarify both the upcoming OS 5.4 release and the broader direction since the pivot. It’s good to hear the open-source version is still being carried forward alongside the commercial efforts. Once the release is out, I’d be interested in learning more about how the scaling improvements and repo split might impact operators on the open-source side. Please keep me in the loop if there are any early notes or best practices you’d recommend. One quick question: will the marketplace remain exclusively available for commercial customers, or will open-source operators also be able to purchase licenses for specific modules?

Cool! - Keep up the good work (in my opinion). Really neat to see (from someone who doesn't use OS) that you guys are sticking to your word! Looking forward to those apps! :D

@Chris Burgy Absolutely, would be nice to keep the name, but I doubt anyone really cares. Minimal or no documentation is fine; we can figure it out from the source code. :-) As far as some [many] modules not being part of the open source release, that was expected, but can you tell us if the release will be complete as far as having all components of a working system, [albeit possibly barebones]? In other words, are there any critical parts that will be missing for a standard PBX that we (the open source community) will need to add? Also, is this release going to be a "one time dump and then move on" or will the open source public repos be the same codebase used internally for your developers' continuing work on the project (like Kazoo was prior to v4.3)?

We did go through the motions with our legal team (obviously we have inside counsel with a handful of attorneys and outside counsel to also consult). Unfortunately, because 2600hz let the trademark lapse a long time ago, it's a sticky situation. Is what it is and just one of those things we had to roll with the punches on. We even had marketing look at other naming conventions but that's a whole different situation with trademarks. I think everyone that knows 2600hz understands what it was and new customers don't frankly care about the Kazoo branding. They are paying for a solution from 2600hz so that is good enough for them since it's all hidden anyways. I appreciate the comment though. We wished we could've continued on with the platform name we all have known over the years.

Thanks so much for the update, @Chris Burgy! That's [mostly] good news. :) Incidentally, [please confirm with your lawyers of course, but] there is no reason why you must stop using the Kazoo trademark: The other company who successfully registered it declared their first use of it as 2019, and 2600Hz's first use was long before that. Contrary to popular belief, trademark rights don't come from registration, but from usage. Since the other company registered "Kazoo" as a trademark for their forum or whatever service, you probably can't sue them for use of it (well, you can actually, but it's not as simple since they do have a registration), but that doesn't mean your rights to continued use of the "Kazoo" trademark is limited in any way, since it pre-dates the other company by several years. Just an FYI.

We officially approved releasing an OS version of 5.4 as a Senior Leadership Team about 3 weeks ago. Product management is working with engineering on this as we had to split the OS and closed-source repos. As you probably know, 2600hz pivoted years ago to having closed sourced / commercially licensed components as the company couldn't survive without generating revenue and OS wasn't doing that especially compared to the fully commercially licensed competitors of 2600hz (Netsapiens, Alianza, Broadsoft, Metaswitch and RingCentral/Intermedia/etc coming from the UCaaS space with a pure reseller model). All the closed source modules will remain such with an increasing number of those ported from the Ooma side. To be transparent, Ooma's priority has been porting over our intellectual property we built (our desktop, mobile, video conferencing, chat and custom scaling fixes) for the hundreds of commercially licensed customers of 2600hz that have wanted to tap into the tens of millions of dollars we've invested over the years as the largest operator of the platform. That being said, I'd venture to guess it'll probably be in the next 4-8 weeks as engineering has been slowly chipping away at it behind the scenes over the last 2 years and they are in a state where they are generally ready. It's not going to come with much documentation. There are significant improvements in the 5.X family compared to 4.3 although some of those for scaling are tied to closed source modules that have long existed. It was a bit complicated when we acquired 2600hz as they had pivoted their strategy to still having open source but tying it to the new marketplace and there was still a lot of work to be done. They were pretty focused on their commercially licensed customers. That being said, we recognize the value of open source as that is where Ooma started years ago with the platform and then we wanted 2600hz to continue to survive and make money so we entered into a relationship where we could compensate them in a meaningful way to help fund all the developers (the majority of the company was and is R&D resources). Hope that helps! This wasn't purposeful. That site was tied to a credit card we didn't know about in the acquisition, it expired and the hosting provider deleted everything. So we had no way to recover it. We would've gladly left it up (like prior KazooCon videos on youtube). Do see my prior post on open source though. We also can't use Kazoo anymore as the trademark lapsed years ago (another neat thing we wound up discovering) and another company snagged it and wouldn't sell it to Ooma.

It's the end of August. What is the release of 5.4 OS looking look at this point?

Thanks. Currently I have it installed and set up with a lot of configurable brands also. Currently, running some cisco and yealink phone devices. They registered instantly, I could enable some featured keys.

Hello All, My name is Eric and I started my new role this week on our Technical Customer Support team. I look forward to working with you all! Thanks, Eric

Hello Everybody, My name is Naman Kamdar, and I have joined as a technical support specialist for the 2600 Hz project! It feels great to connect with you all!

How can I restrict a user from receiving calls from a specific user or a specific number in Kazoo? I would also like to limit the numbers a user can dial.

If you haven't joined the Discord already, please pop by and say hi. There's a whole channel dedicated to STIR/SHAKEN with a working implementation available for 4.3.

Welcome! https://docs.2600hz.com/ consider checking the docs site out (though it has both legacy 4.3 and current 5.x docs so make sure you're looking at the right ones for your install).

Hi. I am a newbie using this platform. Exploring some documentation to learn about it. Which documentation may you recommend?

What are you looking for help on?

Thanks for let it know. wntpftp.!

@fmateo05 Hi there! Just a quick update — we’ve officially moved all of our documentation to our new site: docs.2600hz.com. You’ll find all the legacy Monster UI documentation there, along with a bunch of other helpful resources. As for open source, we’re still planning on it! That being said, we don’t have a formal timeline just yet. When it does happen, it’ll be based on version 5.4.

Also in the .org website there is no update for a long time.

That's why I keep saying Kazoo 5 is dead. Their very last KazooCon, they made all the videos unlisted, and no update on the project in over 5 years. The KazooCon site has been removed. It's dead. Even if you take a look at their main web site, there is zero mention of anything open source. It's all SaaS/Cloud now.

I cannot see the 'Monster App's' Section; what is going on? (wntpftp!)

Hi, my name is Tim and I am the IT Manager for our company. We recently started using Kazoo (Monster UI) for our Simple Phone system. I have it working but need some help on advanced features.

Wow!! This is excellent! Yeah, we definitely want to be part of testing this and getting it stable on a current OS. Good move you guys!

@mc_ It's really not off topic as stir/shaken is required to keep 4.3 running past June. One of the primary project goals of the fork is implementing stir/shaken. I can't find any posts other than this about it: