What is a session border controller?
A session border controller, usually called an SBC, is the device at the boundary between an enterprise voice network and a carrier. It terminates signalling and media arriving from outside, admitting only as many concurrent sessions as the licence and the capacity permit. It is also where protocol differences between the two sides are reconciled and where internal topology is hidden from the carrier.
Also called: SBC
What an exposed voice edge attracts within hours
A voice service put on the public internet without an SBC is scanned and attacked within hours, and the attack is economic rather than merely noisy. Toll fraud works by placing expensive international calls through someone else's trunk, and the bill arrives before anyone notices the pattern. The device is also what keeps a voice agent from disclosing the internal network, since it hides internal addressing and rewrites signalling on the way through. For a regulated enterprise it is usually the control that makes an internet facing voice deployment approvable at all.
- An exposed voice trunk is scanned for toll fraud continuously.
- Session admission limits protect the platform from being overwhelmed by volume.
- Topology hiding prevents the carrier side learning the internal addressing.
- Protocol reconciliation is what makes two compliant implementations actually interoperate.
- Security review of a voice deployment usually begins at this device.
How a session border controller works
- Signalling from the carrier terminates on the SBC rather than on the application.
- Each request is authenticated and matched against the permitted source addresses.
- Media is relayed through the device, so internal addressing is never presented outside.
- Concurrent session counts are enforced against the capacity provisioned for the service.
- Protocol variations between the two sides are normalised by the device.
- Anomalous patterns trigger rate limiting and an alert to the voice operations team.
How a session border controller is evaluated
An SBC is assessed on what it refuses as much as on what it passes. Examine the following under load and under attack simulation:
- concurrent sessions sustained before admission control engages
- rate of unauthorised session attempts rejected at the edge
- media relay latency added per call leg
- failover time when the primary device is withdrawn
- interoperability failures per carrier after a firmware change
Limitations, risks and common failure modes
- Admission limits are provisioned for a pilot and never revised for the campaign.
- A firmware update changes header handling, so one carrier stops interoperating.
- Media relay through a single device becomes the latency bottleneck for every call.
- Fraud rules are tuned so loosely that an attack resembles ordinary traffic.