What is Session Border Controller?
An SBC is the security and interworking device where your network meets a SIP trunk or Microsoft Teams voice deployment — here's when you need one.
SBC (session border controller) is the device — appliance, software, or cloud service — that sits at the border where your network meets a carrier’s voice network. It controls who gets in, protects what crosses, and translates between equipment that doesn’t speak the same dialect.
What it actually does
- Security: encrypts signaling and media (TLS/SRTP), hides your network topology from the outside, and absorbs toll-fraud probes and denial-of-service traffic before they reach your phone system.
- Interworking: transcoding between codecs, surviving NAT and firewall quirks, and bridging incompatible PBX or carrier implementations.
- Policy and quality: call routing rules, number normalization, and the QoS enforcement that keeps voice from degrading when the network gets busy.
Do you need one?
With UCaaS or hosted PBX, no — phones register to the provider’s cloud and they run the SBCs. With SIP trunking terminated on your own IP PBX, something has to own that border: some PBXes have it built in, some firewalls claim ” SIP-aware” support, but a purpose-built SBC is what carriers and auditors expect on business-grade deployments.
For Microsoft Teams Phone, the choice is explicit: Direct Routing requires a Microsoft-certified SBC you manage (or rent from a carrier), while Operator Connect removes the SBC entirely — see our best Teams Phone providers for how the two compare in practice.