Earlier this month Telnexus was honored to be named by 2600hz as a presenter at KazooCon 2015 this October 5th and 6th in San Francisco. We will be sharing the experiences we’ve gained by using the Kazoo telephony platform to power our Telnexus Cloud PBX and SIP trunking service. I can’t wait to see my fellow communication freaks at the show!
So, why does Telnexus use the Kazoo platform and why do we think it is awesome? It’s because there is no better API-based, Open Source-tested, true-cloud architecture business communication solution available on the market today.
The Kazoo API is what makes Kazoo modern, efficient and exciting. The API makes Kazoo exciting because it can potentially be anything that a programmer or developer can imagine. At Telnexus we’ve taken advantage of the Kazoo API in some interesting and useful ways. That’s what I’ll be talking about at KazooCon 2015, so sign up for our Twitter and Facebook feeds for updates.
The Kazoo codebase comes with the best possible pedigree. Kazoo stands tall on the shoulders of the telephony giants who built the Open Source telephony world with Asterisk, Freeswitch and Kamailio. 2600hz has taken that rock solid core and married it with scalable database and message queuing tech to support a massive cluster. Next, 2600hz sprinkled this array of Open Source components with their own pixie dust in the form of cluster management. The result is Kazoo — a network of dozens of server instances which manages a multi-region, multi-node cloud supporting thousands of business phone systems at once.
It is from the true-cloud architecture where Kazoo gets its best feature: a 99.999% up-time record. To get this level of performance, any online service that purports itself to have a “true-cloud architecture” must have these features to distinguish itself from a merely hosted application:
- Uses a tiered architecture to distribute key application functions to separate application server instances
- Has a cluster manager to control application server instances, support inter-application communication, manage hybrid public-private clouds, and access public cloud resources
- Achieve regional failover capability using public cloud resources
And, in the case of cloud telephony, a “true-cloud architecture” service must have these features to be a scalable and reliable multi-tenant PBX offering:
- Uses a DNS and host-based authentication method that automatically manages server overloads and outages
- Has a Session Border Controller (SBC) and SIP proxy server capability that automatically supports multiple endpoint types in a variety of network configurations
If you examine the “cloud” offerings from industry leaders including Shoretel, Cisco and Broadsoft, you’ll find that their hosted offerings don’t qualify as “true-cloud architecture” and suffer from greater levels of downtime and poorer endpoint support than Kazoo. From what we know about our friends at 8×8 and RingCentral, their services cannot be scaled into the public cloud when their private facilities fail. These competitive factors, among other things, is what makes the 2600hz Kazoo platform a world-class service.
There are actually even more reasons why we think that the 2600hz Kazoo platform is the best cloud telephony platform in the world, and these reasons have more to do with the dedication of the 2600hz engineering crew to their craft. When it comes to solving problems and avoiding them in the first place, you’ll never find a better band of telephony freaks!
That is why Telnexus thinks the 2600hz Kazoo platform (and the Telnexus Cloud PBX) is absolutely the most modern and reliable cloud-based PBX and SIP-trunking system available in the world today.
See you at KazooCon where I’ll be speaking more on the subject of the Kazoo API.
— Vern
