Not receiving texts from abroad

willmow
Established Contributor
Established Contributor

I am experiencing an odd issue that is seriously hampering my ability to verify/confirm things like identity, and thus run my daily life:

Issue: certain transactions conducted here in the UK via mobile apps require me to confirm my identity (or email/phone), e.g. banks, digital signature providers, mountain rescue organisations... To do this, the organisation/company sends an SMS text message with a code, which I must enter in the app. This works faultlessly if the organisation is in the UK (using a UK app), but I receive no such texts if the organisation is in (say) Switzerland (and I'm using their app). Something stops these texts from getting through. It happens time and again and with a variety of apps/organisations. 

Can anyone shed any light on this frustrating behaviour? It feels like it's security related. It's not my phone, as it happens on two different ones.

41 REPLIES 41
willmow
Established Contributor
Established Contributor

I don't know why, but I started another similar thread. Here it is with my latest post describing a successful workaround:
https://community.ee.co.uk/t5/Mobile-Services/Foreign-banking-texts-not-getting-through-this-may-be-...

st0rmcloud
Investigator
Investigator

Had the same issue with authenticating a security app with the Portuguese Government (basically 2FA for setup).

Previously had no issues, but every so often, iOS apps decided to "log out" and you have to set up again. I tried this week and you add your mobile number and get PIN code via SMS. Well, I was not getting an SMS back, no matter what I did. 

Bought an international 7 day eSIM online attached to an SMS plan (in case I needed to send SMS myself), and it auto detected my network to be EE. Tried to register, and still no confirmation code.

Forced that eSIM plan to use 3 Network instead, and boom. Instantly worked and I was able to do what I needed. Trouble is, that eSIM will only last 7 Days and I need the registration to last. 

Moral of the story, EE are blocking certain SMS, so I either have a second line specifically for the annual occasion I need to authenticate for personal reasons, or move from EE to 3 Network/Vodafone (that worked for my wife). Ridiculous really. 

Just more money to spend and stress that is not needed.

Hope you've sorted your issue out though

willmow
Established Contributor
Established Contributor

Yes, the workaround involving an eSIM is rock solid and works for me. It necessitated my registering the (foreign) eSIM number with the (foreign) bank, but after that - no problems.

I'm not sure why you don't want a permamnent second (eSIM) line. It solves your problem, and if you get a PAYG/pre-pay eSIM, it costs you nothing as you won't be using it to call or message out. 👍

Glad it works for you - huge relief no doubt.

A second eSIM is not a solution, as that's another monthly cost just so I can receive text message that EE is blocking. Also, it's only a matter of time before other providers follow suit so I'll be back at square one again. 

I found this article below and doing more digging, the text messages that I need has the sender as "info" so it will always be blocked, until the Portuguese Government change it on their side - and let's me realistic, that's certainly not going to happen either.

Blocking SMS's based on sender name is bizarre and there must be other ways to qualify the source to allow false positives through. If firewalls behaved this way when applying whitelists without exceptions, we would all be screwed.

https://thesmsworks.co.uk/blog/bt-ee-new-regulations/ 

willmow
Established Contributor
Established Contributor

Did you not see the bit about getting a PAYG eSIM? That's what I have (supplied by a Swiss network). It costs me nothing zilch nada and is the perfect solution. It would only cost me if I texted or called out on that line - which of course I don't.

well it can't be "free" - PAYG contracts you still have to top-up at some point or/and show signs of life every set period of time to ensure connectivity remains. I get it's not breaking the bank, but you get my point, we pay enough for a monthly SIM as a it is.

Also, who do you peer that Swiss SIM with over in the UK? At some point, all providers will follow suit in the UK at least - what will you do then, should the problem persist?

willmow
Established Contributor
Established Contributor

I get your point, but I'll cross that bridge as and when. Besides, there's no better solution out there, and hell will freeze over before foreign banks, governments and so forth change their coding to suit UK networks that unilaterally demand the world adapt to them!

As to your question regarding the UK network - it's EE of course (this is the EE community!) - the source of all the SMS problems, and the reason why I tracked down the eSIM solution.

Agree - hell will need to freeze over a few times.

So you peer your Swiss PAYG eSIM with EE and it works? Interesting.... my Austria eSIM will not work with EE here, but does with other networks.

I'm surprised yours works with EE as it shouldn't according to that list (unless your issue does not relate to one of the blocked words).


@st0rmcloud wrote:

Blocking SMS's based on sender name is bizarre and there must be other ways to qualify the source to allow false positives through


Legitimate senders who find themselves blocked, can easily be advised of the requirements to be whitelisted.

If those senders choose not to act on that advice, the issue is with them.

Actually, It's more complicated than that.

I ordered another international eSIM that does not expire within 12 months, and when I use it for the purposes intended peering with EE in the UK as a test, I get the one time SMS from "+351" which is legitimate. However, using my UK EE number, it doesn't present as "+351" but instead "info".

Therefore, for all intents and purposes, there is nothing wrong with the source number, but instead how it's accepted on EE network.

The responsibility here is clearly not on the owner but the blocker in the middle. EE needs to resolve this (especially as they can add the source number to a whitelist, but won't).

Anyway, hope my my posts help someone out when they get issues.