Introduction:

When you decide to port your numbers from one telecommunications provider to another, it’s crucial to be aware that the process might not always go smoothly. The validation process by the losing provider can sometimes result in a rejection, which temporarily halts the porting process. This article outlines the processes involved in validating a port and discusses the common reasons behind port rejections. It also provides recommendations on minimizing the risk of rejections and outlines the steps for disputing a rejection with the losing provider.

Minimizing the Risk of Rejection:

The porting process, as defined by the Communications Alliance in the Number Portability Code, is inherently strict. For the validation process by the losing provider to succeed, every piece of information in the porting application must be 100% accurate. To reduce the chances of rejection, it’s highly advisable to contact the losing provider before initiating the port to confirm the following:

1. All details are correct.
2. The customer is the rightful owner of the number.
3. The number(s) are active and not subject to pending disconnections.
4. Clarify whether the number needs to be submitted as a CAT-A or CAT-C.
5. Ensure all associated numbers that need to be ported together are included.

Request written confirmation of any information received from the losing provider or a Case Reference Number for phone conversations, as this can serve as evidence in case of a dispute.

If any changes to the account or associated services are necessary, these should be made by the customer before the porting application is submitted and confirmed with the losing provider to avoid complications during the porting process. Changes made during the porting process may lead to a rejection by the losing provider.

Disputing a Rejection:

If you believe that the rejection from the losing provider is incorrect based on information provided by them, you can request a dispute to be initiated on your behalf. To submit a dispute, you’ll need to provide a copy of the latest invoice and any written correspondence from the losing provider suggesting that the rejection was incorrect. Alternatively, you can provide a Case Reference Number for phone conversations. Therefore, it’s essential to confirm all information with the losing provider before initiating the port to have the necessary evidence for a dispute.

Once a dispute is raised, the port cannot be resubmitted until the dispute is resolved. The duration of a dispute is not specified in the Number Portability Codes, as it depends on the losing carrier’s investigation and response time.

Common Rejections:

The article outlines common reasons for rejections based on various categories:

CAT-A Rejections: These rejections occur in the context of CAT-A ports, and the article provides specific codes and reasons for rejection. It highlights common issues like inactive services, pending disconnections, complex services, service numbers already ported, telephone number/account mismatch, and pending port out requests.

CAT-C Rejections: Similarly, CAT-C rejections are explained with detailed information on the validation process and common rejection reasons, such as inactive service, pending disconnection, service number ported to another ASD, telephone number/account mismatch, and pending port out requests.

Mobile Rejections: The article covers rejection reasons for mobile number porting, emphasizing issues like pending disconnections and telephone number/account mismatch.

Toll-Free 1800/Shared Cost 1300 Rejections: It details rejections specific to toll-free 1800 and shared cost 1300 numbers, including reasons like pending disconnections, service number ported to another ASD, telephone number/account mismatch, and pending port out requests.

003 – Inactive Service: This rejection occurs when the number’s service is not active in the losing provider’s system. The article explains that the account holder should contact the losing provider to clarify and reactivate the service.

004 – Pending Disconnection or Disconnected Service: This rejection occurs when the number’s service is disconnected or has a pending disconnection. The article advises contacting the losing provider to address the issue and have the service restored or pending disconnection cleared.

005 – Complex Service: In CAT-A ports, the losing provider may reject the port if it is associated with a complex service. The article recommends contacting the losing provider to resolve the issue or opting for a CAT-C port to avoid complications.

010 – Service Number Ported to Another ASD: Rejections may occur when the number has already been ported to another carrier. The article suggests contacting the current provider to withdraw the porting request and confirm readiness for a resubmission.

017 – Telephone Number / Account Mismatch: This rejection happens when the details on the application do not match the account information at the losing provider. The article advises verifying the account details and contacting the losing provider to rectify any discrepancies.

042 – Pending Port Out Request: Rejections may occur if there is an active port out request associated with the number. The article recommends withdrawing the pending port request by contacting the relevant provider before resubmitting the port.

PNV – Additional Numbers: When submitting a CAT-C port, all associated numbers must be listed and ported together. If additional numbers are discovered during validation, the article provides options for the customer to either port and keep, port and cancel, or disassociate the numbers in cooperation with the losing provider.

PNV – Number(s) Part of a Range/Block: Similar to additional numbers, when a number is part of a range or block, all numbers must be ported together. The article outlines the steps to address this situation.

In summary, this article serves as a comprehensive guide to understanding and addressing rejections in the number porting process, helping customers navigate potential issues and disputes.