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 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 US DIDs for SIP trunks and dialers. 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.
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.
You will also see the same numbers sold as “VoIP numbers” or “virtual phone numbers.” The three terms describe one thing from different angles: DID is the telecom term for a number that routes straight to an endpoint, “VoIP number” says the call is carried as voice over IP, and “virtual number” says the number is not tied to a copper line or a SIM. The last hop can be forwarding to a mobile phone, a softphone app, or — the case this guide covers — a SIP trunk into a PBX or dialer.
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 numbers spell a word or phrase on the phone keypad, like 1-800-FLOWERS. The best-known ones are toll-free, and toll-free vanity numbers are normally assigned first-come, first-served, the same as other toll-free numbers.
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, the carrier assigns a number that is provisioned on its network. Numbers reach carriers in blocks: in the US, the North American Numbering Plan Administrator (NANPA) assigns central office codes and the Pooling Administrator assigns thousands-blocks, both to providers that hold numbering authority. A provider without that authority gets its numbers from one that has it. When SIPNEX provisions a Dallas 214 number to your account, it is provisioned on our network and routed to your trunk.
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 — you can move them.
The process runs on paperwork. You sign a Letter of Authorization (LOA) for the new (gaining) carrier, which sends a Local Service Request to your current (losing) carrier. The losing carrier either confirms it with a Firm Order Commitment (FOC) date or rejects it for a specific reason, such as an account number or authorized-signer mismatch. On the FOC date, the port is activated in the Number Portability Administration Center (NPAC) database and calls start routing to the new carrier’s network. Toll-free numbers move differently, through a RespOrg change rather than an LNP port.
Timelines depend on the size of the port and the carriers involved. Our number porting guide covers realistic timelines, what the FCC’s one-business-day rule for “simple ports” does and does not cover, and how to read a rejection.
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, the numbers you present affect whether people answer — and whether they see a spam label first.
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: people screen unfamiliar calls by area code, and a local number is more likely to get picked up. No carrier can promise a specific lift, so measure it on your own campaigns; our local presence dialing guide covers pool design and the compliance limits.
Implementing local presence requires DIDs in the area codes you are calling into — for a national campaign, that can mean hundreds of numbers. Your dialer must be configured to automatically select the CID that matches the called number. VICIdial supports this through CID groups, which can match the outbound number to the called area code or state.
Call volume and registration. The analytics engines behind carrier spam labels (First Orion for T-Mobile, Hiya for AT&T and Samsung, TNS for Verizon) score numbers on calling patterns and complaints, and none of them publishes a per-number call limit. Size your pool to the consented calling you actually do, not to keep each number under an engine’s radar, and register every number with the engines before it dials.
Once the pool is settled, register it — our guide to business phone number registration by caller type covers which portal applies.
STIR/SHAKEN interaction. Every DID in your outbound CID pool must be one your carrier has verified you are authorized to use, so it can sign your calls at A-level. If you are using numbers your carrier has not verified — numbers from a third-party source, or numbers that have not completed porting — those calls go out with B-level attestation at best. Analytics engines treat partial (B) attestation as a lower-trust signal, which matters most on high-volume outbound numbers. On SIPNEX, every DID we provision to your account is signed at A-level from day one.
DID costs and what affects pricing
DID pricing varies by type, geography, and volume. Here is 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 called party’s side pays to carry the call from the caller’s network.
Vanity toll-free numbers are reserved through RespOrgs and, like other toll-free numbers, normally assigned first-come, first-served. FCC rules (47 CFR 52.107) prohibit hoarding toll-free numbers and selling them for a fee, outside numbers assigned by competitive bidding, so the real constraint on a memorable combination is whether it is still available.
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. SIPNEX bulk orders are filled from US inventory by area code and quantity, with CNAM on every number — details on our DID numbers service page.
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 charges a flat monthly fee per DID, and our pricing page publishes our outbound per-minute rates; confirm inbound minute charges with any carrier before you order.
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 can be 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 numbers in the area codes you call into, which for a national campaign can mean hundreds. Size the pool to the consented calling volume you actually run, not to keep each number under an analytics threshold, and register every number with the analytics engines. On SIPNEX, bulk provisioning 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. Timelines depend on the size of the port and the losing carrier. 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. The most common cause of port delays is mismatched account information on the LOA — verify your details with your current carrier before submitting.
How long does DID provisioning take?
Most SIPNEX DID orders provision the same day. We assign the numbers, create the routing rules, register CNAM, and add the numbers to your STIR/SHAKEN authorized CID list as part of the standard provisioning process. Large orders across many area codes can take longer, depending on availability in each rate center.
SIPNEX provisions US DIDs with CNAM registration and A-level STIR/SHAKEN signing from day one. To size an order for your trunk or dialer, call (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.