Google Contact Info no longer coming through for Caller ID info
Ember1205:
I have a very long list of contacts stored in Google as I sync both my personal and work cell phones via that method so that I always have every possible phone number available on both phones. For a very long time, my OBI200 would correctly pass information about the contact through to my phone's "Caller ID" screen when they called my GV number. This is no longer working.
Example: I have John Doe stored as a contact in the Google Account that I use with GV (and that is connected to my OBI). The phone number is (212) 555-1212. If John calls my GV number, I no longer see "John Smith" but only (212) 555-1212 in the display on my phone. Looking at the call history directly in GV, I see the contact name shown.
Does anyone know why this behavior has changed?
My OBI device is directly connected to my GV account using SIP communication for inbound calls. It WAS connected via CallCentric call forwarding until they removed their free service a couple of months back. The Caller ID functionality seems to have changed independently of that configuration change, however.
Please note: I am NOT referring to anything to do with CNAM. Many of the numbers that I have stored are business numbers that I have overridden with personal names because I don't care that "Company X" is calling me - I care instead that "Person Y" is calling me. I've never had an issue with this in the past because GV has always overridden any specific Caller ID info and sent the stored contact information instead (which means that a CNAM query wouldn't be used or needed). Forwarding this info to CC in the past always ensured that the Contact Information is what was seen as well. So, this has nothing to do with executing a CNAM query and GV is already passing a name. Why is the OBI device not passing that through?
drgeoff:
Regular readers of forum posts will have noticed many reports of GV/OBi issues over the last few months and few if any of them have been resolved.
My guess and I emphasis "guess" as I have no inside knowledge is that Google has been making and continues to make tweaks to GV which would require corresponding changes to OBi firmware. Either details of the changes are not being communicated to Obihai or if they are they are not reaching the relevant OBi engineers or there are no longer any OBi engineers who have the technical competence to act on them or Obihai engineers who do have the competence are for some reason not doing so.
Additionally, though I have no evidence, it is difficult not to be tempted into thinking that the current "Obihai malaise" is connected with the Polycom acquisition of Obihai. Which of the two might be cause and which be result is another question.
Ember1205:
Thanks for the response.
I continued to dig and search after posting this and wonder if this is actually a purposeful change on the part of Obi/Polycom in an effort to increase revenues. The "Obi Extras" package claims to make this exact function available if I am will to subscribe to their $4.99/month service. While I can totally appreciate their interest in trying to drive revenue up, I absolutely do not understand this specific item.
GV will provide the Caller ID Name along with number to a Linked Number. This is exactly how information had previously been passed to CallCentric. When that number receives the information, it will skip executing a CNAM lookup since it already has the detail and will then forward that through to the device. For $1/month, I could re-establish my CC account and leverage the same exact functionality I had before. It would seem to me that Obi would stand more of a chance of selling the ObiExtras package if they actually did CNAM lookup for full Caller ID instead of "only" allowing the contacts information through.
Taoman:
Quote from: Ember1205 on April 05, 2019, 09:56:29 am
GV will provide the Caller ID Name along with number to a Linked Number. This is exactly how information had previously been passed to CallCentric. When that number receives the information, it will skip executing a CNAM lookup since it already has the detail and will then forward that through to the device. For $1/month, I could re-establish my CC account and leverage the same exact functionality I had before. It would seem to me that Obi would stand more of a chance of selling the ObiExtras package if they actually did CNAM lookup for full Caller ID instead of "only" allowing the contacts information through.
Not "exactly," as that's not the way it works with Callcentric. GV only forwards the number to Callcentric, not any other Google Contact information. Callcentric only does CNAM override if the incoming number matches a number in your Callcentric phone book, not in your Google Contacts. The only other way it might match is if the Google Contact is also in your telephone's phone book. Just tested this again and that is the way it works.
But that aside, I agree with your sentiments regarding OBiExtras. In my view, paying $1/month for a CC DID is well worth the cost for the CNAM, spam detection, and call treatment features.
Quote from: Ember1205
I continued to dig and search after posting this and wonder if this is actually a purposeful change on the part of Obi/Polycom in an effort to increase revenues.
That's my guess also.
Ember1205:
Good point on the CC Contacts / Phonebook. As I think back, it's likely that I exported my GV Contacts and imported it into CC when I set everything up and then did ongoing management over time...
Still........
I would be more than happy to do that and spend $1/month for full CNAM than $5/month to "only" get my GV contacts.
Navigation
[0] Message Index
[#] Next page