Google Voice calls display wrong caller ID to callee
Doc_Glenn:
A friend of mine has been using GV (Google Voice) on Obi 202 for a number of years (so have I, but she's the one with this problem). In the past week or two, all her callees have noticed a very wrong phone number. She is in the US, area code 831. The number that is displayed is 164-283-xxxx (I don't want to post the last 4 digits).
I tried calling this number with my own GV and Google told me it would cost 10 cents per minute. After about 30 seconds of silence I finally heard a rapid ring-like tone. No one ever answered.
What has happened? I can't begin to imagine how to debug this. Has she been hacked or is this just some weird bug? Is this funny number generated by GV or by Obi 202?
I wish I could manage it for her, but we setup her Obi using the convenient Google login option and right now no -in-home tech support visits!
SteveInWA:
I strongly suspect that the number being displayed is part of a longer string, such that the "1" digit that appears to be part of the area code is actually the country code, followed by a valid phone number. This obviously shouldn't be happening.
Perform a simple test to isolate the source of the problem: instead of using the OBi-attached phone to make calls, open Firefox or Google Chrome Browser on a laptop/desktop computer, and make the call directly on the computer (Google Voice uses VoIP to make calls). Find out what the called party sees.
https://voice.google.com/u/0/calls
Then, make the same call from the OBi, and compare the digits. Is part of the digit string from the OBi call the same as the browser call? If the browser call correctly displays the number, then there's a configuration error on the OBi.
Is this person's OBiTALK device installed in the USA?
Doc_Glenn:
Yes, device is installed in the US.
I had her call from GV on computer and the caller ID is correct, so the problem is with Obi. It has been rebooted and that did not fix it.
The number displayed is evidently not country code 164, rather it is 64, New Zealand, and GV charges 10 cents per minute to NZ mobile phones - so that is a match to what I found.
Now I just have to dig into Obi settings and figure this out. I wish I could find a way to remote manage - will probably have to reset and not use the convenient GV config shortcut.
Lavarock7:
My off the wall guess is that it is a number in the 643 area code (Kansas) used by Google when the caller-id is not correct. The 1 is the US long distance code and the number is truncated. My reason for suggesting this is I remember something about generic numbers being used by Google Voice if you didn't have a phone number in the account. They have used (760) 705-8888 in the past, is it possible this is yet another number they use?
SteveInWA:
Quote from: Doc_Glenn on April 26, 2020, 01:03:56 pm
Yes, device is installed in the US.
I had her call from GV on computer and the caller ID is correct, so the problem is with Obi. It has been rebooted and that did not fix it.
The number displayed is evidently not country code 164, rather it is 64, New Zealand, and GV charges 10 cents per minute to NZ mobile phones - so that is a match to what I found.
Now I just have to dig into Obi settings and figure this out. I wish I could find a way to remote manage - will probably have to reset and not use the convenient GV config shortcut.
This shouldn't happen, unless you customized digit maps or made some other user error.
I'd suggest biting the bullet and starting over. Go to the OBiTALK dashboard (http://www.obitalk.com/obinet/pg/obhdev) and completely delete the OBi device off of the dashboard. Wait several minutes until the device stops flashing the power LED. Pick up the attached phone and key in ***8 then 1 to restore factory defaults. Wait until that finishes. Re-add the device to the dashboard, via the **5 xxxx procedure, then set up Google Voice again. When authorizing the SP to Google, make sure that the Gmail address it tells you it is going to authorize is the correct Gmail account that holds your Google Voice phone number.
Make a test call. Did that fix it?
Navigation
[0] Message Index
[#] Next page