Local calls showing up as international.

Hold the line, mate. The only thing carriers relay for CLID (Calling Line Identification) is simply a string of 10 numerals. The CLID doesn't include the +1 for calls within the U.S. and Canada and never includes a + symbol in any case. The + symbol is pro forma, so to speak, only. If it shows up, it's from the caller id. display device which, with the iPhone, is simply the Phone app. The carrier settings on the iPhone could certainly play into that but the + symbol is simply not coming in via CLID. Caller id. display devices built into phones, including that of the Phone app on the iPhone, format the CLID so you are able to successfully call numbers back from your incoming call log! I'm not saying a CLID couldn't be malformed by a carrier so as to cause the caller id. display device to insert a + symbol. Theoretically possible.

I've been looking into this and, to make a long story short, I do believe you either have a code fault in your carrier settings or else a code fault or even a transient bug fault within Dial Assist. By design, Dial Assist should only affect the CLID display when you're traveling so to speak but it's the only thing I can think of could cause the false + symbol. Therefore simply disable Dial Assist in Phone settings and find out. If that's it, leave it off until the next time you do go traveling outside of your area code or internationally by which time maybe the fault will have been fixed via carrier settings and/or iOS updates.

I would hope the callers and their VoIP providers would just as interested as you in getting it fixed. Tell them to tell their network admins to tell their VoIP providers to configure their origination CLID to include country code 1. ✅

In the meantime, I would also add each malformed # to the applicable contact in Contacts and enable Dial Assist. That might help and I would be interested to know if it does. That should cause the correct contact to be presented upon call reception. Then, upon callback with Dial Assist enabled, it would be cool if it automatically chose the correctly formatted # instead of the malformed one, based on your location and I'd be interested to know if it does!

Whether you're roaming or not is irrelevant. Every carrier as the end carrier has at least three ways to relay the CLID to the end subscriber when the original phone has the exit code added sans country code. In case you don't realize it, only the origination service provider can fix the root cause.

I need to correct myself by pointing out that the original # having the exit code added without the country code unfortunately technically doesn't result in an E.164 non-conformant # which is arguably a part of the problem. It's erroneous but still conformant which is absolutely not much of a silver lining.

It's not clear to me that you gathered my meaning. I assumed you had each of these callers in your contacts with their right phone numbers. If not, make it so. Then add each erroneous number to the contact card that also has the contact's right number. Then confusion gone on incoming. Then I was curious, with Dial Assist enabled, if you tapped on the recent call in the call log, which is now going to appear as the contact not just the erroneous phone #, would Dial Assist go with the right # instead of the recent erroneous #. I suppose not but it could.

Whether you're roaming or not is irrelevant. Every carrier as the end carrier has at least three ways to handle relaying the CLID to the subscriber when the exit code has been inserted upstream without a country code. Ultimately, only the originating carrier can fix the root cause.

I need to correct myself by pointing out that the CLID is coming in erroneously but, unfortunately the net result is nevertheless E.164 conformant albeit erroneous which is far from a silver lining.

It's not clear to me that you gathered my meaning. I was assuming you already had these callers in you contacts with their right #. If not, make it so. Then add each erroneous # to the applicable contact in addition to their right #. Now confusion on incoming gone. Then enable Dial Assist. Nothing to lose. Then after one of these erroneously formatted # calls comes in, it'll appear as the contact in the call log instead of just the erroneously formatted #. Tap on it to call it back and see if Dial Assist uses the right # instead of the erroneously formatted # despite the fact that was most recent. I doubt it but it might.

Also, as off of the wall as it may be, I'd be curious to know of any other common denominators between the two subject phone numbers e.g.

• same carrier (possible at least with non-fixed VoIP)
• recently ported from one carrier or service type to another
• PBX based service
• VoIP service (some of the big time operators e.g. AT&T do offer VoIP as well as traditional twisted-pair POTS)
• non-fixed VoIP
• numbers you've never called back
• numbers not added to your contacts
• numbers not correctly formatted in your contacts
• numbers associated with contacts with Find Friends location sharing enabled
• anything else relevant you can think of

Caller ID transport is a carrier function. Period.

Any phone simply displays what it was told by the carrier. There is no interpretation done at the device level.

First of all, a phone call from a phone number based in a different rate center than your phone number, regardless of whether it's the same area code or even regional vicinity, is not a local call. I have no idea what area code or exchange rate center your phone number is based upon, but calls from Ottawa and New York can't both be local, mate. They're not even intra-national.

It's theoretically possible for someone to live in the 613 area code and have a non-fixed VoIP phone number from Australia which actually should have the +61 code prefix and someone to live in New York and have a non-fixed VoIP number from the Netherlands that actually would come in +31 prefixed. I know I'm probably overlooking something here but no matter for it's only theoretical and I believe you would know.

More likely, then, is that you're running some kind of 2nd (carrier) or 3rd party caller id. app all enabled up in Phone settings and it's a little out of whack and maybe you can just open it and let it update its database.

My compliments to you for bring this up. It would be good to keep this going until you or somebody else or I gets this figured out.

Just curious if all of the exchanges within the 613 area code that this happens to you with are any of 200, 201, 264, 267, 300, 326, 390, 464, 466, 772, 812. I've got a crazy angle on this.

Thanks for the heads up. So the problem with the Ottawa # is on your iPhone. The problem with the first New York # is on their end. What about the second New York #? Is the problem just on your iPhone or on their end or do you know?

Trying that wouldn't be worth my while but if you feel it is worth yours, go on, then, and if that happens I would be interested to know!

For the record, I wasn't suggesting that adding an erroneously formatted # to contacts would henceforth correct the #. Just that adding such to the applicable contact along with the correct # would help in terms of contact acknowledgement and callback.