Callcentric call treatments.
giqcass:
Quote from: Taoman on February 03, 2015, 10:28:12 pm
This is incorrect. If Google Voice "assumed" the call had been picked up then voicemail would not kick in after 25 seconds. It does.
When trying to use CC telemarketer block with Google Voice your Callcentric line will not ring but your other forwarding phones will most definitely continue to ring until one is answered or GV voicemail picks up.
Don't take my word for it. Try it yourself.
EDIT: Let me clarify. Steve only said some Call treatments would not work correctly with GV. How I said they misbehave was based on my earlier tests that I performed a long time ago and either something has changed or I simply remembered incorrectly. It appears you are correct and it ignores the telemarketer block. Good catch! I updated the original post to reflect that.
I will also split the original post into a GV and NonGV section as you suggest.
SteveInWA:
Quote from: Taoman on February 03, 2015, 10:28:12 pm
Quote from: giqcass on February 03, 2015, 08:32:14 pm
SteveInWA brings up a good point in another thread about CC telemarketer block. If you are using the telemarketer block with GV then GV will assume the call has been picked up(because it has been). As a result any Voicemail left will end up on the CC server. In addition your other forwarding phones either will not ring or will ring just 1 or 2 times for any call sent to the telemarketer block.
This is incorrect. If Google Voice "assumed" the call had been picked up then voicemail would not kick in after 25 seconds. It does.
When trying to use CC telemarketer block with Google Voice your Callcentric line will not ring but your other forwarding phones will most definitely continue to ring until one is answered or GV voicemail picks up.
Don't take my word for it. Try it yourself.
I don't recall that discussion, vs. all the other stuff we have discussed on this topic. Perhaps I mis-stated something at the time. It should be clear that Callcentric's telemarketer block feature won't work when forwarding a call from GV to CC, because the GV caller won't have any way to respond to the CC "press a key" prompt. GV is just going to keep ringing all forwarding phones. I explained why this is the case, in yesterday's discussion.
Taoman, you keep bringing up the "GV doesn't support early media" issue. The point is, GV is ignoring what goes on during the early media period, on purpose, so that it can properly simulring all forwarding destinations, and give the call to the first destination that actually answers the call within the 25 second time period.
giqcass:
Quote from: SteveInWA on February 04, 2015, 12:16:02 pm
I don't recall that discussion, vs. all the other stuff we have discussed on this topic.
I had worded that post very poorly the only comment I meant to attribute to you directly was the part where I said.
"SteveInWA brings up a good point in another thread about CC telemarketer block."
SteveInWA:
OK, thanks.
Not to derail your thread, but to further clarify the "early media" issue: Big picture: GV, itself, is designed to be the one inbound call handler/manager, and thus, it is not designed to interact nor to otherwise be compatible with any subsequent call handling technology. GV, itself, is using early media on inbound calls to your GV number: when you enable GV call screening, for example, the caller hears ringback tones, while GV forwards the call to the forwarding number. At that point, when you "answer" the forwarding phone, the call is still in the early media period, and the person answering will hear Kiki tell them to press "1" to accept the call or press "2" to send it to VM. Only after that happens, or 25 seconds expires, is the call actually answered (meaning, the VoIP equivalent of "answer supervision" is sent, and the parties are connected).
This same early media behavior is occurring on every inbound call to a GV number, while GV forwards the call to all the forwarding targets (forwarding phones, Chat and/or Hangouts). Thus, GV, by design, intentionally ignores subsequent early media behavior on the called number, as there would be no way to interact with it from the calling party's end. This is the same reason why various inbound services, like human answering service bureaus, or certain TFN IVR systems, are incompatible as forwarding destinations for a GV number.
Bottom line: some OBi users think of GV as a free inbound VoIP trunk, like a SIP VoIP DID. It's not. It's a call forwarding and call management system, and it's intended to be used in that manner with forwarding phone numbers that don't do further call processing.
Taoman:
Quote from: SteveInWA on February 04, 2015, 12:16:02 pm
Taoman, you keep bringing up the "GV doesn't support early media" issue. The point is, GV is ignoring what goes on during the early media period, on purpose, so that it can properly simulring all forwarding destinations, and give the call to the first destination that actually answers the call within the 25 second time period.
Semantics. In your honor, Steve, I will now start posting that Google Voice ignores early media. Will that appease your sensibilities?
In my view, this is a distinction without a difference. I am fully aware of why GV "ignores" early media. But is that really "the point?" Isn't the real point that destinations using early media just don't work for the caller when using Google Voice? I doubt someone trying to troubleshoot this issue is going to care all that much about why Google Voice ignores early media.
But if you feel compelled to continually post why Google Voice ignores early media by all means knock yourself out. To me it is irrelevant. In the end, all that matters (to me) is that destinations using early media don't work with Google Voice. The caller will just hear a ringback tone until GV voicemail picks up the call. And after all is said and done isn't that really "the point?"
Navigation
[0] Message Index
[#] Next page
[*] Previous page