Problem With Callcentric Incoming Caller ID

(1/9) > >>

BearJerCares:
I have set up an Obi 100 using Google Voice, plus I have set up an additional incoming phone number with Callcentric.com for the purpose of being able to have 911 service and caller ID.  Everything is working well except I have a hit and miss problem with Callcentric's caller ID - it only shows the NAME about half the time.  I submitted a ticket to Callcentric and submitted my Obi configuration screenshots to them, but so far they have not been able to diagnose the problem.  Furthermore, they say that I am only paying $1.50 for 911 service and they make no guarantees that the caller ID service will come across with their "free" phone number.   Is anyone else using Google Voice and Callcentric with the Obi having issues with caller ID such as this and do you know if there is a setting in the Obi that could be tweaked to help alleviate the problem?  Thank you,  Jerry in Michigan / BearJerCares@gmail.com

BobTeatow:
I've had callcentric and Obi and google voice for more than a year.

But I just recently started using my free callcentric DID as the target phone for my google voice in coming calls.
I did this exactly so I would get CallerId and NAME.

So far it pretty much works as expected.

As with the other phone companies, Callerid/Name is not 100%. 
More like 95% for numbers and 50-90% for names DEPENDING who is calling you from what kind of service.

With more than 1/2 my calls coming from cell phones, the best you get when receiving a cell phone call is
"Cell Phone - <name of state>" 
I wonder why, since most cell phones are post-paid phone registered to a particular name, why don't the cell companies cooperate with caller-name?  But they don't.

BUT there is a cool Callcentric feature - you can put names and phone numbers into an online "phone book" associated with your Callcentric account - then whenever an inbound caller-id NUMBER "hits" on your personal phone book, Callcentric over-rides the calling name provided by the other phone company and instead, of course, send the name you specified in your personal callcentric phone book.

There is a way to import/export phone books as simple spreadsheets...
And/Or you can can review your incoming calls on callcentric "report" and work with that...

MikeHObi:
I rarely get incoming calls at home but wife gets them frequently and today she told me that calls have been coming up as Private for the last 1 and 1-/2 week.  I checked on my CallCentric Dashboard and found that calls showing up as private are showing as Anonymous on call centric's system.  I suspected a problem with Google Voice so I switched voice to route to my secondary VOIP provider Anveo.  Calls through Aveo properly showed numbers and would give names as well.  Switched back to Callcentric and still having the problem.
I opened a ticket with Callcentric to see if they can figure out what is going on.  I'll report back what I find, for now I'll switch to having Anveo handle calls for a while.

JustinS:
MikeHObi, I am having the exact same problem you described.  My CallCentric call log started showing all calls as anonymous around noon eastern time on Friday, Sept 27th.  It's been two days now.  Please keep us posted on what CallCentric says when they resolve or close your ticket.

MikeHObi:
Here is the results of the ticket and talking.

Problem is not CallCentric and is Google.  Calling my GV number forwarded to the Free NY DID from my Cell phone I get Anonymous on the call log at CallCentric.  Calling my Free NY DID number directly from my cell phone I get CNAME and CNumber from the phone book entry I have at Callcentric. 

Call Centric verified this information in their reply to the trouble ticket, if they get nothing on the incomming that what gets sent out.

For now I'm routing GV through Anveo as I get CNAME through that as well.  I'm going to figure out how to tell Google they have a problem with their 914-662 numbers not getting the calling number reliably.

Note, it has been somewhat random in that everyonce and a while CNUmber would get through.  But more often than not it didn't.

Navigation

[0] Message Index

[#] Next page