What is an SBC?

A Session Border Controller sits at the exact point where your calls cross from your network into someone else's. Almost every enterprise call passes through one, whether anyone notices or not.

The border checkpoint for a call

An SBC, Session Border Controller, sits at the edge of a network, at the exact point where calls cross from something you control into something you do not, or the other way around. Every call your organisation makes or receives to the outside world passes through it, inspected and often modified on the way through.

What it is actually doing to your call

An SBC does several distinct jobs at once, and knowing them individually makes its behaviour far less mysterious:

• Topology hiding: it rewrites SIP headers so the outside world never sees your internal network structure, only the SBC itself.
• Protocol interworking: it translates between SIP dialects, codec sets, and transport types that would otherwise refuse to talk to each other.
• Security: it enforces encryption, blocks malformed or malicious traffic, and is usually the first line of defence against toll fraud.
• NAT and media handling: it often sits directly in the media path too, not just signaling, solving the same NAT traversal problem WebRTC solves with ICE, but for traditional SIP trunks.

Why almost every enterprise call passes through one

An on-prem PBX was never designed to be exposed directly to the open internet, and a carrier's network was never designed to trust an unknown customer's equipment. The SBC is the negotiated middle ground both sides trust, which is exactly why it sits at the centre of enterprise carrier interop.