Number Porting Process & Lifecycle
Master the mechanics of Local Number Portability (LNP), LOA exact-matching, LRN dipping, and E911 provisioning to ensure flawless origination routing and zero-downtime migrations.
How Local Number Portability Actually Works
Local Number Portability (LNP) revolutionized telecommunications by divorcing phone numbers from the physical copper lines and switches that originally hosted them. However, this flexibility introduced immense routing complexity. When a number ports, its NPA-NXX prefix no longer definitively identifies the terminating carrier.
To solve this, the telecom industry utilizes the NPAC (Number Portability Administration Center) database. When a call enters the PSTN, the originating switch performs a database dip to retrieve the Location Routing Number (LRN). The LRN is a 10-digit number representing the physical switch where the ported number now resides. The call is then routed across the backbone to the LRN, not the dialed number.
The Porting Request Lifecycle End-to-End
A successful port request strictly follows a regulated, multi-step lifecycle to ensure consumer protection against unauthorized transfers (slamming).
1. CSR Retrieval: Before porting, the winning carrier (or reseller) requests the Customer Service Record (CSR) from the losing carrier to verify exact account details.
2. LOA Execution: The customer signs a Letter of Agency (LOA) authorizing the winning carrier to move the numbers.
3. Submission & Validation: The winning carrier submits the port order. The losing carrier's automated systems compare the order data against their CSR.
4. Concurrence & FOC: If the data matches, the losing carrier provides 'Concurrence' and issues a Firm Order Commitment (FOC) date.
5. Activation Window: On the FOC date, the winning carrier broadcasts the routing update to the NPAC, updating the LRN globally. The losing carrier simultaneously drops the translation from their local switch.
The LOA and Why Exact-Match Matters
The most critical point of failure in LNP operations is the Letter of Agency matching process. Porting validation is heavily automated by Tier 1 carriers. It is a rigid string-matching exercise, not a semantic review.
The authorized signer name, company name, service address, account number, and Billing Telephone Number (BTN) submitted on the port order must mirror the CSR character for character. A discrepancy as minor as 'Road' versus 'Rd.', or a missing apartment suite, will trigger an instant, automated rejection, resetting the porting timeline to zero.
Pre-Port Checklist
Before submitting a port request, you must have: 1) A recent copy of the losing carrier's bill. 2) The exact BTN (Billing Telephone Number) grouping the lines. 3) The service address listed on the CSR (which often differs from the billing address). 4) Any active PINs or security passcodes required by the losing carrier to release the numbers.
FOC Dates and Realistic Timelines
Carriers operate under mandated timelines for standard simple ports (typically 1 to 3 business days). A simple port involves a single line without complex PBX routing, distinct ring features, or broadband DSL tied to the copper pair.
Complex ports—involving PRI circuits, large sequential DID blocks, or partial port-outs where some numbers remain on the old account—bypass automated systems and enter manual carrier workflows. These complex orders frequently take 7 to 14 days and carry a substantially higher risk of rejection if the remaining services are not clearly defined.
Common Rejection Reasons and Mitigation
- Name/Address Mismatch: The submitted LOA data failed string-comparison against the CSR. Always demand a CSR pull before submitting the final order.
- Pending Orders: The losing carrier account has an open service order (e.g., a recent address change or feature update). Ports cannot process until the open order clears.
- Account Not Current: The losing carrier account is in arrears or suspended for non-payment. The customer must settle the balance before the carrier will concur.
- Port-Out Protection/Freeze: The account has a security freeze applied. The authorized user must explicitly contact the losing carrier to lift the freeze.
- Disconnected Number: A number must be actively ringing to port. If the customer canceled their old service before the port completed, the number drops into a 'snapback' aging pool and cannot be ported.
Toll-Free Porting and RespOrg Transfers
Toll-free numbers (800, 888, 877, etc.) do not operate on the standard LNP/NPAC framework. They are governed by the centralized SMS/800 database.
To 'port' a toll-free number, you are actually executing a Responsible Organization (RespOrg) transfer. The winning carrier assumes the RespOrg ID associated with the number and rewrites the routing tables pointing to their SIP gateways. This process usually clears within 3 to 5 days and is less prone to address-mismatch rejections than local DIDs.
Rate Centers vs LATAs
Numbers are permanently bound to geographic Rate Centers within a specific Local Access and Transport Area (LATA). This geographical binding governs origination constraints.
While cloud PBXs allow nomadic usage (a user in New York making calls from a California DID), the physical transit of that call through the PSTN is still rated based on the DID's assigned Rate Center. Out of Area (OOA) porting—moving a number to a carrier that lacks a physical interconnection presence in that specific Rate Center—will fail.
CNAM Storage vs CNAM Dip
Caller ID Name (CNAM) is not carried natively within the SIP INVITE signaling path. It operates on independent databases (LIDB).
CNAM Storage involves publishing your business name to the national registry, binding it to your DID so downstream terminating carriers can display it. A CNAM Dip is an inbound action—when a call hits your network, your carrier dips the database to fetch the originating party's name for display on your handset. Wholesale carriers bill CNAM Dips as micro-transactions per query.
E911 Provisioning & Dynamic Location
Federal regulations mandate that all interconnected VoIP numbers maintain a valid, dispatchable location for E911 services. Unlike legacy copper lines permanently wired to a physical address, SIP endpoints are nomadic.
Wholesale providers require that you register a verified E911 address for every active DID via API or portal. When a 911 call originates, the carrier references this database to route the call to the appropriate regional Public Safety Answering Point (PSAP) alongside the location metadata.
Number Lifecycle Summary
The following table summarizes the overarching mechanics of DID control, porting, and routing operations in the wholesale telecom tier.
| Operation | Engineering Detail |
|---|---|
| DID Ordering and Rate Centers | Direct Inward Dialing (DID) numbers are provisioned from specific Rate Centers. Availability is constrained by local NPA-NXX exhaustion. Sequential blocks are available but increasingly scarce in dense urban LATAs. |
| Porting Mechanics (LNP) | Local Number Portability requires a Letter of Agency (LOA) matching the Customer Service Record (CSR) exactly. Once approved, a Firm Order Commitment (FOC) date is set. Common rejections stem from name/address mismatches, pending orders, or accounts in arrears. |
| LRN Dipping | Because numbers can port, the dialed digits rarely indicate the physical switch. Switches perform a Location Routing Number (LRN) dip against the regional database to determine the actual terminating carrier switch before routing the call. |
| CNAM Storage vs Dip | CNAM is not transmitted in the SIP INVITE. The originating provider updates the CNAM Storage database (LIDB) with the caller's name. The terminating provider performs a CNAM Dip against that database to display it to the called party. Dips incur a fractional per-query charge. |
| Toll-Free and RespOrg | Toll-free routing is controlled by a Responsible Organization (RespOrg). The SMS/800 database directs how an 8YY call routes. Pointing a toll-free number to a new carrier requires a RespOrg change, not a standard LNP port. |
| E911 Provisioning | Compliance mandates that interconnected VoIP numbers be provisioned with validated E911 dispatch addresses. Nomadic users must utilize dynamic location routing protocols to update the PSAP database when their physical IP location shifts. |
Frequently Asked Questions
Ready to Connect?
Experience enterprise-grade wholesale termination and origination with transparent pricing and real-time control.