Callcentric and Google Voice Setup Guide (with CNAM)
SteveInWA:
Quote from: Wildcatz on February 03, 2015, 05:00:47 pm
I found that this erroneous routing was being caused by call treatments on my Callcentric account. Specifically if I set a call treatment to allow the Callcentric phone to ring (blocked or unblocked number) irregardless then sure enough the call routed through fine. However if I used ANY call treatment on the Callcentric end to say go straight to voicemail, send the call to another number, perform the telemarketer block etc the call would always default route to Google Voice voicemail and never be passed to Callcentric.
Hi:
You and I went through a series of posts on this topic on the GV help forum. The bottom line, regardless of what might have worked in the past, is that the type of call treatments you are attempting to perform on the CC end, should just be performed on the GV end instead.
I can tell you that I have a GV number forwarded to a CC DID, and that the following call treatments do work:
Send certain specific inbound numbers (telemarketer/fraudster/spammer) to the no-service SIT error message (create one such treatment for each number that calls you, and you want to block in the future. If the caller isn't handled by these rules, then the default rule is processed:Send to one, or multiple extensions, and ring each for 30 seconds, then go to CC VM (this should be your only call treatment set as the default for calls made to this DID, and be sure to click the "normalize priority" button after you finish adding treatments.)
Do NOT create any treatments to try to subsequently forward the call to a different phone number, after it hits your CC DID.
The purpose of setting the "forward to CC VM after 30 seconds" is as a GV-compatible fail-safe: GV will ring a forwarded number for approximately 25 seconds, then, if no answer or busy, it will give up and take back the call to GV VM. The 30 second ring interval for CC will prevent CC VM from grabbing the calls before GV VM. However, if someone calls the CC DID directly, the unanswered call will instead go to CC VM.
Taoman:
Quote from: SteveInWA on February 03, 2015, 06:51:45 pm
Send certain specific inbound numbers (telemarketer/fraudster/spammer) to the no-service SIT error message (create one such treatment for each number that calls you, and you want to block in the future. If the caller isn't handled by these rules, then the default rule is processed:
Are you saying the caller literally hears the SIT error message or that the caller just hears a ringback tone until GV voicemail picks up? When I try this (and I've tested this dozens of times) there is no message heard (since it is early media) just the ringback tone.
And I'm not sure why you would recommend making individual call treatments "for each number that calls you, and you want to block in the future." That seems needlessly redundant. Why not make one or two call treatments and make corresponding phone book groups the call treatments act on? Then just add the "telemarketer/fraudster/spammer" contact to one of those groups.
Wildcatz:
Hi Steve
Thanks for the continued pointers, I too am trying some new things and doing some further digging as well. What was interesting is that when I have the call treatments on (simple one right now that takes inbound calls from my google voice number and should send to CC vmail) although I still get pushed to Google Voice mail instead of CC, I am seeing the call show up in the callcentric history report log, therefore a part of this call seems to be registering with Callcentric even though the call seemingly bounces or is pulled back to Google Voice voicemail. I will try the 30 second VMail config now that you mentioned and see what that gives me.
With regards to the call treatment for every call you wish to block in future I was hoping instead I could do like I do with Callcentric direct which is force the Telemarketer option on any private/anonymous calls that originate from my Google Voice number, I know I can set this up in the CC treatments but of course today it appears to be the addition of these treatments that is not letting the call make the final piece of the connect.
Quote from: SteveInWA on February 03, 2015, 06:51:45 pm
Quote from: Wildcatz on February 03, 2015, 05:00:47 pm
I found that this erroneous routing was being caused by call treatments on my Callcentric account. Specifically if I set a call treatment to allow the Callcentric phone to ring (blocked or unblocked number) irregardless then sure enough the call routed through fine. However if I used ANY call treatment on the Callcentric end to say go straight to voicemail, send the call to another number, perform the telemarketer block etc the call would always default route to Google Voice voicemail and never be passed to Callcentric.
Hi:
You and I went through a series of posts on this topic on the GV help forum. The bottom line, regardless of what might have worked in the past, is that the type of call treatments you are attempting to perform on the CC end, should just be performed on the GV end instead.
I can tell you that I have a GV number forwarded to a CC DID, and that the following call treatments do work:
Send certain specific inbound numbers (telemarketer/fraudster/spammer) to the no-service SIT error message (create one such treatment for each number that calls you, and you want to block in the future. If the caller isn't handled by these rules, then the default rule is processed:Send to one, or multiple extensions, and ring each for 30 seconds, then go to CC VM (this should be your only call treatment set as the default for calls made to this DID, and be sure to click the "normalize priority" button after you finish adding treatments.)
Do NOT create any treatments to try to subsequently forward the call to a different phone number, after it hits your CC DID.
The purpose of setting the "forward to CC VM after 30 seconds" is as a GV-compatible fail-safe: GV will ring a forwarded number for approximately 25 seconds, then, if no answer or busy, it will give up and take back the call to GV VM. The 30 second ring interval for CC will prevent CC VM from grabbing the calls before GV VM. However, if someone calls the CC DID directly, the unanswered call will instead go to CC VM.
giqcass:
Quote from: Taoman on February 03, 2015, 07:57:57 pm
And I'm not sure why you would recommend making individual call treatments "for each number that calls you, and you want to block in the future." That seems needlessly redundant. Why not make one or two call treatments and make corresponding phone book groups the call treatments act on? Then just add the "telemarketer/fraudster/spammer" contact to one of those groups.
Yes much simpler to use as few call treatment as possible to avoid confusion. In addition with CC you can even block/whitelist entire area codes if you like.
I started a thread on call treatments here. This thread wasn't really about that in the beginning.
http://www.obitalk.com/forum/index.php?topic=9406.0
SteveInWA:
Quote from: Taoman on February 03, 2015, 07:57:57 pm
Quote from: SteveInWA on February 03, 2015, 06:51:45 pm
Send certain specific inbound numbers (telemarketer/fraudster/spammer) to the no-service SIT error message (create one such treatment for each number that calls you, and you want to block in the future. If the caller isn't handled by these rules, then the default rule is processed:
Are you saying the caller literally hears the SIT error message or that the caller just hears a ringback tone until GV voicemail picks up? When I try this (and I've tested this dozens of times) there is no message heard (since it is early media) just the ringback tone.
And I'm not sure why you would recommend making individual call treatments "for each number that calls you, and you want to block in the future." That seems needlessly redundant. Why not make one or two call treatments and make corresponding phone book groups the call treatments act on? Then just add the "telemarketer/fraudster/spammer" contact to one of those groups.
Your mileage may vary. My personal use case is that I have 4 different Callcentric DIDs on my one Callcentric account. Two of the four numbers are forwarding targets for GV; the other two are just numbers not used with GV. I get my fair share of junk phone calls to one or more of those DIDs. So, when get an inbound call as I did the other day, from some clown threatening to issue a warrant for my arrest if I didn't respond to a order from a Federal magistrate, I add a call treatment to block that number. I hadn't thought of creating a phone book for those callers.
If the caller is calling the CC DID directly, they'll hear the SIT and recorded message.
If the caller is calling GV, AND GV's own global spam list doesn't happen to catch the caller, AND you haven't blocked that caller in GV, and a CC call treatment to send them to the SIT and recorded error message is enabled, then the caller will hear ringing, while GV tries to simulring other forwarding targets (e.g. Hangouts or Chat), but GV will give up on the CC number after it hears the SIT, and the CC phone number won't ring (so, like you said, the caller won't hear the SIT, but the end result will be that you won't be bothered). Since the vast majority of spam calls are made by robocalling systems, they usually hang up before leaving a message.
This is by design. Since GV is designed to simulring all forwarding numbers, and intelligently handle the response from each number during the ring interval, it intentionally doesn't play the SIT to the caller. Think about it: up to six forwarding numbers, plus Chat, plus Hangouts are all being sent the call at once. Whichever destination is capable of answering the call first, will get the call. You wouldn't want one of those numbers to interfere with the others being able to answer the call, and you, the caller, wouldn't want to hear some sort of cacophony of all the numbers either ringing, or playing a busy signal or SIT.
So, as I said, call handling is more effectively processed at the first hop (GV), but adding CC call treatments is an effective alternative that won't cause any problems. Other call treatments may or may not interfere with GV; use at your own risk.
Navigation
[0] Message Index
[#] Next page
[*] Previous page