Ported Number not working with iMessage

Post by Wilf
Hi. I recently ported my (UK) mobile number to a new provider. Since
then, although my iCloud details on my iPhone tell me that the number is
registered for iMessage and FaceTime (it wasn't initially and for a
couple of days), it cannot be used for those apps - a revolving cogwheel
appears on the left of the number in iMessage and FaceTime, instead of a
tick.
I can of course use iMessage and FaceTime with various registered email
addresses, but I want to use my phone number for these facilities, as
always before. I've tried all the recommended standard remedies -
switch off iMessage/FaceTime, restart, reset all the network settings,
etc. etc., to no avail. If anyone here can help with this I'd be very
grateful.

I've had this recently - caused by buying an eSIM for travelling - and the
solution has been to log out of your Apple ID and log back in. Faff factor
is that all bank cards are removed from your wallet when you log out.

Wilf

2024-09-23 22:03:02 UTC

I will give that a go and put up with the faff factor!... thank you

--
Wilf

Wilf

2024-09-23 22:31:26 UTC

Post by Wilf

I will give that a go and put up with the faff factor!... thank you

It worked! Thank you so much. I did this whole thing before (;logging
out of iCloud, etc.) but at that time, under iCloud, my phone number was
labelled as "not registered for iMessage or FaceTime" and logging out of
iCloud, etc., did not help. Three days later, now, and that message had
disappeared from my phone number, yet it still couldn't be used for
iMessage and FaceTime. But following your advice and again logging out
of iCloud and back in again, and it has finally worked!!! Why it all
took so long to get my ported number registered with Apple, I just don't
know, but it has taken up hours of my time! Thank you again. And
I've restored all my cards to Wallet.

--
Wilf

Chris

2024-09-24 18:59:38 UTC

Post by Wilf

I will give that a go and put up with the faff factor!... thank you

You're welcome.

It's frustrating that such complicated systems sometimes only respond to
such rudimentary solutions.

Jörg Lorenz

2024-09-24 20:22:59 UTC

Post by Wilf
It worked! Thank you so much. I did this whole thing before (;logging
out of iCloud, etc.) but at that time, under iCloud, my phone number was
labelled as "not registered for iMessage or FaceTime" and logging out of
iCloud, etc., did not help. Three days later, now, and that message had
disappeared from my phone number, yet it still couldn't be used for
iMessage and FaceTime. But following your advice and again logging out
of iCloud and back in again, and it has finally worked!!! Why it all
took so long to get my ported number registered with Apple, I just don't
know, but it has taken up hours of my time! Thank you again. And
I've restored all my cards to Wallet.

You're welcome.
It's frustrating that such complicated systems sometimes only respond to
such rudimentary solutions.

In this particular case it is logic. For various reasons.

--
"Mille viae ducunt hominem per saecula Romam." (Alanus ab Insulis 1120-1202)

Alan Browne

2024-09-24 20:27:53 UTC

Post by Chris
It's frustrating that such complicated systems sometimes only respond to
such rudimentary solutions.

It's because they're complex that they can get into a state that
requires a heavier nudge to actually fix. May have benefits in
preventing other glitches down the pike too.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

Wilf

2024-09-24 21:33:28 UTC

Post by Chris
It's frustrating that such complicated systems sometimes only respond to
such rudimentary solutions.

It's because they're complex that they can get into a state that
requires a heavier nudge to actually fix. May have benefits in
preventing other glitches down the pike too.

Yes indeed. For over three days, in the AppleID sign-in and security
settings on my iPhone, it said that the number was "Unavailable for
iMessage and FaceTime". Clicking on the information "I" revealed "You
must have a SIM associated with an Apple device for <my number> to be
used for iMessage and FaceTime". Over in appleid.apple.com it said the
same thing about my number even though it accepted it as a trusted number.

After 3 days, this Unavailable status disappeared for my mobile number
and it was only then that logging out of iCloud and back in again did
the trick. But I don't know why it took so long for my number to become
registered by Apple - all the information available suggests that this
process should not take very long at all.

--
Wilf

Alan Browne

2024-09-25 16:57:03 UTC

Post by Chris
It's frustrating that such complicated systems sometimes only respond to
such rudimentary solutions.

It's because they're complex that they can get into a state that
requires a heavier nudge to actually fix. May have benefits in
preventing other glitches down the pike too.

Yes indeed. For over three days, in the AppleID sign-in and security
settings on my iPhone, it said that the number was "Unavailable for
iMessage and FaceTime". Clicking on the information "I" revealed "You
must have a SIM associated with an Apple device for <my number> to be
used for iMessage and FaceTime". Over in appleid.apple.com it said the
same thing about my number even though it accepted it as a trusted number.
After 3 days, this Unavailable status disappeared for my mobile number
and it was only then that logging out of iCloud and back in again did
the trick. But I don't know why it took so long for my number to become
registered by Apple - all the information available suggests that this
process should not take very long at all.

I've never had issues with numbers 'registering' - but have had - from
time to time - to log out of AppleID on 1 or more devices to right
things. Annoying when it happens but it's not very often - and likely
been over a year since I had to do so.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

Wilf

2024-09-26 08:51:19 UTC

Post by Wilf