Landline number porting rejected

[#1]

Plusnet don't have an entry on that list; presumably that means that they are included as BT,

Correct

but is there a way to find out what the 3-digit CUPID is (as BT have multiple entries)?

Its the first in the list - 001 .

[#2]

---

@Peter-J wrote:

Might Plusnet have a record of number porting requests sent to them? If so, I'd be grateful if you could ask your contact for details of the outcome of any porting requests made for my number.

---

Hi Peter, we don't as we're not involved in the process - A&A as the gaining provider should be speaking with Openreach. I've however reached out to OR and it looks like the port was rejected in error, on this occasion. 

They'll be investigating to try and make sure it doesn't happen again, but if A&A resubmit, it should be accepted.

I hope this helps.

[Gandalf,]

Thanks Gandalf,

Unfortunately A&A have a lack of visibility with the number porting process because it is handled by sales people forwarding the request to their supplier, Magrathea, who in this case simply reply that the number is "not in service".

It would be good to have more information about the error that caused the port to be rejected, as it is likely that many other people will experience similar over the next couple of years.

[#4]

Ah I meant it was mistakenly rejected, instead of being accepted. I don’t have anymore information, as the order wasn’t placed by us. It’s down to the gaining provider to manage this. It may be worth forwarding what I’ve found out to them and see what they say. I just wanted to check there’s nothing within our influence causing an issue and from my investigation, I’m confident there isn’t. 

[Unfortunately A&A have a lack of visibility with the number porting process because it is handled by sales people forwarding the request to their supplier, Magrathea, who in this case simply reply that the number is "not in service".]

Unfortunately A&A have a lack of visibility with the number porting process because it is handled by sales people forwarding the request to their supplier, Magrathea, who in this case simply reply that the number is "not in service".

@Peter-J interesting to look at the Magrathea website

https://www.magrathea-telecom.co.uk/service/numbering/number-porting/

Particulary the statements

We are able to use our direct relationship with major carriers, including BT, to help provide number portability to your clients. 

and

Our efficient and knowledgeable number porting team has deep expertise, built up over many years working with the major networks. Our excellent client focus team is ready with help and advice should you need us.

Which begs the question, why did they not use that relationship & expertise to query the port rejection with BT/Openreach directly ?

[#6]

Hello, A&A had told me that they would escalate this with Magrathea, who have now responded to them as follows:

---

In order to port we would need the number back in service as this
scenario does not come under the 30 day retention period. I would highly
recommend that the end user speaks to their previous provider as they
are the only ones that will be able to assist here.
Apologies that there is nothing more we can do this end.

 A&A then tell me to "please ask your current suppliers to re-instate the number and we
will resubmit."

This seems awkward as Plusnet no longer offer new telephone lines; does anyone know if I can cancel my change from FTTC to SoGEA as the new contract begun less than 14 days ago?

[#7]

Someone is having laugh.

[#8]

@Peter-J as @jab1 says, they're talking complete and utter rubbish!

It should be covered by the 30 retention period, it was ceased less than 30 days ago and is being ported by the original 'owner' (I assume you were the Plusnet account holder?).

As John says, its almost certainly not possible to reinstate the number due to the Openreach stop-sell and I would have thought that A & A/Magrathea are well aware of that.

Ultimately the process is GPL (Gaining provider lead) and it is the responsibility of the gaining provider to sort out any problems.

It sounds to me like Magrathea haven't gone back to Openreach as advised. From what @Gandalf  said earlier, I would 'guess' that Openreach were returning an incorrect status to the port request. That may be why Magrathea think its not covered. In which case when they now go back to OR they will get the correct status and be able to complete the port

Have you told A & A that Openreach have now corrected their system and the port can be resubmitted ?

[#9]

@MisterW TBH, I'm extremely surprised at the A&A responses - they must have carried out 100's of these transfers?

[#10]

@jab1 yes, that's the odd thing. Reading between the lines (we will never know exactly) , its seems that OR got things slightly wrong in this case. Maybe they returned a status which didn't show that the line was in the 30 day retention period. Whatever it was , according to @Gandalf they have corrected it and the port should complete. It would seem that Magrathea are reporting the previous results and haven't resubmitted the port.

[#11]

I am sorry that I cannot help you, but I have an observation and some suggestions. In your first post you stated "...port had been rejected as there was already a port order in effect". That makes me wonder if your number was in the process of being ported to another provider, before you started the port to A&A, and that is causing the porting failure to A&A. A&A's and Magrathea's replies imply that your number is not, in fact, ceased and in quarantine.

Suggestions:

1. Double-check that A&A are trying to port the correct number!

2. Think about what other steps you made around the time you regraded to SOGEA: did you consider or try a port to another provider?

3. Contact A&A's owner and director "RevK" on Mastadon: revk@toot.me.uk; he is very helpful and knows his stuff.

4. Give up on A&A and ask Voipfone to port your number. Voipfone relish a challenge.

To rub salt into the wound, my regrade to SOGEA completed on Tuesday, I initiated a port to A&A on Thursday morning and received confirmation that the port had been accepted later that day. So, on the basis of one example only, there doesn't appear to be a system-wide problem porting to A&A.

Good luck!

[#12]

@Lawrencium103 thanks for that confirmation. That would indicate that there isn't a systemic problem and that, as investigated, Openreach got something wrong initially on ceasing just this number and once discovered, they have corrected it and the port should now complete if re-submitted. If they're not willing to just resubmit, then all it takes is for Magrathea to contact the Openreach porting desk (as a porting provider they have the contact details!) and check first.

[Lawrencium103]

Hi Lawrencium103

Good to hear that you haven't encountered the same difficulty. It seems unfair, the process is widely misunderstood even by those operating it, both providers still blame each other, and no accurate reason has been given for the porting rejection.

To your suggestions: (1) I asked A&A to check, (2) no other provider was considered, (3) & (4) Thanks, I might try those!

[MisterW I've seen mention of an Openreach porting desk and a BT porting helpdesk. Are both usually involved or just OR, and do you know how the validity of a porting request is checked - what has to match for the port to be accepted? A&A's order process asks for the Plusnet account number which I provided, but could that actually be checked given that the losing CP isn't consulted and Plusnet aren't the Range Holder?]

MisterW I've seen mention of an Openreach porting desk and a BT porting helpdesk. Are both usually involved or just OR, and do you know how the validity of a porting request is checked - what has to match for the port to be accepted? A&A's order process asks for the Plusnet account number which I provided, but could that actually be checked given that the losing CP isn't consulted and Plusnet aren't the Range Holder?

[#15]

@Peter-J  It is unbelievable that this fiasco is still going on. The response from Magrathea is so wrong both they and A&A know the number cannot be reinstated so it's a mystery why A&A have asked you do do this. Firstly I would ask A&A to tell Magrathea that they are wrong and that they should just re-submit the port request, which it seems they haven't even tried yet

If you don't get anywhere with that @Lawrencium103's suggestion of contacting RevK is definitely worth trying.