The purpose of this survey is to gather people’s experiences and opinions on using Open Source Telecom Software Projects. I’ll share an anonymized aggregate view of the survey with those that compete the survey. I’ll also present a high-level summary for some of the results at TADSummit EMEA in November, where we have a session on “The Emerging Programmable Telecoms Architecture: Threats and Opportunities.”
I’m often asked to comment on the different open source projects, typical implementation architectures, and answer the usual worries on availability, performance, and what-ifs. This is an attempt to provide something more authoritative than my opinions based on who I last talked to. My role here is simply as someone who has working in and promoted programmable telecoms (CXTech) for the past 2+ decades, to help us all be more successful. Please circulate this around your contacts, the more feedback, the more insights and accuracy we will have, thanks.
Most of CXTech (potentially a $1.2T industry) runs on just a few open source telecom software projects, that are run by a few people, supported by a much larger community of supporters. Its like the global food and beverage industry (a $5T market, only 4 times the size of CXTech) was supplied out of the kitchens of a few tens of homes! A contrived analogy to highlight the immense reach made possible by open source software. But it does highlight the global significance of open source telecom software, and the importance of this survey in helping us share experiences and opinions.
I’ve put the questionnaire in 2 formats (a third will be coming soon), depending on your preference:
For the Google Slides / Sheet, make a copy, fill it in, and send it to me.
For the Google Form just complete and submit, and that’s it.
Nothing you send to me will be shared, only the aggregate results. I know many of you have experience across many of these platforms. I ask you complete the ones that matter to you most, and base your comments on experiences within the last 2 years.
The projects we’re evaluating include:
Telecom App Servers
Asterisk
FreeSWITCH
Kamailio
OpenSIPS
Restcomm/Mobicents
SIPfoundry / sipxcom
Management Interfaces / Solution Wraps / Monitoring and Capture
Elastix (for Asterisk)
FreePBX (for Asterisk)
FusionPBX (for FreeSwitch)
Kazoo
RTPProxy
SIP3
Sipcapture – Homer
Sippy Softswitch
VICIdial (for Asterisk)
Wazo (forked from XiVo, for Asterisk)
YETI Switch
WebRTC Projects
EasyRTC
Janus
Kurento
Jitsi
Mediasoup
Medooze
OpenVidu
Other (because there is some overlap and I like them)
Matrix
One’s I’m not considering:
AskoziaPBX, Murmur, Mysipswitch, sipXecs IP PBX
Opencloud Rhino, Metaswitch Clearwater
GNU Gatekeeper
Yate
If I’m missing any projects or you disagree with the ones I’m not considering, please let me know, thanks.
Kazoo and Yeti Switch.
Added 🙂 Thx.
RTPProxy is missing. Not a stand-alone component, but companion server that is often installed alongside of OpenSIPS or Kamailio to manage media traffic.
Also “sippysoft” should probably renamed into “Sippy Softswitch”, this is how we call it here.
Thanks!
Hi Maksym, updated the weblog, will update the surveys in a minute.
SIPFoundry (sipxecs) forked a few years back and eZuce now maintains the sipxcom project.
Hi Matt, should I edit SIP Foundry to SIP Foundry / sipxcom.
great, but can you please write our project’s name correct ? We are “Sipcapture – Homer” and not SIPCature. Thank you!
and we are not a wrap or a management interface, but a Monitoring/Capturing solution 🙂
Updated the name and category, will update the surveys in a minute.