Google Voice Failure
RFC3261:
Quote from: nmstough on July 02, 2018, 10:34:23 am
Help!
Did you follow the referenced directions?
nmstough:
If you mean I should follow all these procedures, no I dont think I can do that. I have many customizations of the configurations and I dont want to lose all those. Not to mention that I dont have all the Google accounts information for all the Google voice accounts that are connected to the Obi device.
audioresearch:
I was using an obi110 for years with no problems except that a few months ago I had to use Simon Telephonics to keep it working.
A few weeks ago it again stopped working (no incoming or outgoing calls) and so I ordered an Obi200 last Monday which was delivered last Tuesday (2 days ago at the time I am posting this).
I installed the Obi200 following all the instructions and it worked for a short period of time. Then I noticed that if as a test I called my cell phone from my analog phone that was connected to the Obi, the cell phone could hear the analog phone but not vice versa.
Then, I tried re-installing using the instructions found here (doing obi revert to factory defaults while obi box disconnected from internet, deleting all obi devices using obitalk, and I even deleted access rights for obitalk to access my gv account and I disabled the Simon Telephonics gateway. Then I re-connected obi box to internet, used obitalk to add obi200 back as a device. At the end of that procedure in the Obitalk window, I saw that sp1 was being configured to gv and saw a spinning circle indicating it was working away and then finally that changed to "connected" status.
Now, the problems got really bad. Can't make any outgoing calls nor receive any incoming calls using analog phone connected to obi. Incoming calls ring a bunch of times then go to gv voicemail. When I dial outgoing calls, I hear a voice saying call can't be placed.
I've tried re-installing using the above procedure at least a dozen times yesterday and today and there is no change.
I have noticed that when I check my gv account and look at what it forwards to, there are no obi devices listed.
Do you think this problem is being seen by many others or do you think it is probably unique to me? Do you think I should just return my Obi200 within the 30 days full refund return window I have and wait a while and buy it again hoping that there is some problem withing gv and/or polycom that will be resolved by then? If you have any suggestions, please make them, I'm all ears.
Thanks.
Engineering:
I am seeing the same thing with my new OBi200, at least I believe I do. The symptoms:
- Calling some numbers (in particular other GV numbers) works fine, it rings, voice mail picks up, I can leave a message, great.
- Calling most other numbers (toll-free or landline), it rings, then the other side picks up and sometimes I hear maybe half a second of it before the line goes silent. The call doesn't disconnect, I just can't hear anything on the other side, only static.
Went through the complete cycle of factory reset, re-registering the device with obitalk etc. again, no difference. I didn't do any modifications through the local web interface.
A_Friend:
I had managed to get Google Voice working again. It seemed straightforward.
BUT THEN...
I was trying to see if I could, I dunno, save my setup and restore it and either keep or get Google Talk working again.
I'm experimenting on my Obi200, which is an auxiliary/play setup in my home system, prior to dealing with the "real" hub of the system, which is an Obi202.
Now, I'm back to square zero, or maybe minus ten. Obitalk isn't reinstalling Google Voice in any usable configuration. I'm getting the exact same symptoms as Engineering says he is. I've done factory resets, even used the semi-hidden magic reset switch in the bottom of the Obi200.
The Google Voice setup isn't working anymore. Firmware level is: 3.2.2 (Build: 5897EX)
I mean, it goes through the motions and SAYS it works. Afterwards...
Obitalk says: Connected.
In-call Call Status is now saying this again, which I believe is the same thing it said when XMPP was failing:
Peer RTP Address: 74.125.39.26:19305(relay)
Which might explain why I'm getting the exact same symptoms as my old, obsolete XMPP setup was getting, which is what Engineering is seeing, too.
What gives???
Navigation
[0] Message Index
[*] Previous page