This article will outline the parameters, reasons and codes for number porting rejections as outlined by Commsalliance. Please note that some rejection codes are not provided with a comprehensive resolution description. If you have any questions, please contact our porting team.
When submitting a porting application, all information must be correct. We highly recommend contacting the losing provider prior to submitting the application, as well as advising the correct port type (Cat A or C) and any associated services that will need to be included if a Cat C port. Best practice would suggest requesting written confirmation that the service(s) are active and ready for porting.
If any inconsistencies or submission content is found to the incorrect the Losing Carrier Provider (LCP) will reject the porting request.
Porting by nature is a meticulous process, requiring all information to be 100% accurate. As a rule of thumb, the best option for trying to get information correct at the first time of asking is to discuss the numbers in question with the current provider to confirm specific information as detailed above.
This document will outline common rejections, their codes and definition to help inform you when submitting porting applications.
Porting Rejection Codes
Provided by Commsalliance via - Commsalliance-Reject-Codes-V1-030220
001 - Reject Reason - Service Number Not Found
Invalid Service / not present on access provider (AP) systems.
It will be necessary for the end user to contact the losing provider to check if these numbers are still active on their network and are ready for porting.
Inactive/disconnected numbers can’t be ported, so they will need to be restored before we can proceed with processing. This can only be done by the current provider, and the end user will need to contact them to arrange this. Once this has been done, we can resubmit the port.
003 - Reject Reason - Inactive Service
Service has been Temporarily Disconnected.
Inactive services can result from the losing carrier deactivating the service for the number. This commonly occurs when internet services are disconnected and are in a bundle with the ported number. It can also be caused due to a Credit Management Disconnection if there are charges outstanding on a billing account.
The end user will need to arrange to reactivate the number via a postpaid Exchange Based Diversion or an alternative setup.
ULLS Call Diversion (Exchange-based diversion)
Means an exchange-based facility that enables calls to a Telephone Number to be diverted to another Telephone Number (for example, a geographic or mobile Telephone Number) for a period of up to 30 calendar days.
004 - Reject Reason - Pending Disconnection or Disconnected Service
Service is Disconnected or Pending Disconnection.
Please note that even if a number appears to be active and rings when called, it is still possible that there is a pending disconnection order against the number in the losing provider’s system.
Disconnected numbers cannot be ported, and so we cannot progress the porting request until the losing provider has restored the service.
Common reasons for this rejection can include a future-dated disconnection order resulting from Credit Management action for outstanding charges, or for an NBN disconnection/move order.
The end user will need to contact the losing provider directly to clarify the above and to make arrangements for the service to be restored, or for any pending disconnections to be cleared from the number. Once this has been done, we can then resubmit the request upstream.
005 - Reject Reason - Complex Service - eg ISDN, Line Hunt etc
Unable to Cancel Individual Complex Service
Complex service rejections occur commonly when an application has been submitted as a CAT A (Simple) port instead of a CAT C (Complex) port.
Resubmit porting application as a CAT C. Please note that this is by far the most common reason for Cat A rejections, and is why we highly recommend having the losing provider confirm no complexity is attached to the number prior to submission. Complex services include but are not limited to ISDN, line hunts, faxing facility and number ranges.
Category A Process
Means the default process to Port a Telephone Number which is, prior to Porting associated with: (a) a Simple Telephone Service; or (b) a non-Simple Telephone Service which the Losing C/CSP has declared can be ready for Porting using an automated process within two Business Days of receipt of an SNA.
Category C Process
Means the process to Port Telephone Numbers that require project management. This is the default process for Telephone Numbers associated with Complex Telephone Services.
010 - Reject Reason - Service Number ported to Another ASD
Already Ported. Often with resellers, the end-user may be unaware of who the true host network is. This is frequently the case with resellers who may onsell numbers from a range of different wholesale providers.
The positive side of this error code is that upon rejection, our team generally is provided with information on who the correct losing carrier is, allowing for follow up to be made.
Contact our porting team for assistance.
017 - Reject Reason - Telephone Number / Account Mismatch
A mismatch of the requested number to the provided account.
Correction or reconciliation of account/number details. Once the provided application details have been checked, the end user will then need to contact the current provider to ensure that the number is still active under the same account.
018 - Reject Reason - Account Number invalid for Access Provider
The MBN (Main Billing Number) is either incorrect or invalid.
Please ask the current provider to confirm the correct MBN and ensure that the number is in service. This is a very rare rejection reason, as usually the pre-port validation (PNV) process will identify the MBN if it is not included and list it as an associated service that must be ported with the services in the application.
60 - Reject Reason - Incomplete Number Block or Missing Telephone Numbers in Batch
Applicable to Category C (CAT C) porting applications, if a number is missing from a block or group of numbers that must be ported together, then the port will be rejected.
The end user will need to contact the current provider for reconciliation of any missing numbers. This is also a very rare rejection reason, as normally, the pre-port validation (PNV) process will identify any numbers from the number block if they are not included and list them as associated services that must be ported with the services in the application. If any of these services cannot be ported together (e.g. belonging to separate end users) then the current provider will need to disassociate them before we can proceed with your port.
101 - Reject Reason - PNV Associated Services
The pre-port validation (PNV) is rejected by our upstream due to some indial numbers on the losing carrier account not being included in the initial porting request.
Add the additional numbers to the porting request. As above, if any of these services cannot be ported together (e.g. belonging to separate end users) then the current provider will need to disassociate them before we can proceed with your port.
[[title=Number Porting Rejections]]
[[description=Definitions and descriptions on how and why number porting applications are rejected]]