Yeti-Switch

Is Yeti-Switch actively maintained?

We cannot measure this one. Yeti-Switch is developed outside the platforms our data source collects activity from, and its repository lives at github.com — so there is no commit history or release cadence here to score.

Read that as missing data, not as a warning. Several of the best-maintained projects in this catalogue are unrated for exactly this reason. To judge it, open the repository and look at the date of the most recent commit yourself.

What Yeti-Switch actually does

Yeti-Switch is a transit class 4 softswitch and session border controller featuring an integrated billing and routing engine. It comes with a REST API for programmatic control over voice traffic management. As a class 4 switch, it is designed for wholesale VoIP operators handling high volumes of long-distance call routing between carriers.

Best fit: It suits telecommunications engineers and wholesale VoIP providers who need an open-source routing and billing engine for carrier-to-carrier traffic. It is ideal if you want to self-host your own transit switching infrastructure using a GPL-licensed codebase.

Worth knowing: The lack of recent commit activity and zero tagged releases indicate that you may encounter unmaintained code, missing documentation, or unpatched bugs. Operating a class 4 softswitch also requires deep domain expertise in SIP signaling, network security, and real-time media handling.

Deployment notes

Since the application combines C++ and Ruby components, you will typically need to manage a relational database for billing data, along with a process manager like systemd or Foreman to handle the background worker processes. Proper firewall configuration and SIP port management are essential for exposing the signalling engine securely.

Links

• Official website
• Source code
• Live demo