(FIXED) GV CID outbound "UNKNOWN CALLER"
gmercator:
I have 2 separate GoogleVoice numbers with different area codes.
Both GV numbers are listed as assigned to 981E BANDWIDTH.COM CLEC, LLC - CA and both are in Southern California, so they aren't across country from each other.
The one with area code 8xx is assigned to sp1
If I manually select sp1 by dialling **1 before the called number, the called party gets UNAVAILABLE in their caller ID
The one with area code 7xx is assigned to sp2
If I manually select sp2 by dialling **2 before the called number, the called party sees the calling number from GoogleVoice as 7xx-xxx-xxxx.
I have also replicated these results by using GoogleTalk through Gmail for each GoogleVoice number and the results are the same. The 8xx GV number shows UNAVAILABLE; The 7xx GV number displays correctly.
If I use the GV web trigger (where it calls you back first to initiate the call), BOTH GV numbers show correctly at the called party's end.
I have tested this by calling 3 different destination/called numbers:
AT&T POTS landline
Verizon Wireless cellphone
T-Mobile cellphone
All three providers gave the same results when those numbers were called.
This seems to be a problem with the GoogleTalk/GoogleChat client software and doesn't affect all users the same.
This problem is noted on 2 separate GoogleVoice forum threads:
http://www.google.com/support/forum/p/voice/thread?tid=49c21d292e80ff65&hl=en
and
http://www.google.com/support/forum/p/voice/thread?tid=305a3852cb635c69&hl=en
I don't think this is a problem with the obi110
If I can think of anything else to try to isolate the problem, I will post those results here.
Hope this helps.
Loughary:
Thanks all for replies...I've tried calling multiple numbers with the same results...one is with charter cable and the other are with AT&T mobile...I hope I can figure this out....I was so hoping to cancel my landline and save a few bucks...but If everyone that I call is going to see "UNKNOWN CALLER" as my CID that's not going to fly.
Thanks.
OBi-Guru:
There are reports of UNKNOWN callerID being sporadically showing on certain GoogleVoice accounts, and the cases happen even without OBi devices involved.
There is no setting available on GV to enable/disable this. Let's wait and see what GV team have to say.
jimates:
I spent several hours on the GV help forum tonight answering all types of questions and there were dozens of reports for caller id problems. The problems seem to have started mostly on Tuesday.
Some did specifically say that when they initiated from their GV page that the caller id was fine, but when initiated from gmail (like a call using the Obi) their GV caller id was not shown.
Mine still works fine.
MichiganTelephone:
Just some thoughts on this:
First, it would be helpful if those who are experiencing this problem would post the area code and first three digits of the affected number(s). I'd be interested to know if this involves all numbers in a certain region or from a particular CLEC.
Second, Google is never very quick to fix reported issues. We had a situation last yer where a whole block of Gizmo5 numbers (remember that Google bought Gizmo5) just stopped working. After a while we were able to figure out that it only affected Gozmo5 numbers in a particular number range and that more than likely some Google employee had put in an incorrect rule somewhere. Even then it took them over two weeks to get around to fixing the problem (and i think there were many more complaints about that issue than this one).
Third, people need to remember that they bought a product that worked with a particular service at the time they bought it, and that still works for many people, but the people who make the product cannot control what the people who offer the service do. If you lived in a rural area with only one TV station and you bought a TV to receive it and then the station went off the air, you wouldn't blame the TV manufacturer. The Obihai people cannot control what the Google Voice people do (in fact I wonder if anyone can - Google has become much too large, in my personal opinion).
Fourth, I'm wondering if any Asterisk 1.8 users are having this problem. I haven't personally seen it, but then again, all my Google Voice accounts have Michigan numbers. And I'm not seeing this issue on the account that I use with my OBi device either (also a Michigan number). Therefore it may be not so much a case of "you can't have outgoing caller ID" as "you temporarily (until they fix it) can't have outgoing caller ID IF your Google Voice number falls into one of these affected patterns."
My bet would still be that in the end this will be determined to be the fault of a CLEC that Google Voice uses to complete calls, but right now we have no idea which CLEC it might be.
Navigation
[0] Message Index
[#] Next page
[*] Previous page