https://www.blog-des-telecoms.com/tags/sbc/Recent content in SBC on Mathias WOLFFHugofr-FR<a href="https://www.blog-des-telecoms.com">Blog des télécoms</a> © 2009 - 2026 by <a href="https://www.linkedin.com/in/mathias-wolff-47a7941/">Mathias WOLFF</a> is licensed under <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0</a><img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"><img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;">Fri, 03 Jul 2026 20:10:00 +0200https://www.blog-des-telecoms.com/blog/pk-sbc-presentation-sbc-open-source/Fri, 03 Jul 2026 19:00:00 +0200https://www.blog-des-telecoms.com/blog/pk-sbc-presentation-sbc-open-source/<p>Interconnecter des trunks SIP d&rsquo;opérateurs et des IPBX d&rsquo;entreprise semble simple sur le papier. En pratique, c&rsquo;est l&rsquo;un des points de friction les plus coûteux d&rsquo;une infrastructure VoIP : il faut sécuriser l&rsquo;IPBX exposé sur Internet, gérer plusieurs opérateurs en parallèle, basculer en cas de panne, normaliser le routage, le tout sans grever le budget avec un SBC propriétaire opaque et fermé.</p> <p><strong>PK-SBC</strong> est une réponse open source à ce problème. Un Session Border Controller construit sur <strong>Kamailio</strong>, <strong>RTP Engine</strong>, <strong>Redis</strong> et <strong>PostgreSQL</strong>, conçu selon le principe <strong>KISS</strong> — <em>Keep It Simple, Stupid</em> — et éprouvé en production depuis 2012.</p>https://www.blog-des-telecoms.com/en/blog/pk-sbc-open-source-sbc-presentation/Fri, 03 Jul 2026 19:00:00 +0200https://www.blog-des-telecoms.com/en/blog/pk-sbc-open-source-sbc-presentation/<p>Interconnecting carrier SIP trunks and enterprise IPBXs looks simple on paper. In practice, it is one of the most expensive friction points in a VoIP infrastructure: you have to secure the IPBX exposed to the Internet, juggle several operators in parallel, fail over when one goes down, normalise routing — all without blowing the budget on a closed, opaque proprietary SBC.</p> <p><strong>PK-SBC</strong> is an open source answer to that problem. A Session Border Controller built on <strong>Kamailio</strong>, <strong>RTP Engine</strong>, <strong>Redis</strong> and <strong>PostgreSQL</strong>, designed along the <strong>KISS</strong> principle — <em>Keep It Simple, Stupid</em> — and battle-tested in production since 2012.</p>