I don’t understand how the X_SkipCallScreening with GV is supposed to work
SteveInWA:
Just disable it in Google Voice settings.
Your proposed scenario makes no sense. The CALLED party (you) hears the "press one" prompt, not the CALLING party (potential robocaller). The Google Voice call screening feature is not a robocall blocking solution, nor does the current implementation of Google Voice work as it did in 2012.
If you want to limit robocalls, enable the "Filter Spam" setting in Google Voice settings.
Shinelikethunder:
No. I've been very polite, and you refuse to even attempt to understand what I'm trying to do. Is anyone else reading this?
Shinelikethunder:
Quote from: SteveInWA on February 03, 2020, 03:34:48 pm
Your proposed scenario makes no sense. The CALLED party (you) hears the "press one" prompt, not the CALLING party (potential robocaller). The Google Voice call screening feature is not a robocall blocking solution, nor does the current implementation of Google Voice work as it did in 2012.
If you want to limit robocalls, enable the "Filter Spam" setting in Google Voice settings.
Sorry, I wrote my previous response before you added this part; all I saw was "just disable it."
I have "filter spam" on, and always have. It's as useful as a screen door on a submarine. Call screening does seem to help stop spam callers, because they're asked to state their name when call screening is on, right? At least that's what happens when I call from a number that's not in my GV phone book. My OBi call history shows many calls from unknown callers that appear to hang up after 2 seconds. Isn't that because they've been asked to give their name and declined? When I Google those numbers, I frequently see Nomorobo spam reports for them. Exactly why does my proposed scenario make no sense?
SteveInWA:
OK, let's start the conversation over.
First: this thread was from eight years ago. Google Voice has undergone a complete refresh since then, and many features have changed. Google Voice now directly supports SIP VoIP calling, without the old XMPP/Google Chat kludge. That OBi X_SkipCallScreening setting is now non-functional and irrelevant.
Google Voice call screening has been completely replaced, and it now has a different behavior. Here is how call screening now works, assuming you have turned it on in Google Voice settings:
All calls, from all callers, will be screened. "Screened" is defined as: when you answer the call, Google Voice will always announce "Call from..." and then ask you, the Google Voice user and called party to decide -- press 1 to accept the call and talk to the caller, or press 2 to send the caller to your Google Voice voicemail.If the calling phone number is not in your Google Contacts, then that caller will be asked to state their name before the call rings on your end. Google Voice will play back whatever the caller said, after "Call from..." It will not save their name, and they will be asked to speak their name on every subsequent call. Even if they say nothing, your phone will still ring, and it will simply have no recorded speech to play back.If the calling phone number is in your Google Contacts, then the caller will not be asked to speak their name, however, their call will still be screened. Instead, Google Voice will use that contact's information with text-to-speech, to say the name you entered in their contact.
Over the past couple of years, the majority of robocalling has been using "neighbor spoofing", whereby the robocall software spoofs the caller ID of some random number that has the same area code and prefix as your number. This is a "social engineering" trick to make you think the call is indeed from one of your neighbors or local businesses, doctor's office, etc. Until the new "STIR/SHAKEN" based caller ID authentication system is more widely supported, there is no defense against this, other than to simply not answer calls from numbers you do not recognize, or to build a cumbersome white-list solution.
Note that you can "fork" inbound calls to Nomorobo, to add its blocking database, and that's been discussed in other threads.
Shinelikethunder:
Quote from: SteveInWA on February 03, 2020, 05:36:56 pm
That OBi X_SkipCallScreening setting is now non-functional and irrelevant.
Yes, that matches what I've observed.
Quote from: SteveInWA on February 03, 2020, 05:36:56 pm
Google Voice call screening has been completely replaced, and it now has a different behavior. Here is how call screening now works, assuming you have turned it on in Google Voice settings:
All calls, from all callers, will be screened. "Screened" is defined as: when you answer the call, Google Voice will always announce "Call from..." and then ask you, the Google Voice user and called party to decide -- press 1 to accept the call and talk to the caller, or press 2 to send the caller to your Google Voice voicemail.If the calling phone number is not in your Google Contacts, then that caller will be asked to state their name before the call rings on your end. Google Voice will play back whatever the caller said, after "Call from..." It will not save their name, and they will be asked to speak their name on every subsequent call. Even if they say nothing, your phone will still ring, and it will simply have no recorded speech to play back.If the calling phone number is in your Google Contacts, then the caller will not be asked to speak their name, however, their call will still be screened. Instead, Google Voice will use that contact's information with text-to-speech, to say the name you entered in their contact.
Yes, I believe that I understand all of that. I have no complaint with the way GV call screening works. I just was under the misimpression that X_SkipCallScreening sent a "1" when I answered and that it should eliminate the need for me to do so myself. If nobody has a workaround that does what I want, maybe I need to make an OBi feature request. I'm just looking for a way to automatically halt the screening announcement and directly connect to the caller.
Quote from: SteveInWA on February 03, 2020, 05:36:56 pm
Over the past couple of years, the majority of robocalling has been using "neighbor spoofing", whereby the robocall software spoofs the caller ID of some random number that has the same area code and prefix as your number. This is a "social engineering" trick to make you think the call is indeed from one of your neighbors or local businesses, doctor's office, etc. Until the new "STIR/SHAKEN" based caller ID authentication system is more widely supported, there is no defense against this, other than to simply not answer calls from numbers you do not recognize, or to build a cumbersome white-list solution.
Note that you can "fork" inbound calls to Nomorobo, to add its blocking database, and that's been discussed in other threads.
Yes, I used Nomorobo for several years and know how to fork to it, but it's no longer effective. I suspect it's because spammers that use "neighborhood spoofing" change numbers as fast as I can blink.
Navigation
[0] Message Index
[#] Next page
[*] Previous page