GV Rejected By Service Provider 603
SteveInWA:
You are not understanding what I am trying to point out.
In your original post, you performed some good troubleshooting. You proved that you can call various other phone numbers, and the only number that returns the error is your wife's cell phone number.
That is not a Google Voice nor an OBiTALK problem. It is a problem with the number you are calling. Either you are misdialing (for example, swapping two digits), or she has blocked your calling phone number from being called by the number you got from Google Voice. You will have to work with her mobile phone and its carrier to find out how/where/what is blocking the calls.
BadSanta:
Quote from: SteveInWA on November 04, 2021, 06:27:20 pm
You are not understanding what I am trying to point out.
In your original post, you performed some good troubleshooting. You proved that you can call various other phone numbers, and the only number that returns the error is your wife's cell phone number.
That is not a Google Voice nor an OBiTALK problem. It is a problem with the number you are calling. Either you are misdialing (for example, swapping two digits), or she has blocked your calling phone number from being called by the number you got from Google Voice. You will have to work with her mobile phone and its carrier to find out how/where/what is blocking the calls.
Ok, thank you. You're right, I wasn't understanding what you were saying. It simply doesn't make any sense to me, as the beach house OBI and GV# are brand new and there's no way my wife would/could have blocked the number from her phone. I suppose maybe Verizon at a higher level blocks the number thinking it is spam and I guess the only way to tell that for sure would be to give up this number we were assigned and get a different number from Google and see if that clears up the problem.
Since I last posted I did speak to a Verizon tech who was uniformly unhelpful. I was told there was no type of call restrictions on our phones. When I explained the problem I was told I should contact Google, as it was not a problem on "our end" (meaning Verizon).
I guess ultimately like the other guy on the college campus who had the same problem in another thread I'm going to have to suck it up and just go without it ever being resolved.
Navigation
[0] Message Index
[*] Previous page