Knowledgebase: Phone Numbers
LNP Order Flow and Statuses
Posted by Albert Diaz, Last modified by Taylor Lobo on 02 February 2024 07:14 PM


After an LNP order has been submitted, the receiving carrier will begin processing your request. During this time your order will transition through a series of ‘Statuses’ which indicate the progress of the order.

Status updates are delivered via email to the Partners main address on their profile and to Staff members that are subscribed to LNP Notifications.

The status and details of any LNP order can also be viewed in the LNP section of the RingLogix portal by clicking the edit icon for that order.


Typical Order Flow

Once the processing begins, the first status is usually Acknowledgement. This indicates the order has passed the validation step and is assigned an official PON (Purchase Order Number).

It then proceeds to Pending. Orders in Pending status have been submitted to the losing carrier are awaiting an approval via a Confirmation status with an FOC date (Firm Order Commitment) or a Rejection/Error status with a supporting reason.

When an order reaches Confirmed it means it has been approved by the losing carrier and the phone numbers will transfer on the provided FOC date and time.

Please Note: The FOC date is assigned by the losing carrier and does NOT always match the Desired Due Date requested on the order. You must review the Confirmation status update to determine when the transfer will take place.

After the numbers on your LNP request have transferred, the order status will be updated to Completed. At that time, you should call a number from your order using an Offnet source like a cell phone to ensure it is routing to our network. In the unlikely event you experience any issues with your newly transferred number please contact our support team right away for assistance and be ready to provide a failed call sample. Our team will review the issue and escalate to the receiving or losing carrier as needed.

Always remember to have your phone number routing completed in the RingLogix portal and the customers equipment before the FOC date to avoid any service interuptions.


Handling Rejections and Errors

A Rejection status may occur if the losing carrier rejects the LNP request. A rejection update will contain a reject code which should indicate the reason the losing carrier rejected the order. A list of reject codes is provided below. Please note that while the receiving carrier takes steps to prevent rejections this is outside of their control. Should an order get rejected please review the reason why and open a ticket with our support team to help update and proceed with the order.

If an order is rejected or errored and has not been corrected for more than 10 days from the date of the update, the order will be automatically closed by the carriers and the status will be changed to Abandoned. This order is no longer active and will need to be resubmitted if you wish to continue porting the numbers.


Status Details



Order State


Acknowledgement that the LNP Request has been received and the PON created or Supplemental version received. An acknowledgement is received immediately after submitting a request that passes basic editing.



The LNP Request has been submitted to the current Service Provider and awaiting Confirmation (FOC) or Rejection/Error response to the request.



The current Service Provider has provided a Firm Order Confirmation (FOC) that confirms the request details and includes the FOC Date/Time.

The FOC Date/Time provided by the current Service Provider does not always match the requested port Desired Due Date (DDD)/Time on the submitted request.

Therefore, the Partner must review the Confirmation status response to determine when the port will take place.



An Error is generated when the LNP Request does not meet upfront edits/validation. 

Once the error has been investigated, the request will need to be resubmitted with the corrections.



A Reject is generated when the current Service Provider rejects the LNP Request.

The LNP Request cannot be processed until the reject has been cleared. See Reject Codes.

Once the reject has been investigated, the LNP Request will need to be resubmitted with the corrections (SUP-Other) or cancelled (SUP-Cancel).



The LNP Request has been in a Reject/Error state for a specified amount of time (over 10 calendar days) and is no longer considered an open order.



This status indicator confirms that the LNP Request has been canceled. Response to SUP-Cancel request.



The TN(s) associated with the LNP Request are Active in NPAC.



Reject Error Codes

Reject Code

Reject Message



Incorrect Account Number

The Account Number does not exist or is incorrect.


Incorrect Account Telephone Number

The Account Telephone Number does not exist or is incorrect.

When performing a port, all Telephone Numbers must be associated with the same SPID.


ATN/WTN Mismatch

TN(s) requested to port are not associated with the Account Telephone Number (ATN) provided.


Local Freeze

A Local Service Provider Freeze (RSCP) exists on the Account/Line(s) on the LNP Request.

The LNP Request can only be submitted after the end user has contacted their current local service provider to remove the local service provider freeze.


PIN Code Required

A PIN Code is required to complete this Port.


Incorrect Address

This error message usually indicates the local service provider could not find a match to the provided End User Address.


Incorrect End User Name

This error message usually indicates the local service provider could not find a match to the provided End User Name.


Incorrect Auth Name

This error message usually indicates that the Authorization Name does not match the the local service provider's records.


TN(s) Disconnected

The TN(s) are no longer in service with the local service provider.


Port Type - Partial vs Full

The selected Port Type is incorrect.


New ATN Required

The New ATN is missing or incorrect for this port.


Pending Order On Account

A Pending Order exists for the ATN provided. The pending order has to complete or be cancelled before a new LNP Request can be submitted.


Account Mismatch

There were multiple errors processing this port. This can include any combination of fields, but most commonly involves a combination of End User Name, End User Address, Authoriztion Name, and Account Number.

This error can also occur when more information is needed to process this port request.


Required Field Missing

This reject message indicates that the current Service Provider requires a field that has not been populated.

The missing field requirement can be found in Notes.


Manual Rejection

This reject code is used when the current service provider rejects the LNP request for a reason that does not fall within predefined reject codes.

The details surrounding the reject notification can be found in Notes.