Kazoo Classic is a community-supported hard fork of 2600Hz Kazoo 4.3. Its goal is not to create a brand-new low-code communications tool, but to keep maintaining an open-source, distributed, extensible VoIP/telecom platform—especially to address the practical issue that Kazoo 4.3 only provided CentOS 7 packages, while CentOS 7 has already reached EOL. It is aimed at engineering teams that need to self-host a PBX, SIP platform, or multi-tenant telecom service.
Based on the project content, Kazoo Classic depends on components such as FreeSWITCH, Kamailio, CouchDB, RabbitMQ, HAProxy, Monster-UI, while its core applications still revolve around Erlang/OTP. The verified feature set is fairly complete, including API authentication, device creation, callflow management, Web/Monster UI, device registration, internal calling, inbound and outbound trunking, two-way audio, hold/transfer, feature codes, voicemail, email notifications, and BLF/Presence. Fax, SIP SIMPLE messaging, and some other features are still marked as uncertain or pending verification.
The project is clearly positioned as an open-source community hard fork, and its maintainer encourages participation through GitHub forks, Pull Requests, and Discord. Self-hosting is its core deployment model. The documentation covers installation and configuration for FreeSWITCH, HAProxy, Kamailio, Kazoo-Applications, CouchDB clusters, and more, and lists tested environments such as Debian 11/12, Alma Linux 8/9, RHEL8/RHEL9, and Docker. In terms of ecosystem, it leans more toward a traditional telecom infrastructure stack and is best suited to teams familiar with SIP, Erlang, Linux, and database clustering.
The content does not mention any commercial subscription or paid plan, so it can currently be considered free and open source. Support mainly comes from the community, and the text also notes that financial support may be welcomed when the project is ready. As a result, its main cost is not software licensing, but deployment, testing, operations, and secondary development. Compared with commercial UCaaS or hosted PBX offerings, it emphasizes control and customization, but it is not suitable for users expecting a vendor-backed SLA.
Its strengths are transparency and a clear roadmap. The maintainer lists component versions, testing status, and plans in detail, such as support for Erlang OTP26, RHEL9, and adding STIR/SHAKEN capabilities to prevent caller ID spoofing. The drawbacks are also clear: the technology stack is complex, and version constraints are strict—for example, FreeSWITCH versions above 1.10.9 may crash due to legacy AMQP messaging issues. Some modules are still being migrated or planned. It is suitable for telecom platform engineers, existing Kazoo users, and operations teams with self-hosting capabilities, but not for beginners who want a quick setup.
The content does not provide information on access from mainland China, mirrors, payments, or compliance, so china_access can only be classified as unknown. Since deployment involves external resources such as GitHub, the SignalWire repo, and Docker, teams may need to verify network connectivity themselves before production rollout. Comparable or alternative open-source options include Asterisk, FreeSWITCH, Kamailio, FusionPBX, and the original 2600Hz Kazoo.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on ospbx.com official site.
ospbx.com is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of China direct-connect friendly. Click "Visit Official Site" to reach ospbx.com directly.