Problem With Callcentric Incoming Caller ID
JustinS:
I'm pleased to report that the caller ID issue is resolved. It started working again. I temporarily switched to having the Obi100 receive my Google Voice calls directly through Google Chat, which provided number-only caller ID. I then switched back to forwarding my Google Voice calls to CallCentric, and the caller ID is once again working. Google must have resolved the issue on their end.
Let's hope it stays working.
VOIPisGreat:
I have also been getting the problem of callcentric showing Anonymous, while on the GV call log it shows the correct number. The occurrence is random, sometimes the same number will show on callcentric while some other time it'll appear as anonymous.
gmercator:
I have also been having this exact problem off and on.
First time was from about Sept 23 - Sept 26. It started happening again on Oct 9 and is still happening as of Oct 13.
My setup: obi 110
SP1: GoogleVoice for free outbound
SP2: Callcentric free NY DID number for outbound 911 and designated as inbound destination number for GoogleVoice. Inbound calls made to my GV number are directed to SP2's Callcentric NY DID number, where a match is made to my Callcentric directory and the Caller ID name field for that call shows my customized listing.... this has been an absolutely perfect setup.. very low cost and reliable..... until about a month ago.
Suddenly inbound calls were listed in the GV call log correctly and showing Caller ID, but when those calls reached Callcentric, the Caller ID number had been stripped off, leaving "anonymous" in its place.
In my limited testing, the problem was with calls made FROM Verizon Wireless or T-Mobile cell phones... this anomaly happened over and over when tested from either of these cellphone providers. In addition, when these 2 cellphones (one from VZW, one from T-Mobile), were set to ring as destination numbers in GV, and calls were placed to the GV number from a third (VZW) cellphone, both the VZW and T-Mobile cellphones received the Caller ID from GV while Callcentric did not (and showed anonymous).
I do not have access to any AT&T or Sprint cellphones to test.
I did not submit a support ticket to Callcentric since there are so many providers in this equation.... all VZW or T-Mobile calls made directly to my Callcentric NY DID showed perfect Caller ID, but those same calls routed through GV showed anonymous, both in the Uniden home phone Caller ID display, and in the Callcentric call log on the Dashboard page
Have any of you guys (or gals) had anonymous calls show up from GV to Callcentric that were made from a different provider than Verizon Wireless or T-Mobile
For now, I have inbound calls ringing on SP1 using GoogleChat, which shows number only, of course.
Thanks for any ideas or help to get this solved.
Additional testing info:
I just used the GV "web-trigger" callback option where you can type in the number you want GV to call when signed into your GV account on the computer and have it call you back on one of your verified phones....
When my Callcentric NY DID was chosen as the number for GV to call me back on to setup the outbound call..... the calls came in as "anonymous".... these calls did not involve any other GV destination phones since the dropdown box is specific to have GV call back on the one number that is chosen..
Again, thanks for any help or ideas
VOIPisGreat:
It seems to me that the problem occurs regardless of the source. I have had calls with this problem from both landlines and cell phones.
gmercator:
@VOIPisGreat... Thanks for your reply. Is your CallCentric number one of the Free NY DID's or a paid CallCentric DID?
AFAIK, the free NY DID's use CallCentric's in-house CLEC, Telengy. The paid DID's use other CLECS which may be much larger providers that have USA and international coverage.
As an experiment to change up the equation, I signed up for and added one of CallCentric's "Dirt-Cheap" DID's for $2.95/mo. It uses XO Communications as it's CLEC instead of Telengy. I verified it with GV and am now using the Dirt Cheap DID as the GV destination number. It still rings into my obi 110 on SP2 since it is on the same CC account. So far, every inbound call made to the GV forwarded to the new DID has shown the proper Caller ID. I will monitor this to see if that fixes the problem or not....
Thanks for any help or other ideas
Navigation
[0] Message Index
[#] Next page
[*] Previous page