(FIXED) GV CID outbound "UNKNOWN CALLER"

<< < (4/6) > >>

MichiganTelephone:
Okay, it's now official — this is NOT just an OBi device issue:

http://pbxinaflash.com/forum/showthread.php?p=59975

For those that don't know, "PBX in a Flash" is one of several "install it yourself" PBX distributions that include the CentOS (Linux) operating system, the Asterisk PBX software, and the FreePBX web-based GUI and configuration file writer for Asterisk.  If those guys are having this issue, then it means it's a Google Voice problem (or a problem with one of the CLEC's they are using to provide service) beyond the shadow of a doubt, and NOT something that Obihai can do anything about.

gmercator:
I found 16 separate threads in the GoogleVoice Problem Solving area that are reporting this same issue. I have posted the response below to each and every one of them.  I don't know of any other way to bring this to the attention of GoogleVoice techs. Hopefully the squeaky wheel will get greased.

This is not a problem with the OBi110.

If you have one of the affected UNKNOWN CallerID GV numbers and are trying to use it with your OBi110, please go to the GoogleVoice Problem Solving page and respond to at least one of the many threads that are already there.

To help a GoogleVoice tech (if one ever reads these posts), please list your GV number with area code (NPA) and first 4 numbers of the GV number.

GV's primary provider, Bandwidth.com, may only own one or more thousands groups within a prefix and not the entire prefix.

I am copying and pasting the URL for the GoogleVoice Problem Solving page here: (hope it works)

http://www.google.com/support/forum/p/voice/label?lid=7c2a1629dac84e4d&hl=en

My response to those posts is below:


We are now 4 days into this problem and still not fixed. (since 02-15-2011)

Google Voice techs need to open a trouble ticket with Bandwidth.com to investigate, if that has not already happened.

805-628-2xxx here. Shows UNAVAILABLE when used from Gmail on computer.

Let's keep these threads current with updates.

Please list your area code and first 4 digits of your GV number that has the missing Caller ID issue through Gmail.  In many cases the prefixes are split down to thousands groups, so Bandwidth.com may not own the entire prefix.

I am posting this same response in other common threads. Hopefully that will help to get the ball rolling.

Many thanks to everyone else who has taken time to report this.

MichiganTelephone:
WORKAROUND:  If you are affected by this and find you have a need to place a call with outgoing Caller ID, you could possibly do it using a workaround suggested in the PBX in a Flash forum by user "tiggerpaws":

Quote

For now, I am dialling my own GV number and then using the "press 2 to make a call" and then dialling it that way and it seems to pass your GV caller ID, but in the calling records it does not say the actual # you are dialling just that you dialled your GV number for X amount of minutes. But, it will do for me, for now. I'd also like to hear any news. 316-742-XXXX

I haven't personally tried this because I'm not affected by this issue (so far). Don't forget you can put your Google Voice number in a speed dial slot (which you would probably do anyway to make checking your voicemail easier).

I suppose that if Google doesn't fix this issue in a reasonable timeframe, the above process could be automated in some way, but as I noted previously, the last time they had an issue like this it took them a bit over two weeks to fix it, so it's probably not worth the effort to code around the issue until they've had at least a few more days to fix it.  In the meantime, whether the above hint works or not, I still encourage anyone affected by the issue to leave a post in their forum.

azrobert:
Looks like this is a Google Voice problem.  Got this fix from one of the GV threads.  In GV call settings changing the Incoming CallerID to display your GV number fixes the Outgoing CallerID problem.  For me this is not an acceptable fix because you lose incoming CallerID.

sfcwtuOBI:
Letting incoming CID display GV number does fix the outgoing CID problem for me. I have two GV numbers. Their area codes and the first 4 digits are all the same. It's strange that only one has the outgoing CID problem. So I don't think reporting the first 4 digits along with the area code would help google too much in solving the problem. The only difference I can think of between my two GV numbers is that, the one with unknown outbound cid has the "make call from gmail" function enabled. I tried to disable the function from gmail completely. However, I can only disable outbound calling from gmail.  I can't completely remove the module from gmail. Could that be the problem?

Navigation

[0] Message Index

[#] Next page

[*] Previous page