March 20, 2018, 08:03:21 pm *
Welcome, Guest. Please login or register.
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
Author Topic: Any Way To Thwart Neighbor Spoofing?  (Read 941 times)
Jr. Member
Posts: 60

« on: February 21, 2018, 03:34:20 pm »

I'm wondering if anyone has come up with a good way to stop unwanted "neighbor spoofing" calls. You know these are the calls that look like they are coming from your neighbor, 1-XXX-YYY-ZZZZ where the 1-XXX-YYY part of the incoming call is the same as your own number, only the ZZZZ is different.

I am using Google Voice forwarded to CallCentric (for CNAM and e911). Google Voice doesn't have any means for setting up call filtering or rules based on number patterns. I tried setting up a Call Treatment in CallCentric to route incoming calls to their "Telemarketer Block" function. With this setup, the phone attached to the Obi never rings, the caller hears ring back, and the call eventually gets picked up by Google Voicemail.

CallCentric never picks up the call in this configuration, and therefore can't apply the Call Treatment. This isn't the end of the world for us since 99% of the phone calls that we get with the same 1-XXX-YYY as our number are spam. So if we were to receive a legitimate call, we would eventually get the voicemail message. The downside is that we would never get the live call this way.

What I wanted to happen was for the call to get picked up by CallCentric and apply the Telemarketer Block function. Then if it was a real person, they would have to select the defined code and it would ring through to the Obi.

Is there an Obi approach to this problem using digit maps or call routes? Has anyone come up with another solution that doesn't involve a separate third party, e.g. RoboKiller or Nomorobo?
Hero Member
Posts: 991

« Reply #1 on: February 21, 2018, 04:08:49 pm »

The key to getting effective CC call treatments when forwarding from Google Voice is to use CC's IVR function. The reason the telemarketer block doesn't work as expected is because it uses early media which GV ignores. The CC IVR does not use early media so it works well.

So make your own Telemarketer block with an IVR and then route to it in a call treatment.

For instance, my CC IVR telemarketer block looks like this under Menu Audio:
1 (one)
To leave a voicemail message

Then under "Key Pressed" I just have key 1 do a special forward to CC voicemail.
All other keys are No Action
Last Route is also a Special forward set to Busy tone/Line disconnect

Then just route to your IVR from a CC call treatment based on desired criteria. Very effective.
Jr. Member
Posts: 60

« Reply #2 on: February 21, 2018, 07:54:35 pm »

@Taoman, I took your advice with one slight adjustment. I wanted successful calls to ring my phone, to not always be routed directly to voicemail. I setup a new IVR requesting the caller dial "1" to be connected. If the caller dials "1" then I forward the call to my default CallCentric extension "100" which rings the phone connected to my Obi.

That allows me to receive live calls if the caller successfully dials the "1" to connect. If the caller doesn't dial a number, or if they dial a number other than "1", then like you I setup the Last Route to forward the call to a "Busy tone/Line disconnect", thanking them for their call of course Wink I'm assuming most robo calls won't have the ability or won't dial a "1".

Thanks for your help. I don't think I would have thought of this approach on my own. I don't know why CallCentric doesn't treat the Telemarketer Block like an IVR call. If they did, then all of this could be handled with a simple Call Treatment without the IVR. I sent them a suggestion for the change.
« Last Edit: February 22, 2018, 02:43:17 pm by chilirock » Logged
Pages: [1]
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC