Common Reasons for Rejection

When submitting a porting request, every bit of information must be correct, otherwise the LCP will reject the request. While some of these reasons may seem pedantic and petty, the nature of the porting beast is such that everything needs to be correct. This page will run through a few of the more common reasons for rejection we get from LCPs, so you know what to look out for before you submit a request. Ideally, LCPs will give us every reason for rejection when they reject a port request, however they can occasionally stop validation as soon as they find the first, meaning it’s better to try to get everything correct at the first time of asking rather than submitting in the hope that you’ll find all the correct information. As a general rule, the best option for trying to get information correct at the first time of asking is to talk to the current provider on the customer’s behalf, using the porting Letter of Authority.

Code 6 - Porting telephone number missing or invalid

The MBN is either incorrect or invalid.  Please ask the current provider to confirm the correct MBN and ensure that the number is in service.

Code 25 - Single Line Order but porting telephone number is Multi Line

Often a customer may assume that because they only have one actual telephone number, it must be a Single Line installation. This is not always the case, as the line type depends on how it was installed - we regularly see single numbers that are actually classed as a Multi Line installation. The best way to be sure of the installation type is to check with the provider - they should give you this information if you can verify the account information.

Code 26 - Multi Line Order but porting telephone number is Single Line

Very similar to code 25 - a customer may assume that because they have multiple numbers installed at the same address, it must be a Multi Line order and attempt to port every number in one request. While this is usually the case, it may be that all numbers are installed separately and must be submitted as individual requests. Again, this is information that the current provider should be able to give you.

Code 30 - Telephone Number Already Ported

Often with resellers, the end-user may be unaware who the true host network is. This is often the case with resellers who may be selling numbers from a range of different wholesale providers. Thankfully with this error code, the rejection will have to come with information about who the correct LCP is.

Code 31 - Customer has no service with LCP

A similar issue to Code 30, but rather than being ported away from the LCP in the original attempt, this means the number wasn’t ever ported to them in the first place - again, often confusion that comes with resellers. Unlike code 30, however, we won’t be able to advise you on who the correct LCP is, and the suspected provider will need to be chased for more information.

Similarly to Code 6, this can also mean the number is no longer in service.

Code 41 - LCP Installation Postcode invalid

Postcodes are used as a way to verify porting orders, without the correct one a port request cannot be accepted and we are unable to request further information relating to the installation.  Please note the postcode must match the one held on file by the Losing CP, this is not necessarily the one shown on the customer’s bill.

Code 44 - Telephone number(s) associated with MBN missing or invalid

This can often be related to Code 25, though not always mentioned if there are other reasons (such as postcode) to withhold information. Customers can often be unaware of associated numbers on their accounts, but with a code 44 an LCP should send us the specific numbers that are missing from the port order, meaning (like with code 30) it’s an error we’ll only receive once.

These are the main day to day issues we come up against in porting, however providers will always find ways to surprise us with problems nobody knew existed, thanks to the magic of Error Code 15 - Other. We’ll always do our best to investigate and find more information on these, and if you need any advice on any of the other rejection codes we receive, feel free to create a follow up to the ticket and we’ll endeavour to get as much information as the LCPs are willing to provide.