Inbound calls ring late or don't ring at all with Callcentric and GV
SteveInWA:
There was a previous discussion here on the OBi forum about a related issue, of caller ID being lost in calls from GV to CC. There was a lot of finger-pointing by CC saying it was GV's problem.
This delayed/missing call problem may or may not be related to the CID issue; I suspect it is. My area code 845 CC DID briefly had the Anonymous CID issue, which then magically went away. Now, it's really FUBAR, and I also intermittently get the delayed or completely non-functional GV-->CC calls. This week, I am now getting a combination of anonymous CID, correct CID, or somebody else's random CID (!!!)
I now think it's pointless to flip between various CC free DIDs; I suspect they all are impacted by the issue, which is most likely as mentioned earlier, something about the route between GV's CLEC and CC's CLEC. Note that my PAID, local CC DID, which is on a different CLEC, works just fine.
My contact at Google opened a bug report for their engineers on the issues today. It would help encourage them to work on it if y'all would please pile on to either of these two discussion threads, depending on which bug you experience: Please be nice and add helpful data ;)
The anonymous/wrong CID thread: https://productforums.google.com/d/topic/voice/FOMC_n8pYUM/discussion
The delayed or dead call thread: https://productforums.google.com/d/topic/voice/HFVaCVxiD_w/discussion
What their engineers typically want, is a list of a few (3-5) calls, including the last 4 digits of your GV phone number (to authenticate that you own the account they're looking at and acknowledge that they'll be looking at your data), the date(s) and approximate times of calls that are not working, and the last 4 digits of the CC (or Anveo) DID that is not receiving the calls, receiving them late, or receiving them with anonymous or bogus CIDs.
Usetheforceobiwan:
I am having the same CID (incorrect/anonymous) issues as everyone else with CC NY based DID's. But I am also experiencing a problem with a GV # forwarded to an Anveo DID - you cannot pick up the forwarded call from a softphone it just keeps ringing and ringing like GV is ignoring the Anveo connection. This has been happening over the course of several days.
GV calls forwarded to Voip.ms DID's seems to work fine though.
I do think that something is trying to prevent the use of Callcentric as a free CallerID processor. I am not pointing the finger at anyone in particular but perhaps an entity is getting stuck with the freight to pay for all those lookups that are being performed.
CoalMinerRetired:
I'll confirm SteveInWA's observations, specifically it went away, but now I'm seeing a combination of anonymous CID, correct CID, or somebody else's random CID. The someone else's random CID is especially worrisome, because the CNAM shows as "New York" and I suspect this is a number in a block of CC numbers.
I'll jump in the linked threads, I do have faith in that GV and CC (especially CC) have worked out issues in the past.
SteveInWA:
I do encourage people with this problem to post on the two threads I linked earlier in the discussion. Concise, polite posts with lists of call information as requested in the threads will be most helpful. I will continue to nag my contacts at Google until it's either fixed or it's apparent that they won't fix it.
A bug report was filed with Google engineering on 12/6, so they at least have to look into it.
At this time, I can't recommend anyone use a Callcentric free DID as a GV forwarding destination. Callcentric paid DIDs work fine (assuming you select one that is not from their pool of free DIDs). This is because the problem seems to be isolated to the routing between Google's CLEC and Callcentric's "Telengy" CLEC:
http://www.localcallingguide.com/lca_prefix.php?ocn=473G
Navigation
[0] Message Index
[*] Previous page