What Is a DID Number? Everything Operators Need to Know

Every phone call your business places or receives routes through a DID. Every caller ID your agents display is a DID. Every local presence strategy, every toll-free vanity number, every inbound IVR menu — all of it runs on DIDs. If SIP trunking is the highway, DIDs are the addresses. And like real addresses, some are worth more than others, some come with history you did not ask for, and managing them well is the difference between a professional operation and one that looks like a robocall shop.

This guide is written by SIPNEX, an FCC-licensed carrier that provisions DIDs across every North American area code. We hold our own STIR/SHAKEN Service Provider certificate and we manage the full lifecycle of phone numbers — provisioning, CNAM registration, attestation, reputation monitoring, and porting. What follows is the carrier-side view of how DIDs actually work and why your number strategy matters more than most operators realize.

What a DID number is

DID stands for Direct Inward Dial. It is a telephone number that routes directly to a specific endpoint — an extension, a queue, an IVR, a SIP trunk — without going through a human operator or auto-attendant first. The term dates back to the PBX era when businesses wanted to give individual employees their own phone numbers without needing a separate physical phone line for each person. The PBX would receive the inbound call on a shared trunk, read the dialed number (the DID), and route it to the correct internal extension.

In the modern VoIP world, the concept is the same but the implementation is entirely virtual. A DID is a phone number that your carrier assigns to your account and maps to your SIP trunk endpoint. When someone calls that number, the call arrives at your carrier’s network, the carrier looks up the DID in its routing table, and forwards the call to your registered SIP endpoint — your PBX, your VICIdial server, your cloud contact center, whatever system is configured to receive it.

DIDs come in three primary types. Local DIDs have a geographic area code — a 214 number is Dallas, a 212 is Manhattan, a 305 is Miami. They signal local presence to the people you call or who call you. Toll-free DIDs use non-geographic prefixes (800, 888, 877, 866, 855, 844, 833) and are free for the caller — the receiving party pays the per-minute cost. Vanity DIDs are numbers that spell a word or phrase on the phone keypad, like 1-800-FLOWERS. They are toll-free numbers with premium pricing based on the desirability of the letter combination.

A single SIP trunk can carry hundreds or thousands of DIDs simultaneously. The trunk is the pipe. The DIDs are the addresses on that pipe. When your dialer places an outbound call, it sets one of your DIDs as the caller ID in the SIP INVITE’s From header. When an inbound call arrives for any of your DIDs, it comes through the same trunk. You do not need a separate trunk per DID — that is PRI thinking. In SIP, one trunk handles all your numbers.

How DID provisioning and routing works

When you order a DID from a carrier, the carrier assigns a number from its inventory — a block of numbers that it owns or has been allocated by NANPA (the North American Numbering Plan Administration). NANPA manages the assignment of area codes and number blocks to carriers throughout the US and Canada. When SIPNEX provisions a Dallas 214 number to your account, that number comes from a block assigned to SIPNEX by NANPA. We own it. We control the routing. There is no intermediary.

The provisioning process creates a routing rule in the carrier’s network: inbound calls to this DID should be forwarded to this customer’s SIP trunk endpoint. The endpoint is identified by IP address and port, or by a SIP URI. When a call comes in from the PSTN destined for your DID, the carrier’s switching infrastructure matches the called number to your routing rule and sends a SIP INVITE to your system.

For outbound use, the DID serves as your caller ID. Your dialer or PBX sets the outbound DID in the From header of the SIP INVITE. The carrier validates that the DID belongs to your account (this validation is essential for STIR/SHAKEN attestation — it is how the carrier determines whether to sign at A-level or B-level), and the call proceeds to the PSTN with your DID displayed to the recipient.

Multiple DIDs can be mapped to different internal destinations on the same trunk. Your main business line (your toll-free number) routes to the IVR. Your sales DIDs route to the sales queue. Your support DID routes to the support queue. Individual agent DIDs route directly to specific extensions. All of this happens through DID-to-endpoint mapping in your PBX configuration — the carrier delivers everything to your trunk, and your system handles the internal routing based on which DID was called.

Number porting: moving DIDs between carriers

Local Number Portability (LNP) is an FCC mandate that guarantees your right to take your phone numbers with you when you switch carriers. You are not locked into a carrier because they provisioned your numbers — those numbers are yours and you can move them.

The porting process works like this: you submit a Letter of Authorization (LOA) to your new carrier. The LOA authorizes the new carrier (the “gaining carrier”) to request a port of your numbers from the current carrier (the “losing carrier”). The gaining carrier submits the port request through the Number Portability Administration Center (NPAC). The losing carrier receives the request and has a defined window to confirm or reject it (rejections must be for specific valid reasons — incomplete LOA information, account number mismatch, unauthorized signer). Once confirmed, a Firm Order Commitment (FOC) date is set. On the FOC date, the number routing in the national database is updated to point to the gaining carrier’s network. Calls to your number now route to your new carrier.

Timeline: simple ports (1-10 local numbers from a single carrier) typically complete in 7 to 14 business days. Complex ports (large blocks of numbers, multiple losing carriers, toll-free numbers) can take longer. Toll-free porting follows a different process — it requires a RespOrg (Responsible Organization) transfer rather than an LNP port, and the timeline depends on the current RespOrg’s cooperation.

The most common reason ports get delayed: incorrect information on the LOA. The authorized name, account number, and PIN on the LOA must match exactly what the losing carrier has on file. A single character mismatch can trigger a rejection that adds days to the process. Before submitting your LOA, confirm your account details with your current carrier.

At SIPNEX, we handle the porting paperwork on your behalf. You provide the LOA and your current account details, and we manage the submission, follow up on FOC dates, and coordinate the cutover. You can start dialing immediately on new SIPNEX-provisioned DIDs while your existing numbers port in the background. There is no gap in service if the port is executed correctly.

DID strategy for outbound dialing operations

If you run outbound campaigns, your DID strategy directly impacts your answer rate. This is not theoretical — it is measurable, and the operators who manage it intentionally outperform those who do not.

Local presence dialing is the practice of displaying a caller ID with an area code that matches the area code of the person you are calling. When you call a 214 number, your outbound CID shows a 214 number. When you call a 305 number, your CID shows a 305 number. The rationale is simple: people are more likely to answer a call from a local number than from an unfamiliar area code. The data consistently supports this — local presence dialing typically improves answer rates by 15 to 30 percent compared to displaying a single static caller ID from a non-local area code.

Implementing local presence requires a pool of DIDs across the area codes you are calling into. If your campaigns target the entire continental US, you need DIDs in every major area code — potentially 200 to 300 numbers. Your dialer must be configured to automatically select the CID that matches the called number’s area code. VICIdial supports this through its CID group functionality, which maps outbound CIDs to called area codes or area code prefixes.

CID rotation spreads your outbound call volume across multiple DIDs within each area code. Instead of placing 500 calls per day from a single 214 number, you spread them across 10 different 214 numbers at 50 calls each. The reason: caller ID analytics companies like Hiya, TNS, and First Orion flag numbers that exhibit high call volume — more than approximately 100 calls per day from a single number triggers pattern detection in most systems. By rotating across a pool, each individual number stays below the flagging threshold.

DID warm-up is the practice of gradually increasing call volume on new numbers rather than immediately dialing at full capacity. A brand-new DID with zero calling history that suddenly places 200 calls on its first day looks like a robocall number to analytics systems. Start new DIDs at 20 to 30 calls per day and increase by 20 to 30 percent every few days until you reach your target volume. This establishes a calling pattern that looks human rather than automated.

STIR/SHAKEN interaction. Every DID in your outbound CID pool must be registered with your carrier and verified for A-level attestation. If you are using DIDs that your carrier has not verified — numbers from a third-party source, numbers that have not completed porting, numbers that were provisioned but never registered in the carrier’s STIR/SHAKEN database — those calls go out with B-level attestation. B-level on a high-volume outbound number is a fast path to spam labeling. On SIPNEX, every DID we provision is automatically registered in our STIR/SHAKEN database for A-level attestation from day one.

DID costs and what affects pricing

DID pricing varies by type, geography, and volume. Here is what the market looks like in 2026 and what drives the numbers.

Local DIDs typically cost $1 to $3 per month per number. The variation depends on the area code — dense metro area codes (212, 310, 312, 214) have large number inventories and competitive pricing. Rural area codes with limited inventory may cost slightly more or have limited availability. Some carriers charge a one-time setup fee per DID on top of the monthly recurring cost. SIPNEX does not charge setup fees.

Toll-free DIDs run $2 to $5 per month per number for standard 800/888/877/866/855/844/833 numbers. Toll-free numbers also carry per-minute inbound charges that local DIDs typically do not — the business receiving the call pays for the inbound minutes. Toll-free per-minute rates are generally higher than local inbound rates because the originating carrier charges the toll-free carrier (RespOrg) for transporting the call.

Vanity toll-free numbers carry premium pricing that varies wildly based on desirability. A number like 1-800-LAWYERS might cost thousands to acquire (if available at all), while a less recognizable combination might be standard toll-free pricing. Vanity numbers are purchased through RespOrg channels and availability is first-come, first-served.

Volume discounts are standard for large DID orders. If you need 500 local presence DIDs across 50 area codes for a national outbound operation, the per-number monthly cost drops significantly compared to ordering 5 numbers. Ask your carrier about bulk pricing — the difference can be substantial.

Per-minute inbound charges may or may not apply depending on your carrier and the DID type. Some carriers include a certain number of inbound minutes in the monthly DID cost. Others charge per-minute for all inbound traffic. SIPNEX keeps this simple: competitive monthly DID fees with transparent per-minute rates for both inbound and outbound traffic, published on our pricing page.

The hidden cost of cheap DIDs. Some carriers and DID brokers sell numbers at rock-bottom prices — $0.50/month or less. The risk: those numbers are often recycled inventory that was previously used by robocall operations, already flagged in analytics databases, and carrying negative reputation history. A “cheap” DID that displays as “Scam Likely” on T-Mobile handsets is not cheap — it is worthless for outbound campaigns. When evaluating DID sources, ask about the number history and whether the carrier performs any reputation screening before provisioning recycled inventory.

Frequently asked questions

What does DID stand for in telecom?

DID stands for Direct Inward Dial. It is a telephone number that routes directly to a specific endpoint — an extension, queue, IVR, or SIP trunk — without going through a human operator. In the VoIP context, a DID is a virtual phone number assigned to your account by your carrier, mapped to your SIP trunk endpoint. Inbound calls to the DID arrive at your system for handling. Outbound calls display the DID as your caller ID. A single SIP trunk can carry hundreds or thousands of DIDs simultaneously. The term originated in the PBX era when businesses needed individual phone numbers for employees without dedicating a separate physical phone line to each person.

How many DIDs do I need for my call center?

It depends on your operation. For inbound-only, you need at minimum one DID per inbound campaign or routing destination — a main line, a sales line, a support line. For outbound with local presence dialing, you need DIDs in every area code you call into — for national campaigns, that means 200 to 300 numbers across major metro area codes. For CID rotation (spreading volume to avoid per-number flagging), multiply your local presence pool by 5 to 10: instead of one 214 number, you want 5 to 10 numbers in 214 rotating through your outbound campaigns. A national outbound operation with proper local presence and rotation might use 1,000 to 3,000 DIDs. On SIPNEX, bulk provisioning at that scale is a standard request with volume pricing.

Can I port my existing phone numbers to SIPNEX?

Yes. FCC regulations guarantee your right to port your phone numbers to any carrier. The process requires a Letter of Authorization (LOA) with your current account details — authorized name, account number, and PIN. SIPNEX handles the port submission, FOC scheduling, and cutover coordination. Simple ports (1-10 local numbers from one carrier) typically complete in 7 to 14 business days. You can start dialing immediately on new SIPNEX DIDs while the port processes in the background. Toll-free numbers follow a separate RespOrg transfer process that may take slightly longer. The most common cause of port delays is mismatched account information on the LOA — verify your details with your current carrier before submitting.

What is local presence dialing?

Local presence dialing means displaying a caller ID with an area code that matches the area code of the person you are calling. When you call someone in Dallas (214 area code), your outbound caller ID shows a 214 number. When you call Miami (305), your CID shows 305. People are significantly more likely to answer calls from local numbers — answer rate improvements of 15 to 30 percent are typical compared to displaying a non-local or toll-free number. Implementation requires a pool of DIDs across your target area codes and a dialer configured to automatically match the outbound CID to the called number’s area code. VICIdial supports this through CID group configuration. Every DID in your local presence pool should be verified for A-level STIR/SHAKEN attestation.

How long does DID provisioning take?

On SIPNEX, new DID provisioning takes 24 hours or less. We assign numbers from our NANPA-allocated inventory, create the routing rules, register CNAM, and add the numbers to your STIR/SHAKEN authorized CID list as part of the standard provisioning process. Bulk orders (hundreds of DIDs across many area codes) may take slightly longer depending on inventory availability in specific area codes. Resellers typically take 3 to 5 business days because they request numbers from their upstream carrier and wait for provisioning before passing them through. The 24-hour carrier-direct timeline versus multi-day reseller timeline is one of the practical advantages of working with a carrier that owns its own number inventory.

---

SIPNEX is an FCC-licensed carrier that provisions DIDs across every North American area code with same-day setup, automatic CNAM registration, and A-level STIR/SHAKEN attestation from day one. Request DIDs for your operation or see our rates.