On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT
Started by 915855, September 08, 2021, 12:36:11 PM
Quote from: 915855 on September 08, 2021, 05:21:16 PMIf you read the reply above, I wrote that because another HERO MEMBER posted a link to how google voice works to try to contradict me, but his link stated exactly what I was saying. I guess he realized that he was wrong and deleted the post.
QuoteIf the person who is calling me is in my contacts, Google Voice will automatically transfer the call to my home phone without asking them to state their name. If the person calling is not on my contact list, then it will ask to state their name.
Quote from: 915855 on September 08, 2021, 05:41:09 PMWhere does it say in your link that google will call you even if the caller is not in your google contacts and will not state their name? I have been using the screen calls service forever, and within the past 2 month, it started ringing once when the caller does not state their name.In the past, if the caller did not state their name, the phone would not ring. Verizon and AT&T has the same feature as well, and in their service, the phone will not bother the recipient if the caller does not leave their name.
Quote from: SteveInWA on September 08, 2021, 05:49:45 PMYou're not going to get help here by ranting and whining about the people who are here to help. If you can't get past that, then go away.I know precisely how Google Voice works, and I've been supporting the service as one of Google's Product Experts, on the official Google Voice help community, for over a decade.You posted:QuoteIf the person who is calling me is in my contacts, Google Voice will automatically transfer the call to my home phone without asking them to state their name. If the person calling is not on my contact list, then it will ask to state their name.That's what I said, except that you left the crucial point: call screening cannot control ring behavior. It has nothing to do with that. It screens your inbound calls, meaning: it always rings your phone and it always asks you if you want to accept the call. The only difference between a call from a caller in your Contacts vs. a call from a caller not in your contacts is that, since Google already knows a contact's name, it won't annoy them by asking them to speak it. Instead, it uses a synth voice to read their name to you. Otherwise, all screened calls work identically.You have some other issue causing the single ring. There are two possibilities I can think of:Using a laptop or desktop computer's web browser, not a tablet or phone, sign into the correct Google account that holds your Google Voice phone number, and go to Settings: https://voice.google.com/settingsExamine the lists of devices and linked numbers. Delete all devices and numbers except for your "OBiTALK device", your mobile or landline phone number if you have one, and the "Web" device. Any old, orphaned, dead or otherwise not in use numbers will cause ring problems.If any active linked phone numbers are forwarded to yet another number, this will also cause problems. All linked numbers must use conditional call forwarding to send busy or unanswered calls back to your Google Voice phone number. Otherwise, the linked number will grab the Google Voice calls and cancel ringing, and possibly send the caller straight to that number's carrier's own voicemail.You may have set up the old, "Legacy" Groups feature, to apply special call routing, ringing and voicemail to certain numbers.For example, if you have configured the "Anonymous callers" group to not ring any of your linked devices or numbers, then that's what will happen when the calling party is blocking their caller ID. Again, this has nothing to do with callers who do have an unblocked phone number which is simply not in your contacts.It is up to you to understand how Google Voice works, and to configure it properly. You should also be testing it by unplugging your OBiTALK device(s), and sign into Google Voice on a web browser, and make and receive calls using the browser. This will eliminate the OBiTALK device as a possible culprit.