I’d like to share a little project I’ve been working on—VoIPBin.
It’s a personal, hobby-driven project that started as a small playground for experimenting with voice applications. Over time, it has grown into something a bit larger, though it’s still a side project and not running in production anywhere yet.
The project has been a lot of fun, and I’ve been learning as I go. I’ve decided to open-source the backend services for anyone who might find it useful, though there’s still a lot of room for improvement and refinement.
The project focuses on building simple, scalable voice systems, and though the VoIP deployment side (Kamailio, Asterisk, RTPEngine) isn’t open yet due to some ongoing issues, I hope to get there someday.
On Tuesday 06 May 2025 at 18:30:54, pchero via Asterisk Community wrote:
I’d like to share a little project I’ve been working on—VoIPBin.
Why the name? What is “bin” supposed to suggest?
I’ve decided to open-source the backend services for anyone who might find it
useful
What is the “front end”? What isn’t being open-sourced here?
the VoIP deployment side (Kamailio, Asterisk, RTPEngine) isn’t open yet
due to some ongoing issues
Are those licensing issues, where you don’t have the right to publish the
code, or do you just mean “it’s not fully working yet, so I don’t want to show
it to people”?
If it’s the latter, I would strongly suggest that you do publish the code,
and potentially get the assistance of other people who can solve (some of) the
problems for you.
Antony.
–
I own three Windows books, published by O’Reilly. They are “Windows
Annoyances”, “Office 97 Annoyances” and “Windows 98 Annoyances”. That pretty
much sums it up for me.
Thank you so much for your thoughtful message and kind encouragement. It means a lot.
Why the name? What is “bin” supposed to suggest?
“Bin” is my little joke—it’s like a trash bin for all my fun, crazy, and sometimes not-so-smart ideas. This project became a place where I experimented freely without pressure, and the name reflects that.
What is the “front end”? What isn’t being open-sourced here?
Right now, I’ve only open-sourced the backend services. The parts that aren’t open yet include the VoIP deployment side (Kamailio, Asterisk, RTPEngine).
This is the same for the frontend(https://admin.voipbin.net/).
There are a few reasons:
Some files contain hardcoded IPs, secrets, and personal tokens that I still need to clean up.
The deployment side is also a bit unstable—I’ve run into NAT and security issues I haven’t solved fully yet.
Are those licensing issues?
Not at all. No licensing concerns—just a matter of code quality and security. Once I feel the VoIP side is in a better state, I’d really like to open that up as well.
Suggestion to publish anyway and invite help
I really appreciate the suggestion—and I totally understand the value of sharing early and building with the community.
That said, some of the issues are quite sensitive—especially around hardcoded tokens and infrastructure security. I want to make sure I’m not exposing anything risky before sharing those parts. Once I clean things up a bit more, I’d love to open it up and welcome any help or feedback.
More about the architecture
If you’re curious about how it all works, I wrote a simple architecture page here: Architecture — voipbin documentation
It gives a high-level overview of how everything is wired together.
Thanks again for your thoughtful message—it’s incredibly encouraging.
VoIPBin GitHub Repository