|
This article is to give a brief overview of LNP concepts and some commonly asked questions about porting and the porting process. Below is a brief table of contents of the information in this article.
If you have any further questions or concerns regarding porting, please feel free to open a ticket with our LNP Team.
▂▃▅▇█▓▒░Table of Contents ░▒▓█▇▅▃▂
☏ What is Local Number Portability (LNP)?
☏ What is required of an LOA?
☏ What is a Partial Port?
☏ How do I submit a port with multiple carriers from the same account?
☏ When should I expect to receive an FOC or Confirmation on the port?
☏ What time do ports complete/activate?
☏ Can a requested FOC be updated after a port is submitted?
☏ Can a new FOC be requested after a confirmation has been granted?
☏ How to Cancel an LNP Port?
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
What is Local Number Portability (LNP)?
Local Number Portability is the transferring of Telephone Numbers from one carrier to another.
In order for numbers to process a port order, RingLogix requires the following information be provided in a signed LOA (Legal Order of Authorization).
An example of RingLogix LOA template can be found in the ‘Start Selling’ zip folder provided to our partners.
If you need a copy of this folder, please feel free to reach out to your CSM or open a ticket with our LNP department.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
What is required of an LOA?
Below is a list of required information that carriers need in order to process a port.
Along with details of each field.
1. Company Name (also referred to as an End-User Name)
This is the name of the company as it appears in the Losing Carriers records. Sometimes a customer may have opened the account using their Full Name.
2. Authorized Contact (Full Name in Print & Signature
RingLogix LNP Team cannot process a manual port order without a signed LOA provided in the ticket.
The Authorized Contact for an account would be the account holder for these services.
3. Service Address
An address listed on the account where services are provided.
This is sometimes, but not always, different from the Billing Address.
4. Account Number
The account number is the identifier for carriers to confirm the location of services for an account.
This can sometimes, but not always, be the same as the number porting.
5. Billing Telephone Number (BTN) or otherwise known as an ATN (Account Telephone Number)
This is the number that is the main line on the account.
If there is a port with only one number on the account, it is safe to assume that this number would also be its own BTN.
6. Account PIN Code (not always required
Some carriers require a PIN Code upon submission of a port, else it cannot be submitted.
7. Desired Port Activation Date (also not required)
Some carriers will require 5, 7, or even 14 business time-period to process ports. It is, for this reason, the dates available will fluctuate between port orders.
A specific date requested by the customer for activation. If a date is not specified, the default date of selection should be 7-days from the submission date.
If a customer requests for another port date after an FOC is granted, changes CANNOT be made within 48-hours of the current FOC date.
If a port receives a rejection for any reason regarding the account information provided, it is highly advised that the customer request for a Customer Service Record (CSR).
A CSR must be in PDF format in order to be used to dispute a rejection with the Losing Carrier.
For more information on how to process a port via the LNP Portal, please click here for a walkthrough guide.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
What is a Partial Port?
The following is what a partial port would be considered
Example A
The customer has 10 DIDs and will port 7 of them.
If the customer is porting the ATN you must provide a New ATN
Normally you would pick the DID lowest in count
13055550000 Porting
13055551111 Not Porting / New ATN
13055552222 Porting
13055553333 Porting
13055554444 Not Porting
13055555555 Porting / ATN
13055556666 Porting
13055557777 Not Porting
13055558888 Porting
13055559999 Porting
Example B
The customer has 10 DIDs and will port 7 of them.
If the customer is Not porting the ATN you will not need a New ATN
13055550000 Porting
13055551111 Not Porting
13055552222 Porting
13055553333 Porting
13055554444 Porting
13055555555 Not Porting / ATN
13055556666 Porting
13055557777 Not Porting
13055558888 Porting
13055559999 Porting
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
How do I submit a port with multiple carriers from the same account?
Sometimes a customers account may have multiple carriers involved with their numbers.
Port Orders can only process 1 carrier per submission.
In cases like this, 1 port per carrier will need to be submitted in order for processing.
Typically, we recommend submitted each port as a "Full Port" to avoid any rejections.
The BTN/ATN for each port should be one of the DID(s) porting.
For example, imagine the numbers below belong to the same account but different carriers.
13055550000 - Frontier Communications
13055551111 - Bell South
13055552222 - Frontier Communications
13055553333 - Frontier Communications
13055554444 - Bell South
The Bell South and Verizon Numbers would need to be on their own port orders.
And all numbers on each port should belong to the same carrier.
For this reason, they would be submitted as per the example below.
Port # 1 - Frontier Communications
13055550000 - BTN
13055552222
13055553333
Port # 2 - Bell South
13055551111 - BTN
13055554444
Both ports can be submitted using the same account information, such as account number, service address, company name, etc.
Should any of the ports return rejected, we recommend having the customer reach out to the Losing Carrier to obtain a CSR.
The CSR should be in PDF format and come from the actual carrier, not the provider.
To verify if your customers numbers are from various carrier, you can open a ticket with our LNP Team to run a carrier check on them.
They will then respond providing a carrier break-down for the numbers provided.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
When should I expect to receive an FOC or Confirmation on the port?
Losing carriers typically respond 3-5 business days to a port request.
Some carriers may take longer depending on their flow and queue of requests.
If a port is in ‘Pending’ status for a long period of time, it is recommended to have the customer reach out to their carrier for a status update or request a response to the port order.
Once an FOC is received, the numbers will be added to your customers DID Inventory so routing can be setup prior to the ports completion.
This can minimize down-time and even allow to basic on-net call testing of the routing.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
What time do ports complete/activate?
All ports are set to automatically complete at 10AM ET (9AM CT | 8AM MT } 7AM PT)
A customer can request for another time of completion between the hours of 10AM EST and 4PM EST via a Ticket.
This timeframe is to fit the working office hours our carriers.
No ports can complete outside these office hours as it can risk a lot of issues and having no assistance if an issue were to arise.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
Can a requested FOC be updated after a port is submitted?
Yes, a ports Desired Due Date can be edited after a ports submitted.
If an FOC cannot be updated via the Portal, please open a ticket with the new requested date.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
Can a new FOC be requested after a confirmation has been granted?
So long as a port order is not being updated within 48-hours of the current completion date, an new FOC can be requested.
That being said, it is to be noted that this would cause the port to lose the current FOC, which cannot be reversed once updated.
This is because updating the FOC requires the Losing Carrier to respond
Once updated, the port will be in 'Pending-Submitted' status until the Losing Carrier
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
How to Cancel an LNP Port?
It is important to note that ports cannot be cancelled within 48-hours of a confirmation date.
This can lead to risks of breaking a port and losing the numbers altogether from either of the carriers.
Automated ports can be cancelled in the LNP Portal or requested on the ticket for manual ports.
☏ • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ✆
For more information about other porting processes, please feel free to review our other Knowledge Base Articles below.
LNP Order Flow and Statuses
Route Phone Numbers to a Service
Phone Number Features
Number Port Out Processes and Inquiries
| 