# What Is a Session Border Controller (SBC)? | DialerBee

> A session border controller (SBC) sits at a voice network's edge and manages the SIP signalling and media crossing it. Learn what it does and when to use one.

Canonical URL: https://dialerbee.com/glossary/what-is-session-border-controller/

---

Glossary November 2026 6 min read

## What Is a Session Border Controller (SBC)?

A session border controller (SBC) sits at a voice network's edge and manages the SIP signalling and media crossing it. Learn what it does and when to use one.

D

[DialerBee Team](https://dialerbee.com/about/team/)

November 2026

Last updated November 7, 2026

Quick answer

A session border controller (SBC) is a SIP intermediary that sits between networks, for example between two providers' networks or between a company's phone system and its carrier, and manages the signalling and media that cross that border. RFC 5853 describes its functions as including topology hiding, NAT traversal, media traffic management and access control.

An SBC is the device or software at the edge of a voice network. Where a firewall sits at the edge of a data network, an SBC sits at the edge of a SIP network, with the extra job of understanding the calls passing through it. If your company runs its own phone system and connects it to a carrier, an SBC may well be sitting between the two.

### The Definition

RFC 5853 is the IETF document that describes the functions of SIP intermediaries known as Session Border Controllers. It is not a product specification, and it notes that the term SBC is not standardized or defined anywhere. It describes what SBCs are deployed to do, gives special focus to the practices that conflict with SIP's architectural principles, and says SBCs usually sit between two service provider networks in a peering environment, or between an access network and a backbone network. RFC 3261, the core SIP specification, defines the building blocks: a proxy, which forwards requests, and a back-to-back user agent (B2BUA), which receives a request as a user agent server and then generates its own requests as a user agent client, keeping dialog state and staying in the path of every request on its dialogs. RFC 5853 says that because SBCs often modify SIP headers and message bodies that proxies are not allowed to modify, they are by definition B2BUAs.

### What an SBC Does

RFC 5853 discusses several functions, including the ones below. It also covers fixing capability mismatches, protocol repair and media encryption.

- **Topology hiding.** Limiting the amount of topology information given to external parties. The RFC notes this is often done by removing Via and Record-Route headers and replacing the Contact header.
- **NAT traversal.** Keeping a control connection to user agents behind network address translators. One method it describes is shortening the registration expiry so that the user agent registers again before the NAT binding closes.
- **Media traffic management.** Controlling or monitoring the media, for example by inserting a media relay into the path. The RFC warns that this requires the SBC to access and modify the session descriptions, so it does not work if the user agents encrypt or integrity-protect their message bodies end to end.
- **Access control and security.** The RFC lists access control and denial-of-service prevention as perimeter-defence functions, but treats an SBC as both protection and risk: it also notes that an SBC is a single point of failure from the architectural point of view, and that because user agents cannot easily tell an SBC's actions from a man-in-the-middle attack, an SBC can prevent end-to-end authentication.

### An Example

This is a simplified illustration. A company runs its own phone system in an office. Its carrier will accept calls only from a known address and a known set of SIP behaviours. The SBC sits between them. Calls from the phone system arrive at the SBC, which presents a single clean address to the carrier, keeps internal addressing private, and relays the audio. If the office changes its phone system, the carrier-facing side stays the same because the SBC is the party the carrier talks to.

### Why It Matters for Outbound and Inbound Teams

For many companies adding a dialer, the question is whether the existing voice infrastructure can stay. On the [deployment](https://dialerbee.com/deployment/) page DialerBee describes a pattern where you keep your own PBX and trunks and the dialer becomes the campaign, pacing and compliance layer on top. The gateway can point at a standards-compliant SBC, and you choose the authentication mode: IP allow-list, SIP digest or registration. The page strongly recommends TLS. The practical walk-through is in [adding a predictive dialer to an existing PBX](https://dialerbee.com/blog/add-predictive-dialer-to-existing-pbx/).

If you bring your own carrier instead, [BYOC](https://dialerbee.com/features/byoc/) connects any SIP-compatible provider, so the same questions apply to the link between the platform and the carrier: how it authenticates, which address the carrier sees, and which codecs are allowed. See [SIP trunk](https://dialerbee.com/glossary/what-is-sip-trunk/) for the carrier connection itself.

### Questions to Ask Before Putting One in the Path

- **Does it need to modify session descriptions?** RFC 5853 notes that media management of this kind does not work if the endpoints encrypt or integrity-protect their message bodies end to end.
- **Is it a single point of failure?** The RFC says so plainly, so plan redundancy.
- **Who authenticates whom?** Settle IP allow-list, digest or registration before testing.
- **Do you need one at all?** A direct connection that your carrier accepts may be simpler.

### Frequently Asked Questions

#### What is the difference between an SBC and a firewall?

A firewall filters network traffic by addresses and ports. An SBC understands SIP: it terminates and re-originates sessions, can alter signalling headers, and can manage media. RFC 5853 describes these SIP-aware functions.

#### Is an SBC the same as a SIP proxy?

No. A proxy forwards requests. RFC 5853 says SBCs are, by definition, B2BUAs, because they modify headers and message bodies that proxies may not. A B2BUA receives a request as a user agent server and then generates its own as a user agent client, keeping dialog state, as RFC 3261 describes.

#### Do I need an SBC to use a dialer?

Not necessarily. Whether you need one depends on your carrier's requirements and your own network. With your own PBX and trunks you may already have one in the path, and a dialer can connect to a standards-compliant SBC.

#### Can an SBC cause problems?

Yes. RFC 5853 notes that an SBC is a single point of failure, which makes it an attractive target for denial-of-service attacks, and that modifying session descriptions for media management does not work if the endpoints encrypt or integrity-protect their message bodies end to end. These are reasons to design deliberately.

#### What does topology hiding mean?

It means limiting the topology information given to external parties, for example by removing Via and Record-Route headers and replacing the Contact header, so outsiders see the SBC rather than your internal addresses.

Related terms and guides: [SIP trunk](https://dialerbee.com/glossary/what-is-sip-trunk/), [deployment patterns](https://dialerbee.com/deployment/), [adding a dialer to an existing PBX](https://dialerbee.com/blog/add-predictive-dialer-to-existing-pbx/), [BYOC](https://dialerbee.com/features/byoc/).

### Sources

- [RFC 5853, Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments](https://www.rfc-editor.org/rfc/rfc5853) (sections 2, 3 and 5) (source, checked November 7, 2026)
- [RFC 3261, SIP: Session Initiation Protocol](https://www.rfc-editor.org/rfc/rfc3261) (proxy and back-to-back user agent definitions) (source, checked November 7, 2026)

**Related reading:** [Asterisk PJSIP trunk to a cloud dialer: setup guide](https://dialerbee.com/blog/asterisk-pjsip-trunk-to-cloud-dialer/) · [SIP one-way audio: a step-by-step troubleshooting guide](https://dialerbee.com/blog/sip-one-way-audio-troubleshooting/) · [DTMF not working on a SIP trunk? How to fix keypresses](https://dialerbee.com/blog/dtmf-not-working-sip-trunk/)

**Related reading:** [SIP TLS and SRTP: Encrypting a SIP Trunk](https://dialerbee.com/blog/sip-tls-srtp-encryption-setup/)

Related terms

#### [What Is a Silent Call?](https://dialerbee.com/glossary/what-is-silent-call/)

A silent call is one where the person answers and hears nothing, often because a dialer over-dialled. Learn what regulators say and how to avoid them.

#### [What Is a SIP Trunk?](https://dialerbee.com/glossary/what-is-sip-trunk/)

A SIP trunk is a virtual voice connection that carries calls over the internet between your phone system and a carrier. Learn how SIP trunking works.

#### [What Is a Virtual Receptionist? Meaning, How It Works and Cost](https://dialerbee.com/glossary/what-is-a-virtual-receptionist/)

A virtual receptionist is a remote person who answers your business calls. How it works, how it is priced, virtual vs AI vs in-house, and when each fits.

#### [What Is a Voice Codec? G.711, G.729 and Opus Explained](https://dialerbee.com/glossary/what-is-voice-codec/)

A voice codec turns speech into digital data and back. Compare G.711, G.729 and Opus: bit rates, bandwidth and what to choose for SIP trunks and softphones.

#### [What Is a Wallboard?](https://dialerbee.com/glossary/what-is-wallboard/)

A wallboard is the live floor display showing queue and agent state in real time. What belongs on one, what does not, and how it differs from a dashboard.

#### [What Is a Warm Transfer? Warm vs Cold Transfer, with a Script](https://dialerbee.com/glossary/what-is-a-warm-transfer/)

A warm transfer means briefing the next agent before handing over a call. Warm vs cold vs conference transfer, a step-by-step script, mistakes and metrics.

#### Ready to see DialerBee in action?

Request a 15-minute live demo, or start a 14-day free trial — no slides, no commitment. Calling starts once your own SIP trunk or PBX is connected and approved.

[Request a Demo](https://dialerbee.com/demo/) [Start free trial](https://dialerbee.com/trial/)

14-day free trial · free AI credit · no card · 11 languages · BYOC · compliance-supporting controls

[Back to all posts](https://dialerbee.com/blog/)
