US Number Porting Rejection Troubleshooting helps you quickly identify and resolve carrier rejections that block your phone number migration into Ringover. Understanding common North American rejection codes, required documentation, and post-port routing behaviors prevents unnecessary delays. In this guide, you’ll learn how to diagnose every rejection reason, gather the exact corrective proof, obtain a new Firm Order Commitment (FOC) date, and distinguish a porting block from a post-activation routing issue.
Prerequisites
- An active Ringover account with administrator permissions.
- A submitted US/Canada number porting request flagged with a rejection status.
- A recent Customer Service Record (CSR) or latest monthly telecom invoice (dated within the last 30 days) from your losing carrier.
Troubleshoot and resolve US number porting rejections
1. Identify the rejection cause and required corrective proof
Match the rejection reason reported by your losing carrier against the diagnostic reference table below to prepare the exact required fix.
| Rejection Reason | Root Cause | Required Proof / Document | Corrective Action |
|---|---|---|---|
| Name or Service Address Mismatch | Company name or physical service address on the LOA differs from the losing carrier's CSR (note: P.O. boxes are rejected). | Recent Customer Service Record (CSR) or latest invoice showing the physical service location. | Update the LOA to match the CSR character-for-character (including suite/floor numbers) and resubmit. |
| Account Number or BTN Mismatch | Incorrect account number or wrong Billing Telephone Number (BTN) provided for a multi-line account. | Latest monthly carrier bill or CSR displaying the master BTN and full account ID. | Request the exact BTN from your losing carrier, correct the order form, and resubmit. |
| Incorrect PIN / Passcode | The account security PIN or Number Transfer PIN is missing, expired, or invalid (mandatory for wireless/VoIP). | Valid Account PIN or newly generated carrier port-out passcode. | Generate a fresh Number Transfer PIN in your losing carrier portal and provide it to Ringover. |
| Unauthorized Signatory / Invalid LOA | The person who signed the Letter of Authorization (LOA) is not listed as an authorized user, or the LOA is dated over 30 days ago. | Newly signed and dated LOA from a verified authorized contact on the carrier account. | Have an authorized administrator sign a fresh LOA and upload the updated document. |
| Open / Pending Order on Account | An active service change, billing update, or competing port request is currently open on the line. | Written confirmation from the losing carrier that pending orders are closed or canceled. | Contact your losing carrier to complete or cancel the open order before resubmitting the port. |
| Account Freeze / Port Lock Enabled | Local Carrier Freeze or port-out protection is active on the account or individual telephone number. | Confirmation from the losing carrier that the freeze/lock has been lifted. | Disable Number Lock in your carrier settings or call their support to remove the freeze. |
| Inactive or Disconnected Number | The phone number has already been canceled or disconnected (only active numbers can be ported in the US). | Proof of active line restoration from the losing carrier. | Ask your losing carrier to reactivate the number immediately before re-initiating the port. |
| Incomplete Number Block / Remaining Services | Porting only part of a consecutive DID block, or porting the BTN while leaving active sub-numbers/DSL services behind without instructions. | Full CSR listing all numbers in the block and a new designation for remaining lines. | Include all numbers in the block, or assign a new BTN/disconnect order for remaining services with your carrier. |
2. Submit corrections and secure a new FOC date
Once you have resolved the discrepancy with your losing carrier, resubmit your updated information to obtain a new Firm Order Commitment (FOC) date.
- Reply directly to your open Ringover Porting Support ticket.
- Select the rejected porting request and add your updated LOA, recent CSR/invoice, or corrected Account Number / PIN.
- Wait for confirmation of your new FOC date (the confirmed date and time when your numbers will transfer to Ringover).
3. Escalate persistent rejections
If a carrier repeatedly rejects a valid order despite matching CSR records, escalate the dispute through Ringover's porting team.
- Request an official Customer Service Record (CSR) directly from your losing carrier's porting or retention department (standard monthly PDF bills sometimes omit internal wholesale routing fields).
- Verify that every character on your LOA matches the CSR (including abbreviations like ST vs. STREET or suite numbers).
- Reply to your Ringover Porting ticket with the CSR attached and request a carrier escalation.
- Ringover's wholesale porting specialists will challenge the rejection directly with the losing carrier's LNP (Local Number Portability) desk.
4. Distinguish a porting rejection from a post-activation routing issue
Determine whether your call issue is a blocked port order or a telecommunications routing delay after activation.
Porting Rejection (Before FOC)
The losing carrier refuses to release the number before migration occurs. Your porting status displays Rejected, no FOC date is active, and your number still rings exclusively on your old provider's system.
Post-Activation Routing Incident (After FOC)
The port succeeded and your number is active in Ringover, but incoming calls from specific carriers fail or still hit your old provider. Outbound calls work from Ringover and the number shows as active in your Dashboard, but external carriers have not yet updated their NPAC (Number Portability Administration Center) routing tables (which can take up to 24–48 hours) or your old carrier has not removed the number from their switch.
- Check your Ringover Dashboard > Numbers to confirm your ported number is assigned to an active user or IVR scenario.
- Place test inbound calls from multiple networks (e.g., AT&T, Verizon, T-Mobile, and a landline).
- If calls from one specific carrier still route to your old system more than 24 hours after FOC, contact Ringover Technical Support with 2–3 recent call examples (caller number, called number, and timestamp) so engineers can trigger a routing refresh.
FAQ
How long does it take to get a new FOC date after fixing a rejection?
Once corrected details are resubmitted, US carriers typically respond within 1 to 3 business days with a new Firm Order Commitment (FOC) date. Standard local ports generally complete within 5 to 10 business days total, while toll-free or complex multi-line blocks may take longer.
Can I use a P.O. Box as my service address on the Letter of Authorization (LOA)?
No. US telecom regulations require a physical street address where the telecommunications service is registered. Even if your billing address is a P.O. Box, you must enter the physical service address listed on your Customer Service Record (CSR).
What happens if I only want to port one number out of a multi-line account?
If the number you are porting is not the Billing Telephone Number (BTN), you can port it individually without affecting remaining lines. If it is the BTN, you must first contact your losing carrier to assign a new BTN to the remaining numbers—or authorize disconnecting them—before the port will be approved.
🎉 You now know how to diagnose and resolve US number porting rejections and can complete your number migration into Ringover smoothly without service interruptions!