Problems with Obi/GV once again....
DarkNova:
After continuing to experience this issue, I saved the device's configuration to a file (System Management -> Device Update -> Backup Configuration), then did a factory reset by holding the small switch on the back with a paperclip for 10 seconds, then I loaded the configuration back into the device. I was attempting to test if something was messed up in the device that could be fixed by a wipe and reload. It continued to malfunction.
Next, I did a factory reset again and reconfigured Google Voice from scratch, without reloading the configuration. This time everything seems to work. I am able to do both incoming and outgoing calls.
So it would appear that there was something in how the Obi110 was originally configured that was causing a problem, but did not manifest itself until recently.
I did a diff on the two config files and they are almost identical, but have a few small differences. I do not know enough about the config options to know the significance, but hopefully someone in Obi's support can use this to identify and fix the issue.
But in the meantime, you may want to try a similar factory reset and reconfigure and see if that fixes your problem.
richardcoop:
My theory is that the obi110 usually gets better voice quality than other VOIP devices because it uses more data and some sort of smoothing algorithm to improve quality. .
In the Obi when the data flow is inadequate the voice starts breaking up or, in extreme slowdowns, no voice is received. In cable Internet connections, the upload speed is much slower than download speed. You can see your own data speed by looking at the site speedtest.net Since the internet speed limitation is on the upload or sending side the problems all reported are people who can't hear on the other end because the outgoing data flow is inadequate, but you can hear them.
I have been following the upload speed of my local Cox Cable connection using speedtest.net and find that it varies widely. This weekend, when I was having problems, the speed was lower (2 Mbits/sec) less than half what it is now.
Does this make sense? It would be useful to see more speed data from other troubled installations to confirm my theory It would be interesting to see what the internet speed that is required for good performance of the Obi. A solution would be for Obhai to rewrite the smoothing algorithm so that it is more tolerant of lower internet speeds.
DarkNova:
Definitely not what was happening in my case. My internet speed was still testing fast the whole time and the problem immediately went away after the device was wiped and reconfigured. If you chart it, the Obi doesn't actually use that much bandwidth in the grand scheme of things.
dvbhardware:
When everyone had this issue in this thread, my service was working fine.
Now I am having this problem for incoming calls only. As an alternative work around, and if you have a phone app turn it on to connect to GV with Groovip Lite to bypass the Obhai for incoming calls
See http://www.obitalk.com/forum/index.php?topic=2773.0
Jimmy
kenny113:
I too am having this issue with a Obi110. Dead air on inbound and outbound calls. It just happens randomly. Not every call. Not every third call. Just random. Rebooting doesn't seem to be a resolution. Sometimes it still does it after a reboot. Even after a reboot of the entire home network. Nothing has changed in my home network config. This started happening about 2-3 weeks ago. I'm going to go ahead and factory reset/reconfigure my device and hope it fixes it. I have a friend in Chicago who is having these same issues with a brand new Obi100 that he just purchased three weeks ago. Perhaps something with GV changed or perhaps something strange happened with the last firmware update.
Navigation
[0] Message Index
[#] Next page
[*] Previous page