Inbound calls ring late or don't ring at all with Callcentric and GV
slowbiscuit:
I just setup a new Callcentric account for inbound calls only, and configured the Obi to register it on SP2. This works fine when I call the CC number directly. However, with GV setup only to forward to the CC number, my inbound calls only work intermittently.
My setup: Obi 100
SP1: GoogleVoice for free outbound
SP2: Callcentric free NY DID number, designated as inbound destination number for GoogleVoice. Inbound calls made to my GV number are directed to SP2's Callcentric NY DID number.
Incoming calls work sometimes and not others, and when they work it rings 3-4 times before my home phone rings or caller gets sent to GV voicemail. With GV set to forward to Chat and not CC it works flawlessly and has for years.
Call history in GV shows all inbound calls, history in CC portal only shows some of them (the missing calls get sent to GV voicemail).
Obviously there is some sort of issue with GV forwarding to CC, but can't figure out what it is. All I have for phones in GV is my old Chat for inbound (not checked) and the new CC number. I verified that all my GV groups are set to go to Callcentric.
Stumped at this point, basically GV to CC is unusable for me now.
gderf:
Do you have anonymous call rejection enabled on your free CC DID? If so, and a call comes into GV and is passed on to CC without caller ID it won't be forwarded to your OBi..
slowbiscuit:
No, I don't. I can try calls from my cell to my GV # and half of them get through (late), half don't. All of them show up in the GV history, the missing ones don't in CC. Same problem when dialing from my work # (a landline).
CPC_obi:
I am having the same issue as slowbiscuit.
Same setup on SP1 and SP2. I have GV set to ring both my cell and fwd to FREE callcentric/obi. The cell rings almost instantly when the GV number is dialed. On some days the forwarded to callcentric/obi rings a few seconds later and other times much later (5 rings or more) or not at all. In recent weeks its getting worse and worse.
I have had it setup this way for about a year and for most of that time the cell and the forwarded to callcentric/obi rang almost at the same time. Again.. its just recently getting worse and worse... bigger and bigger delay cause by callcentric. (and/or whoever is handling their free #'s)
As a test, I just reconfigured GV to ring straight to the OBI and simultaneously to the cell and took callcentric out of the equation. Problem gone.... The obi rings almost instantly and usually before the cell phone does. So the delay is cause by the callcentric hop. Note: I have all options off at callcentric, call treatments off etc.
Of course the negative is no incoming caller ID name... although callcentric was terrible with this anyhow as only a small percentage showed proper incoming caller ID name through them.
Now looking at alternative incoming caller ID name solutions rather than Callcentric..
Update: I see this other recent thread with a similar issue. Maybe its all call forwarding via GV and not just Callcentric??? Others with thoughts? https://www.obitalk.com/forum/index.php?topic=6965.0
slowbiscuit:
Yep, I've also tried switching to different free CC DIDs (in different area code) and it seemed to be better initally but then I noticed missing calls, same issue. This will make GV with the Obi useless in May when the Obi to Google Chat protocol goes away, because I won't be able to count on it ringing any inbound SIP service.
Problem is that GV is a free service and Google doesn't provide any real support, so who knows if/when the routing issue gets fixed.
Navigation
[0] Message Index
[#] Next page