freesbc

One binary, one YAML: FreeSBC keeps your FreeSWITCH off the internet FreeSWITCH should not sit on a public IP. Every SBC that fixes that wants a per-session license, or four services and a media daemon to babysit. So I wrote one. One Go binary, one YAML, ./freesbc run. No DB, no Redis, no separate media process. One 4 vCPU VM: 5000 concurrent calls with both legs anchored, 3500 CPS, under 1 ms added latency. Eight hour soak at 3500 calls, 432,000 calls, zero failed, no memory growth. FreeSBC admin UI Admin UI: http://<public-ip>:8080 I did not run Kamailio or a commercial box on the same rig, so I am not claiming it is faster. The load harness is in the repo. Apache 2.0. rasonyang/freesbc Tell me where it breaks.