VoIP Phone Numbers and DID: How They Work and How SBCs Route Them

On a VoIP network, a phone number is not bolted to a copper pair or a single handset. It is a software-defined identifier that a carrier agrees to route to wherever you point it. That one fact explains almost everything that makes VoIP flexible, and it also creates the routing problem that sits at the edge of every serious deployment. A dialed number arrives at your network as a string of digits inside a SIP message, and something has to decide where that call actually goes.

In this article, we’ll walk you through what a VoIP phone number really is, how carriers assign and provision the underlying Direct Inward Dialing (DID) numbers, the difference between hosted numbers and Bring Your Own Carrier (BYOC), and how a Session Border Controller (SBC) turns a dialed DID into a delivered call. If you run a VoIP service, a contact center, or a multi-tenant platform, the routing section is where the practical work lives.

What a VoIP Phone Number Is at the Network Level

A VoIP phone number is a Direct Inward Dialing (DID) number that a carrier agrees to route to an IP endpoint instead of a copper pair. The number itself is indistinguishable from any other PSTN number: it sits in a rate center, belongs to an NPA-NXX block, and is reachable from any phone. What changes is the delivery: the carrier sends the call as a SIP INVITE to your SBC or SIP trunk endpoint, and from there, routing is entirely in your control.

How DIDs Reach Your SBC

Carriers allocate DID blocks from the NANP (North American Numbering Plan) or equivalent national plan. Each DID maps to an NPA-NXX that determines the rate center and the regulatory obligations that come with it. Toll-free numbers (8XX) use a separate SMS/800 database for routing. What matters at the SBC layer is how these numbers arrive: as digits in the Request-URI or To header of an inbound SIP INVITE, which the SBC’s routing engine uses to decide where the call goes next. For the E.164 normalization patterns that make this routing work across international dialing plans, see E.164 Phone Number Format.

Hosted VoIP Numbers vs Bring Your Own Carrier (BYOC)

There are two common ways to get a VoIP number working for you, and they sit at opposite ends of the control spectrum.

Hosted VoIP numbers

In the hosted model, your provider owns and provisions the number inside their own platform and hands you a way to use it, typically SIP credentials or an app. This is the simplest path. You do not manage trunks or routing, and the provider absorbs the operational detail. The trade-off is control: your numbers live inside someone else’s system, and moving away later can be awkward.

Bring Your Own Carrier (BYOC)

In the BYOC (Bring Your Own Carrier) model, you source DIDs and SIP trunks from one or more carriers of your choosing and route them through your own infrastructure. You take on more responsibility, and in return you get portability across platforms, the freedom to use multiple carriers for redundancy and better rates, and independence from any single vendor’s ecosystem. When you change your UCaaS or contact center platform, your numbers and carrier relationships come with you.

BYOC is where an SBC becomes essential, because something at your edge has to terminate those carrier trunks, secure them, and decide where each inbound number should land. That edge function is what the rest of this article is about.

How an SBC Routes an Inbound DID Call

Here is the path a typical inbound call takes. The originating caller’s carrier hands the call to your provider, the call crosses a SIP trunk to the edge of your network, and from there it has to reach the right downstream platform, whether that is an IP-PBX, a contact center, a softswitch, or Microsoft Teams.

The dialed DID rides inside the SIP INVITE, in the Request-URI and the To header. When the call hits your edge, the SBC reads that number and matches it against its routing rules to decide where the call goes next. Because an SBC operates as a Back-to-Back User Agent (B2BUA) rather than a lightweight proxy, it fully terminates the incoming call leg and originates a fresh leg toward the chosen destination, which gives it complete control over both sides of the call. Different DIDs can map to entirely different destinations, so one number range can route to a contact center while another lands on a specific tenant’s PBX. ProSBC drives this with a rule-based routing engine that supports complex multi-route, priority-based, and configurable routing, and it scales to as many as 1,024 Network Access Points so a single platform can front many carriers and many downstream systems at once.

At this same edge the SBC also hides your internal topology, normalizes SIP differences between carriers and platforms, and enforces security at the perimeter. Those functions are the subject of their own guides, so we will not repeat them here, but they are happening on every call alongside the routing decision. For multi-tenant operators, the routing-by-DID model is what lets one deployment keep each customer’s number ranges cleanly separated.

Outbound Caller ID and STIR/SHAKEN

On outbound calls, the DID appears as the calling number in the From and P-Asserted-Identity headers. The SBC controls which number is presented on each leg and can enforce caller-ID policy per trunk group. STIR/SHAKEN attestation applies to every outbound call: the SBC signs the call through an external signing service, and the attestation level (A, B, or C) depends on whether you can verify the caller’s authorization to use that number. For the attestation mechanics, see A-Level Attestation. The “VoIP Caller” label that consumers sometimes see on incoming calls is an analytics-engine decision downstream, not something the originating SBC controls directly.

Ported numbers follow the same DID routing pattern. The carrier that won the port delivers the call to your SBC exactly like any other DID; the SBC routes it based on the digits in the INVITE, not the number’s original carrier. For the porting process and its impact on routing, see Number Porting for ISPs and Carriers.

Conclusion

A VoIP phone number is a DID: a software-defined identifier that a carrier routes by policy, which is what lets you choose between hosted simplicity and BYOC control, present a local number anywhere, and send different numbers to different platforms. The flexibility is the whole point, and the SBC is the element that turns a dialed DID into a delivered call by reading the number, applying your routing rules, and handing the call to the right destination.

Frequently Asked Questions