A US local number — a DID, for Direct Inward Dialing — gives your customer a presence in a specific place. That local presence is the whole point: a business with a Nashville number feels local to Nashville, and calls to it route directly to the right endpoint on your platform. Behind that simple idea sits a body of reference data that most people never think about until it fails: rate centers, the LERG, and Local Routing Number dips. Get them right and DIDs quietly just work. Get them wrong and you get misroutes, billing disputes, and porting that drags on for weeks while a customer waits.
This is a practical explanation of what actually makes US numbering work, aimed at the resellers and platforms who provision it and have to answer for it when something goes wrong.
NPA-NXX and rate centers
US numbers are organised by NPA-NXX — the three-digit area code (NPA) plus the three-digit exchange prefix (NXX). That combination maps to a rate center: a defined geographic area used for billing and routing. A number is therefore never just ten digits; it carries a geography and, with it, a set of rules about how calls to and from it are rated and routed. When you provision a DID in a particular rate center, you are giving your customer a presence in that place, with all the jurisdictional consequences that follow.
For a reseller, rate-center coverage is a direct measure of what you can actually sell. If a provider is thin in the markets your customers care about, you cannot give those customers a genuine local presence, and you will lose them to someone who can.
Why the LERG matters
The LERG — the Local Exchange Routing Guide — is the industry reference that maps NPA-NXX blocks to their LATA, OCN, rate center, and state. It is how any network determines whether a call is interstate, intrastate, or local, which in turn determines how the call is rated. A numbering provider that resolves DIDs against a real, current LERG table is giving you accurate jurisdiction and predictable billing. A provider that guesses is setting up a dispute you will only discover on an invoice weeks later.
The LERG is not static — blocks are assigned, reassigned, and updated — which is why current data matters. Jurisdiction accuracy is not a one-time setup; it is an ongoing discipline.
Portability and the LRN dip
Number portability is a genuine consumer benefit and a trap for lazy numbering. When a number ports from one carrier to another, its original NPA-NXX prefix stays the same, but the carrier and switch it actually routes to change. The dialled prefix becomes a poor guide to where the number really lives. The tool that resolves this is the Local Routing Number (LRN) dip: a lookup that reveals which carrier and switch a specific number currently routes to, independent of its original prefix.
Correct numbering dips the LRN for ported numbers and does it on both the calling and the called number, then runs the result back through the LERG for jurisdiction, rather than trusting the dialled digits. This is more work per call, and it is the difference between billing that reconciles and billing that starts arguments — particularly on the intrastate traffic where the money is.
Getting porting right
Porting is where numbering promises are tested. A port that goes smoothly is invisible; a port that goes wrong strands a customer between carriers with a number that half-works. The things that make porting reliable are unglamorous: accurate customer service records, clean submission, and a provider who handles rejections proactively instead of letting a port sit. Ask any prospective numbering partner about porting timelines and, more revealingly, about how they handle rejections — the answer tells you whether porting is a managed process or a hopeful one.
- Confirm real rate-center coverage for the specific markets your customers serve.
- Ask whether jurisdiction is LERG-derived and whether numbers are LRN-dipped on both legs.
- Check porting timelines and, more importantly, how rejections are handled.
- Make sure number-level routing and forwarding are in your control, not the provider's.
Hadlo provisions wholesale US DIDs with LERG-accurate jurisdiction, independent LRN dips on both the calling and called number, number-level routing control, and fast porting handled as a managed process. If you need dependable local numbering that just works, talk to us.