SOLVED: My Google Voice caller ID don't show up on receiving phone
DaveSwartz:
I am not having this problem. I have an obi110 with the current firmware configured through ObiTalk to use GV. When I call, the receiving phone sees my GV number in their caller ID.
RonR:
Quote from: AndyA on February 16, 2011, 11:05:40 pm
I did more tests and found that when I dial through the Google Voice interface, where you go to the Google Voice web page and click call and select the phone to call with, it does show my GV caller ID. But when I dial through Google Chat on the Gmail web page, it does not show the caller ID. This seems to point to direct calls made through Google Chat (which is what OBi is simulating) not showing the caller ID.
This has a major implication. If you get rid of of your land line to convert to OBI and Google Voice combination, your calls will always show UNKNOWN on the caller ID. You could end up with the hassle of your calls being ignored. I hope the Obihai people will look into this right away 'coz it's a major downer if there is no fix or if it happens intermittently.
This pretty much proves that it's a Google problem and there is likely nothing Obihai can do in the OBi110 to correct it. The OBi110 simply emulates a Google Chat client. If Google Chat is broken, it's Google you should be expressing your concerns to. Once Google fixes Google Chat, the OBi110 should work as desired.
ipaksolutions:
google must be testing or doing something. i am having the same issue with any incoming or outgoing calls that are through gchat showing up as unknown caller-id's. knowing google, this should be restored and back to normal once they are done "playing".
MichiganTelephone:
If they insist on "playing" with it, I hope they fix the bug in their system where when you set Google Voice to disable call screening it doesn't work for Google Chat calls (which is what necessitates having to include the X_SkipCallScreening option in the Obi device).
That's what gives me pause about Google Voice - if they have any plans to start charging for their service after 2011 (which of course we all hope they don't) they had better get their act together and find a better way to deal with issues as they arise, and not two weeks or a month later. People tend to get REAL cranky when they're paying real money for a service and it doesn't work as expected. As long as it's free, you sort of have to take what they give you.
MichiganTelephone:
I'm going to throw one other thought out there - just call this "wishful thinking out loud."
Of course my real hope is that Google Voice acknowledges that they have a problem and fixes it. As I say, the last time I saw an issue like this that affected a large number of users, it took them over two weeks to fix it.
It would be SO much easier to interface with Google Voice if they would allow direct SIP connections to their service (or even just SIP forwarding, which would be half a loaf, so to speak). However, at this point, the only such connection they allow are to Gizmo5 users. And the problem there is that Google bought Gizmo5 and then immediately shut it down for new accounts. It's obvious that they wanted it for some reason, but apparently NOT to run it as it had originally been run.
My thought is this: If the OBi folks could actually figure out how to get in touch with someone at Google, maybe they could figure out a way to get a similar type of peering into the OBiTALK network. I don't know how "approachable" Google is (I suspect "not very") but still, the Gizmo5 folks made it happen somehow, back before the big G swallowed them up like a shark eating a minnow. If an agreement could be worked out, what you could then do is make an OBiTALK number a Google Voice destination.
Or there is thought #2. See if anyone can find out why Google bought Gizmo5 and whether they really want it. Maybe they've mined it for all the technology they can get out of it, and now it's a service that they are just keeping on life support, as it were. Maybe they'd be willing to sell the existing subscriber base and platform, and maybe Obihai could buy it and offer it as a service to Obi device buyers. They would have to make sure that the purchase agreement included a clause that maintains the existing ability of Google Voice users to pick Gizmo5 as a destination. Obviously from Obihai's standpoint this would not be as desirable as the ability to just pick an OBiTALK number as a destination, but if Google Voice would really like to unload Gizmo5 (and I have no idea why they are keeping it since they obviously don't want to start adding any new accounts) it might be a way in.
The goal here is to get a genuine SIP connection or SIP forward from Google Voice. Of course if Google actually fixes the issues with the Caller ID then we'll all be happy, but as I say, the last time this sort of thing happened it took them over two weeks. I do suggest that anyone who's experiencing this issue be sure to leave a post in this thread, and encourage anyone else you know that's having this problem to do the same. If they thought it was affecting many users, it might get higher priority.
Navigation
[0] Message Index
[#] Next page
[*] Previous page