A network element at the edge of a VoIP network that secures, controls, and normalizes SIP signaling and media passing between networks.
An SBC sits at the boundary between a provider's core and the outside world, whether that is a customer PBX, an enterprise, or another carrier. It hides internal topology, enforces access control, defends against signaling floods and scanning, and handles NAT traversal and media anchoring. It is often the first device to see each call, which makes it an important source of logs for security and fraud investigations.
SBCs also translate between the different SIP dialects used by different vendors and networks. Header manipulation rules let operators add, remove, or rewrite headers, which is useful for interoperability but also a common source of problems when rules accidentally strip Identity headers or alter calling numbers. Any change to these rules should be tested against signed calls to confirm that authentication data still passes through as intended.
Many SBCs can enforce call admission policies such as concurrent call limits and rate limits per trunk, and some integrate with STIR/SHAKEN signing and verification services or external fraud and analytics platforms. Using these features consistently across all edges of the network avoids gaps that attackers can find and exploit.
Why it matters to carriers
The SBC is where you can stop bad traffic at the door: enforcing limits, rejecting calls with invalid caller ID, and applying blocking decisions with the correct SIP response codes. It is also where authentication data is most often damaged, so SBC configuration deserves the same review attention as your signing and verification services.