Calls to GV number forwarded to Callcentric DID's encounter delays

jsolo1

I posted this on HoFo, but figure this might get more attention here.

Noticed this recently. May have been going on for some time as I mostly make calls.

Seems if a call involved gv <> callcentric interchange, there is a delay.

1) Initiate call from mobile using carrier number (NOT place call using gv number), to my gv number (which forwards to the callcentric DID) it takes a good 12-15s before CC DID rings.

1.5) Similar to above, but use gv number to call the CC DID, same delay

2) Enable gv app to place calls using gv number, call CC DID, same 12-15 delay. Doesn’t matter if mobile is set to use carrier or mobile data for the call

It seems if gv/cc is involved in any way in the path, there’s the delay before call is ringing at the dialed number. In addition, once it does connect, there appears to be noticeable latency.

Using GV to call my 2comm DID doesn’t suffer from this issue. Call rings immediately and no delay.

Below is the response from CC regarding this;

Seems to make sense. On the receiving (softphone) end, just as the call appears, I can hear what sounds like a brief switchover on the mobile. Similar to what one hears when a call stops ringing and is forwarded to vm, that brief change in the ringing sound.

I suppose the delay in ringing is tolerable. What isn’t is the latency. More times than not, I have to tell the caller I will call them right back.

Suggestions?

david3

I originally had service with GrandCentral, before Google bought them. For so many years I had the same GoogleVoice/GrandCentral number. Until last year, when google terminated my service due to some policy violation. They don’t say, but it is true I’m using it overseas. But that’s been true since I signed up with GrandCentral.

So I just use my newer number with AnveoDirect now. Ironically, I thought GoogleVoice (and gmail) would be something I could trust to be dependable long-term. But this experience (and other nonsense from Google) proved to me it’s just the opposite.

px_eliezer_

No harm in using GV for outbound, but I no longer depend on them for inbound.

Wolf_Barron

jsolo1

Came here to comment on this. Last year I had the exact same issue. The only difference was that it was a Google Fi number (not Google voice) forwarding to a Vonage landline number. I remember having a 10-20 second delay before the Vonage line would ring. I was on the phone with Fi customer service several times and what resolved it for me was removing forwarding to my Vonage landline in Google Fi settings and then re-adding it 20 minutes later. This was recommended by a Google Fi cust service rep on the phone. Since then it has worked like a champ. If you try this and it works report back. Good luck!

jsolo1

px_eliezer_ How does that work? How can you use gv for outbound while still retaining the same CID for inbound without it going through gv?

Wolf_Barron Thanks for the comment. I tried this on one line, in fact didn’t add it back til a few hours later. Results are inconclusive. There’s still the ringing delay but call audio sometimes has delay, other times not. So not sure it helped all that much.

I do have an insane working solution! It’s still in testing, but so far has been positive.

One drawback I’ve noticed already is lack of CNAM CID, only CID number, but IVR (which is the main spam filter) still appears to work. Latency is minimal to none.

Half @ssed Fix:
In the obi (200/202/obiphone/etc) config, under voice services, SP slot for GV, look for X_InboundCallRoute, within, rather than route the call to PH1 (physical handset), I have it routed to sp2 (which is the callcentric SP) specifically, sp2(17771231231234@in.callcentric.com). This bridges the call to callcentric, which is where the spam filtering takes place. For white listed callers, it rings back to the obi sp2 slot, which has the physical phone as the output device.

Yes, very convoluted. The end result is calls ring almost immediately. For white listed callers, which is handled via a hunting group on CC there is no latency in audio. For unknown callers which go through the ivr, latency is slightly higher but still acceptable - much better than when the call was forwarded to CC by CC first.

<< mind blown!@#>>

P.s. As an added bonus, since inbound calls are now coming to the gv SP slot rather than CC, call waiting now works if already on an outbound call. With calls forwarded to the CC DID, inbound callers would get a GV greeting if already on an outbound call.

px_eliezer_

jsolo1 How can you use gv for outbound while still retaining the same CID for inbound without it going through gv?

You don’t. 🙂

I simply do not use Google Voice for inbound calls.

jsolo1

px_eliezer_ I simply do not use Google Voice for inbound calls.

So outbound calls originate from a different number than those received at? Got it!

How does this not confuse your callers?

px_eliezer_

jsolo1 How does this not confuse your callers?

Typicially I use Google Voice for outbound calls that do NOT have such a possible confusion.

For example, when calling from my cellphone (using WiFi) to my office, thus saving cellular minutes….