Contact phone numbers stored with (0)

Question

Level 1

15 points

Contact phone numbers stored with (0)

I have many domestic Australian numbers store as international numbers as I (used to travel a lot) - e.g +61 (0) 8 9555 1234. Recently I found that when I call these numbers from within Australia i get a recorded message from my telco saying "The number you have called is not available from this service". I found that I could manually call these numbers by manually dialling (e.g.) +61 8 9555 1234. However, if i included the leading 0 for the area code, which appears on my dial pad as +61 (0) 8 9555 1234, I also got the recorded message about the number being unavailable from this service.

I suggest that one of the more recent IOS updates may have introduced a bug in the dialling protocol (e.g. maybe it tries to send the brackets as well as the numbers, or maybe it no longer likes the unnecessary "0" in the area code) or introduced a bug. This is a very recent issue so maybe IOS 15.2?

I have worked around my problem by taking out the unnecessary 0 in the area code, but I've had these numbers stored this way for many years and the problem has only recently started.

iPhone 13

Posted on Jan 13, 2022 7:14 PM

Reply

Answer 1

Top-ranking reply

MRock86 Author

Level 1

15 points

Feb 20, 2022 7:34 PM in response to deejerydoo

It’s hasn’t been resolved even witun15.3.1

I’m with Telstra, but judging by other responses that is irrelevant.

As I said, the workaround is to remove the “redundant” 0. But as others have pointed out the brackets are generally included when you receive international calls. So if you were to save such a number to a contact the brackets are there.

My guess is that the dialling mechanism has been change and it’s now just literally dialling the stored character sequence, including the bracket characters, which of course the telcos can recognise.

in fact you can test it by trying to call a domestic landline number with the complete area code including the 0s with the +international code in front. You will see that the phone recognises the leading 0s and puts brackets around it. And you he telco will most likely reject the call as number not known or similar.

Seems like such a rookie error for Apple to have made.

Reply

Answer 2

Jan 23, 2022 7:44 PM in response to MRock86

I have the same issue which started happening immediately after updating to iOS 15.2.1. Like you I also travel regularly overseas, when COVID doesn't stop me. I have several thousand contacts stored in the same way that now don't work. I tried contacting Apple Support, but they keep telling me its a carrier issue, which it is not. As Apple probably won't pick this up, I am manually editing the (0) out each time I try to call someone and it fails. This is a pain in the butt, but the only way that appears to be open to us to solve the issue.

Reply

Answer 3

Jan 17, 2022 12:44 PM in response to R3M1X972

Hi, I can confirm the same issue in UK however I removed the +44 which works for me. This removes the brackets and puts the zero back on the front of the now working number. This started for me after 15.2

Reply

Answer 4

ceewils

Level 1

8 points

Feb 10, 2022 4:59 PM in response to MRock86

Update 15.3 fixed it for me

Reply

Answer 5

Feb 10, 2022 5:04 PM in response to MRock86

I had this problem too. It appears this was a bug in iOS somewhere between 15.1 and 15.3 where it appears to now be fixed.

My previous post on this was censored by Apple as "speculative".

Reply

Answer 6

R3M1X972

Level 1

8 points

Jan 17, 2022 8:19 AM in response to MRock86

Hi there

Having the very same issue since updating iPhone 13Pro to 15.2.1 : all numbers stored as +33(0)6.... won't work, the French operator telling me no such number exists nor is referenced. I've contacted AppleSupport and tried a few things such as reseting network settings, but only removing the (0) seems to do the trick. Can't figure why it worked like a charm before...(?) apparently downgrading to previous iOS ain't no option so I'm awaiting a solution. or quick Patch from Apple. Will keep you guys posted if this can be sorted without editing all my 500+ contact numbers...

Reply

Answer 7

Jan 14, 2022 1:14 AM in response to MRock86

There is no bug as such

(0) after an international prefix is redundant.

Reply

Answer 8

Jan 22, 2022 1:42 PM in response to R3M1X972

Yes both my wife an I had the same issue in the UK - most of our UK numbers have been stored as +44 (0) for years because Apple originally supplied the "(0)" formatting automatically . We have 100s of contacts to manually update unless Apple fix this bug...

Reply

Answer 9

MRock86 Author

Level 1

15 points

Jan 24, 2022 5:56 PM in response to ceewils

Personally I wouldn’t hold my breath. I got onto Apples support chat and they initially recommended to update to IOS 15.2.1 and were unaware of the issue. Updating the IOS didn’t fix the problem and Support just told me to repot the bug on their feedback form - which I’ve done.

The workaround is to remove the redundant (0) from your contacts and omit it if manually dialling.

My guess is that they change the phone app and now it dials whatever it sees including the brackets which sends an illegal character/number code to the telco, but that’s an empirical guess.

Reply

Answer 10

MRock86 Author

Level 1

15 points

Feb 10, 2022 5:16 PM in response to deejerydoo

It’s certainly not speculative and no it’s not fixed in 15.3. I don’t even think Apple is considering the issue as I’ve had no response on my bug report at all.

Reply

Answer 11

R3M1X972

Level 1

8 points

Jan 17, 2022 10:01 PM in response to TheUtaker

Indeed but modifying each contact is a pain in the butt : I can't just remove the +33 since my contacts are international and a lot of area codes are involved (+44 +353 +41....) so I have to manually remove the (0) ... which by the way iOS writes by itself right after me imputing a new area code... I could have understood such a snafu with Sams*ng or other manufacturers but quite surprised by Apple on this one : indee the only solution offered after 1h on the phone with support was to manually modify each and every one of my contact numbers :(

Reply

Answer 12

MRock86 Author

Level 1

15 points

Feb 2, 2022 5:27 PM in response to PauLBu20

And they haven’t fixed the problem in 15.3.

maybe Apple think they’re more important than the telcos of the world which always include the (0). And, as you say, adding a

new contact for a calling international number will include the (9) by default, which is where I was tripped up.

let’s hope they fix this in the next release. I have reported the bug.

Reply

Answer 13

MRock86 Author

Level 1

15 points

Jan 14, 2022 2:09 AM in response to SravanKrA

I would suggest that your comment is quite incorrect.

Yes, Leading 0s in the area code of international numbers, but

These numbers have been stored and used successfully for years. It is only recently that they stopped working.

It is not correct to say that it is not a bug just because the telcos ignore the leading 0s. This is highlighted by the fact that the numbers hav previously worked and that when entering such an international number, the iPhone inserts the brackets around the redundant 0. Hence it IS a bug. This is a well established practice for decades and iPhones have worked until very recently.

Reply

Answer 14

PauLBu20

Level 1

8 points

Feb 2, 2022 5:14 PM in response to MRock86

Yep, exactly what everyone else says. I'd add that often the 61 prefix often appeared on your phone for messages. I always had my contacts with the international prefixes because

1. I like to be able to use my phone if overseas, and

2. When creating a contact with a new number from a received call or message, it automatically was including the 61 most time.

Reply

Answer 15

MRock86 Author

Level 1

15 points

Feb 11, 2022 11:05 PM in response to ceewils

Well that interesting. 15.3 didn’t fix it for me and I just updated to 15.3.1 and still get an error from my telco if I dial a number in the format +61 (0)8 5551234. The brackets are inserted as I enter the number

Reply

Contact phone numbers stored with (0)

Similar questions