Description: This document will provide you with basic troubleshooting of your failed orders.
There are a variety of reasons why your Order may have failed when you tried to create your port. The most common reasons that a number, or numbers, may fail are:
Error: There is already an existing record with NPAC for that particular number. NPAC only allows for one active-like record for a number at any given time.
Example 1: An SV in "cancel pending" is still considered active-like, until it fully moves into a "cancelled" or "old" status.
Fix: Wait until the cancel pending has completed to cancelled or old status. There are cancel timers you will have to wait for.
Example 2: There is already an existing record with NPAC for that particular number (possibly built by the losing service provider) and the information you submitted did not match what the losing service provider built
Fix: Check that the Losing Service Provider has built concurrence for your SPID with the same dates and times.
Example 3: Failed - NPAC SMS allows only one of pending, cancel pending, conflict, disconnect pending, failed or partial failure Subscription Version per TN.
Fix: Reach out to the Losing SPID and confirm that they have built a record for your SPID.
Error: This Service Provider has already issued a create for the subscription version
Fix: Create new SV if it still applies
Example 4: Failed- Cannot create LISP, after dashX creation, before block is created
Fix: There is no fix as more than 10% of numbers have been ported and you have reached the limit until the block is activated.
Contamination occurs when at least one Telephone Number (TN) within a Thousands-Block (NPA-NXX-X) of TNs is not Available for Assignment to end users or customers. Thousands-Blocks contaminated up to and including 10 percent are eligible for Donation/return. For purposes of this provision, a TN is not Available for Assignment if it is classified as Administrative, Aging, Assigned, Intermediate, or reserved as defined in Federal Communications Commission (FCC) rules (47 CFR § 52.7 (h))
Comments
0 comments
Article is closed for comments.