Good morning and thanks for the reply. I have tried both of these and no luck, still acts the same.
I did some more troubleshooting last night and found this out. This only started when I shifted to Consumer Cellular (from ATT). I am using Vbuzzer as a home phone (VOIP) and Consumer Cellular for cell service on 2 Iphones. When someone else calls with a landline the phone shows the number as a US number and their identity correctly. So far, only when I call one of my cells from my home does it show up as +32 1X XX YY YY format, and identifies a town in Belgium as the source of the call. So I did 2 more things. I went into contacts and built the home phone contact as +321XXXYYYY directly. Now when calling, it shows up as myself (Dave), as you might expect. No Belgium location. So the phone is seeing the string of 321XXXYYYY correctly, it just appears to be interpreting the location incorrectly, because of the plus sign. So I returned the contact back to the US number without the plus sign, and this international location shows up again.
Then I had a friend who has a landline call my cell and the number appears normally. Then, I removed that persons identity from contacts completely, and it came in normally as well. At that point the Iphone didnt know who the number string was. This person was not using Vbuzzer...it was another VOIP service (Brighthouse-Spectrum I believe) This is interesting, because it says that the problem is ONLY when I use a Vbuzzer to call a Consumer Cellular Iphone. BUT this all started when I shifted cell service from ATT to CC. Very odd. So here is a summary calling from the Landline Service to the Cell Service.
Cell Service Landline Service Location Error
ATT Vbuzzer No
CC Vbuzzer Yes
CC Spectrum No
As you might expect, both Vbuzzer and CC deny that they are responsible for this. One of the responses from CC said that the phone itself is responsible for the location display of the incoming call. This does seem to make sense. But I have made the changes you suggested and everything else I could think of, and I don't believe Apple is identifying this as a problem. Everyone points to the "other guy". I am an engineer and this reminds me of the the classic joke about how a problem occurs in a generator.....the ME and EE guys stand there and just point at each other. Funny, but not really funny.
Anyway, this is where I am. It kind of smells like a phone problem, but obviously with Iphones you can't control the OS. This is the problem with the philosophy of Apple, they actually believe they know best what we want and how things should work. In most cases they are pretty close...but when there is a problem, it takes a huge effort to get them to 1. admit the error 2. fix it. Sigh.
Any further help much appreciated!
