2600hz

kazoo

Erlang2012–2020

2600hz / kazoo

kazoo

The core of an open-source, distributed, highly scalable platform designed to provide robust telecom services

Systems & Infrastructure

Explore on GitHub Read Hacker News discussions

5Distinct people

8Mentions

0Explicit recommenders

990GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

The core of an open-source, distributed, highly scalable platform designed to provide robust telecom services

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2012-11-02 18:28:58 UTC to 2020-04-02 21:06:51 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2012	2012-01-01 00:00:00 UTC	2013-01-01 00:00:00 UTC	1	1
2013	2013-01-01 00:00:00 UTC	2014-01-01 00:00:00 UTC	0	0
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	0	0
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	1	1
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	0	0
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	2	2
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	2
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1

What Hacker News says

8 sources

mc_·Apr 2, 2020

Kazoo [0] offers this as a config option on devices (which can represent SIP desk phones, soft phones, WebRTC endpoints, or call-forwarded cell phones): call_forward.require_keypress [1] There's a lot of re-inventing of telecom wheels required (if even possible) with TwiML (and clones). [0] https://github.com/2600hz/kazoo [1] https://docs.2600hz.com/dev/applications/crossbar/doc/device...

In Using Twilio to make a call forwarding and voice messaging system

ignoramous·Oct 7, 2019

Does Wazo compete with 2600hz's Kazoo [0] / Telestax's RestComm [1] or with OpenCORD [2] implementations? If not, I'm having trouble understanding what it really is... Can someone pls explain? [0] https://github.com/2600hz/kazoo [1] https://github.com/RestComm [2] https://opencord.org

In Wazo Platform: build carrier-grade programmable IP communication infrastructures

mc_·Sep 30, 2019

We're happily plugging along on KAZOO [0] since 2010 at 2600Hz. Erlang is a force-multiplier for us. Approaching 300K LOC and ~10 Erlang engineers (depends if Karl is writing code or CTO-ing that day) today. [0] https://github.com/2600hz/kazoo/

In Which companies are using Erlang, and why?

mc_·Aug 22, 2018

We use Erlang to build Kazoo (https://github.com/2600hz/kazoo). In production since 2011, deployed around the world in various clusters.

In Learn You a Haskell for Great Good

mc_·Nov 13, 2017

2600Hz has an API-driven platform, Kazoo[0], built on FreeSWITCH and Kamailio. You can use the APIs to start calls, modify in-progress calls, and more. Multiple commercial offerings[1] depending on your needs are provided by 2600Hz as well. Source: work there building Kazoo [0] https://github.com/2600hz/kazoo [1] https://www.2600hz.com

In Ask HN: What is the best VoIP library/service to add calls to an app?

fenollp·Aug 21, 2017

So if you look into [1] you'll find .hrl sources (actually .erl) and their .S counterpart in the subfolders. From these you will see that functions `a` and `b` look more and more like each other. Note that `b` is the literal version of `a`. How much speedup? Potentially infinite, at the price of compile time. In real world cases though I don't have any data yet. I want to be able to compile a whole project first and that fails for one last reason, described in the README. But I have faith :) The patterns that can be superoptimized are few for now. [2] describes how some of lists.erl functions work so that they can be supercompiled. The long-term idea is to have a local(/global if secured) cache of code so that inter-module calls can be optimized if the developer wants. My real world case/motivation is supercompilation of code such as [3]

Read the rest

(goal is to turn `a` into `b` at the assembly level). This pattern is extremely common in my employer's software [4] (which is probably the biggest open source Erlang project AFAIK). A short example of a being super compiled into b: a() -> hd([get()]). b() -> get(). [1] https://github.com/fenollp/erlscp/tree/master/test/asm_data [2] https://github.com/fenollp/erlscp/blob/master/src/erlang_sup... [3] https://github.com/fenollp/erlscp/blob/master/test/asm_data/... [4] https://github.com/2600hz/kazoo

In A supercompiler pass for Erlang

avatardog·Nov 16, 2015

I work there, just saw this. Bluebox was an old project to provide a GUI for freeswitch. Kazoo has been the focus for the past 4 years, bluebox is now a community project if I recall correctly. Kazoo is a multi-tenant hosted pbx and trunking solution. It is an erlang cluster which uses amqp as a messaging bus and erlang apps which provide centralized call control and features across multiple freeswitch (media server) and kamailio servers (sip proxy). A shared cluster wide database is provided by bigcouch. The difference between this and a cluster of asterisks (or broadcloud, kandy etc) is that you as a user or account, are not tied to a single server, any phone on your cluster can utilize the resources of the entire cluster as the erlang apps and AMQP bus provide a glue joining all servers in the cluster into a single "switch". Most of t

Read the rest

he "cloud" telephony out there is not distributed, it is mostly a lot of boxes with at best HA fail-over to another box that sits in as a warm standby with a unified provisioning layer to hide this from the users. You can checkout kazoo at github http://github.com/2600hz/kazoo There is a kazoo all in one ISO, which lets you run all the services in a cluster via a single server. You can get it at http://repo.2600hz.com/ISOs version 2 has the new GUI monster-UI. Edit: phone does not a good comment make, spelling broken links ...

In Ask HN: What type of phone system do you use?

josh2600·Nov 2, 2012

Thanks! We're total phreaks over here :D. Here's the Git link for our Kazoo project: https://github.com/2600hz/kazoo Here's one of our APIs (conferencing): https://2600hz.atlassian.net/wiki/display/docs/Conferences+A... We've got a client doing a very large number of simultaneous participants in a conference using this stack (in excess of 10k concurrent), so there's a lot of firepower here. Also of interest to this community: the logic is written in Erlang :). Let me know if you have any questions, we're in freenode at #2600hz

In Twilio looks better from afar