RCS texting number incorrect after port

[armstra101]

Hi,

I have recently moved back to EE and ported my number, which didn't go smoothly but is finally sorted. I can make and receive calls and SMS on my ported number.

The problem is RCS messaging. When I send one they appear to come from a different number, presumably the one that EE had on the SIM card.

I've checked the number in RCS settings and it's using the number provided to me. If I turn RCS off and back on it attempts to connect with the ported (correct) number but after a second it switches to the incorrect number and connects.

How can I fix this? I have a Galaxy S22.

Cheers

Andrew

[everybodyhatesc]

Yes, I did once but the guide couldn't help me. I will try again now.

[armstra101]

It should sort itself out after a few weeks, it did in my case. Just turn off RCS and use SMS until it resolves itself. Not ideal I know but the path of least resistance.

[everybodyhatesc]

Try this:

Go to the device's stock messaging app.

Select the circled initial in top RH corner.

Select Messages Settings < RCS Chats.

Check RCS status. Disable RCS Chats and deselect auto verification of your mobile number.

Clear cache and data of the Carrier Services app.

Go back to Messages< Messages Settings and select Advanced.

Under sub-heading Phone number, your status will either be Unknown or it will display the number of your new SIM card.

Replace the number with your ported number and select OK.

Switch off and restart your phone*

You may wish to call Tech support on 150 and they will refresh your SIM settings while you speak to them. I tried this yesterday and was advised to wait 24 hours before switching RCS back on.

Good luck. I hope it works out for you!

Regards 

Chris

[everybodyhatesc]

Thanks for the assurances. I have just noticed I've replied to an earlier post of yours 😏🍋

[everybodyhatesc]

Did this work for you (exact same scenario; nearly a month without RCS since porting number across from BT)?

[XHGG]

Hi all - the problem actually lies with Google rather than EE. I've had the same problem with pretty much every network I've been on (which is virtually all of them!)

Unfortunately, the Google messages app has problems when you port your number, usually when you put in your new SIM before the porting process is complete, as it "remembers" the temporary number associated with your new SIM. The only solution I've had that consistently worked is to switch off RCS for a day or two and it seems to sort itself out eventually. SMS works fine in any event after the port process is complete.  It's a real pain and you'd think Google would have sorted this out by now. 

[Robmcmeechan]

This didn't work for me unfortunately 😔 

[everybodyhatesc]

The only way in which I achieved a successful resolution was by speaking to a clued-up technical support advisor who said she was familiar with my problem and would send out a brand new SIM card with my preferred number already in place. It was a few months ago but I do recall that on receiving the new SIM card one of the steps I had to follow was going to this link:

https://ee.co.uk/simswap where there is a dedicated portal for situations such as these. Quite why it took just one person from at least a dozen other 'guides' or tech support advisors to solve the problem I don't know. This is by far the simplest option. You shouldn't be charged for the new SIM card if you mention the problem you're having and that you want to SIM swap. Best Of luck with it all. 

[XHGG]

Ah yes, when you get a replacement SIM you have to activate it first these days. There was apparently lots of bank fraud related to people fraudulently ordering replacement SIMs and using them - "SIM swap fraud".

Glad you got the problem sorted in the end. It's a real pain.

[everybodyhatesc]

Yes, it was a real pain not to be able to use RCS using my ported number for several weeks. A bit surprised at lack of knowledge from EE's point of view in terms of SIM swap procedure etc, but it's done now.

There's not a huge amount of info online either as to how to overcome the problem - which is surprising, given that RCS has been adopted by most networks and manufacturers for the best part of 2 years (unless you're a recent adoptee, such as Apple).