Since 5/8/2012 night, GV stop working
synchron:
Quote from: yorktown on May 09, 2012, 07:33:22 pm
RonR - I agreee - Obitalk had created a business based on an opportunity that GV made available. Nevertheless, the product is physical hardware. GV is the main reason why most people buy the device. Pretty simple, Its a $40-100 one time fee for free phone use. So its in Obihai's best interest to have a good line of communication with the Google Voice people. Not having that results in what we saw yesterday. Obihai is a new company, so everyone is cool with the phone not working for a 1/2 day because GV did a major change.
But as a new company, Obihai needs to learn from this. The smartest thing for Obihai to do is reach out to GV staff and start talking.
I think my setup is interesting since my SP2 is still set to use the same google voice account via GV's webcallback system and sipsorcery as was configured with my old ATA. It would be ironic if Google were to do something and counter-exploit the XMPP side as I would still have free outgoing/incoming service from Google.
Synchron 8)
jimates:
Many of us have had Obis in service for 15 months +. This is the first "major" service interruption between google and the Obi. Like many, we weren't home today, but our cells still rang as normal from google voice, so no ill effects for us at all.
It's probably the same for all phone service providers, as it was when I had land line service. They are not obligated to issue credit for non service periods of less than 24 hours.
Google is going to pro-rate everyone's bill for this month and issue a credit for 12 hours of outage.
RonR:
Quote from: frankb on May 09, 2012, 08:27:50 pm
It says SoftwareVersion 1.2.1 (Build: 2385)
If i try to load the new firmware it tells me "Previous version identical to the update. Firmware not modified. " I'm trying to load OBi-1-3-0-2711.fw.
I doubt anyone but Obihai can help you at this point. It sounds like something went wrong during today's update.
Lavarock7:
I'd like to make a couple of comments as I was in the process of changing configs on a remote unit when the GV issue came up. Unfortunately, I didn't understand what was happening until I had spent hours on not getting the unit to work. I went to bed and found the solution in the morning.
I too believe there is little to no communication between Obi and Google. I don't think that is Obi's fault. I also work with a shopping cart (ZenCart) and interface between the carts inventory and Googles product feed (Froogle). Google decided to make changes to the format and gave many of us very little notice to make the massive changes needed. Then there were what I consider some poorly documented and implemented ideas. Many people who relied upon the interface to the product feed lost their products out of Google product search engines in the meantime, which would not have been in Googles, the developers or the storekeepers best interest.
I agree with those who believe that Obi is using Googles interface without Googles approval, but somewhat with their blessing. The ability of Obi to connect and get many more people to use GV then would normally, helps Google in their plans to use GV for whatever they ultimately designed it for. Obi and the rest of us seem clueless to the many years of free service that does cost Google real money to support. (My guess is that Google will offer ads instead of dial tones or subliminally add ads in the audio stream during calls ;D.
Watching my unit constantly try to access Google and knowing that there are many Obi devices out also banging the servers, would have given me the idea to push an update IF I was in charge and was worried that Obi would cause Google enough problems that they may squawk. I noticed that my sisters unit started working and was not offered a software update, but I did try every way I could to get it to recognize changes via the portal and boot, which it appeared not to want to do.
I understand that there are people out there who detest that Obi seems to have the ability to possibly "contact the mother ship" and do forced updates even if the owner doesn't want it to. As an IT tech I also understand that certain situations almost demand that a unit do no harm (as it were) to the infrastructure. Assume a scenerio where a number of Obis (or computers) could be taken over and directed to become zombies and attack the DNS servers of the world, thus interfering with the downloading of critical porn ::)
I too agree that we are not guaranteed to be able to use the Obi devices with GV but that every day we do will help us to save money and encourage Google to continue to allow it.
Rikin:
changing DNS to 4.2.2.2 fixes the issue.
either update your router DNS to 4.2.2.2
or
update DNS in OBi.
Follow the steps on page 13 of doc http://www.obihai.com/docs/GoogleVoiceOBiTALK.pdf
Navigation
[0] Message Index
[#] Next page
[*] Previous page