Since 5/8/2012 night, GV stop working

[frankb]

I can not receive incoming calls, and can not making any calls with my obi110/google voice. When I dial a number, I hear a few clicks and then the dial tone comes back. If I try to dial ***6 or ***1 I get the same clicks and then dial tone.

[RonR]

I can not receive incoming calls, and can not making any calls with my obi110/google voice. When I dial a number, I hear a few clicks and then the dial tone comes back. If I try to dial ***6 or ***1 I get the same clicks and then dial tone.

Is the left-most LED on the OBi110 turning red when you hear the click followed by a new dialtone?

If so, the OBi is spontaneously rebooting.  You may have to reset the unit to factory defaults and restore a backup file or reconfigure it from scratch.

[frankb]

Yes, the left-most LED is turning red when i hear the click/dial tone.
I'll try to restore factory defaults and reconfigure it.

[mvg1]

I am unable to make or receive calls. Sp1 shows backing off. When I try to make a call male voice says "There is No service available to complete your call"

I have the latest firmware on my device and still the issue.

[frankb]

I can not receive incoming calls, and can not making any calls with my obi110/google voice. When I dial a number, I hear a few clicks and then the dial tone comes back. If I try to dial ***6 or ***1 I get the same clicks and then dial tone.

Is the left-most LED on the OBi110 turning red when you hear the click followed by a new dialtone?

If so, the OBi is spontaneously rebooting.  You may have to reset the unit to factory defaults and restore a backup file or reconfigure it from scratch.

I did a factory restore, and then re-added google voice. Google voice just keeps saying "Service Not Configured".
I still have the same problem with "the left-most LED is turning red when i hear the click/dial tone".
Do i also have to delete the device on my obitalk page?

[RonR]

I did a factory restore, and then re-added google voice. Google voice just keeps saying "Service Not Configured".
I still have the same problem with "the left-most LED is turning red when i hear the click/dial tone".
Do i also have to delete the device on my obitalk page?

"Service Not Configured" often means the passwords are missing (assuming everything else look correct).

Deleting and re-adding the device from the OBiTALK Web Portal is worth a try.

If all else fails, delete it from the OBiTALK Web Portal and DON'T re-add it.  Then log into the OBi directly, reset it factory defaults, and configure it manually:

System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled

Google Voice on SP1:

Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Service Providers -> ITSP Profile A -> General -> DigitMap:

(<1aaa>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|011xx.)

where aaa is your local area code.

Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

[yorktown]

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.

[frankb]

I did a factory restore, and then re-added google voice. Google voice just keeps saying "Service Not Configured".
I still have the same problem with "the left-most LED is turning red when i hear the click/dial tone".
Do i also have to delete the device on my obitalk page?

"Service Not Configured" often means the passwords are missing (assuming everything else look correct).

Deleting and re-adding the device from the OBiTALK Web Portal is worth a try.

If all else fails, delete it from the OBiTALK Web Portal and DON'T re-add it.  Then log into the OBi directly, reset it factory defaults, and configure it manually:

System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled

Google Voice on SP1:

Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Service Providers -> ITSP Profile A -> General -> DigitMap:

(<1aaa>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|011xx.)

where aaa is your local area code.

Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service

How do i log on to the obi110 manually? I need the ip, if i dial ***1 I get the "the left-most LED is turning red when i hear the click/dial tone" (rebooting).

I'm also unable to re-add it to obitalk, because i need to dial **9-222-222-222.

Is my device dying, i've only had it for 2 months.

[RonR]

How do i log on to the obi110 manually? I need the ip, if i dial ***1 I get the "the left-most LED is turning red when i hear the click/dial tone" (rebooting).

I'd delete (and NOT re-add) the OBi from the OBiTALK Web Portal to get it out of the picture.

Then use a paperclip to hold the reset button on the bottom of the unit depressed for at least 30 seconds to ensure the device is at factory defaults.

If the OBi still reboots on dialing ***1, try to determine the OBi's IP address from your router's Device List.

If you can get logged in directly, use System Management -> Device Update -> Reset Configuration to again force factory defaults.

If you still can't dial anything without the unit rebooting when everything is at factory defaults, it sounds like the unit is defective.

[frankb]

I logged into the device, and used "System Management -> Device Update -> Reset Configuration". I still have the reboot on dial. I also tried to manually configure google voice, but it still reboots.

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.

[synchron]

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 

[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]

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 .

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

[A_Friend]

I just want to express some feelings about all the anger being directed at Obihai.

The ability to use XMPP and hence, Google Voice, is a neat little plus of the OBi100, 110, and 202, but it's not the only reason to buy one.  These units are awesome, feature-packed ATAs.  I don't use the portal to configure mine, so maybe I have a different view than some others.  Being able to use two (or more) carriers for one line, cobble up a sophisticated dial plan, implement your own 7-digit dialing, 100 hardware-based speed dials, including SIP URIs,  200 call detail records, hardware-based call forwarding, an automated attendant...  The mind boggles!  When I compare this to my Grandstream ATA, that looks like something from the stone age.

In other words, I'd use one just for SIP.  And, if I don't like the pricing that GV comes up with next year, that's just what I'm going to do.  Right now, it's great for my old landline number that I LNP ported to a SIP provider, with outgoing service via GV, and a dial plan that calls e911 on the right line, international via SIP, translates our city's 311 to its underlying 10-digit number, routes 411 to a free service, and I forget what else I've coded  already.

It's hard to have anything but humorous contempt for the mad people demanding free phone service as part of their product's purchase.  It's a very neat product, well worth the money for those of us who are BUYING and provisioning our own phone service.  The ability to use GV is a neat little parlor trick, and a nice bonus while it lasts, but it's just that.  And as far as yesterday's glitch, you guys should know that there is no tech company on earth that I've ever seen respond faster or more competently to come up with a fix, implement it in new firmware, and get it out the door.  No one!

If OBihai has made one mistake, it's an understandable one considering their unique ability to use GV.  Their advertising should not be going head-to-head with MagicJack.  Yes, I know that's where the market is, but it's just...  wrong.  MagicJack is a doomed product, a Ponzi scheme of sorts.  At some point, either their new sales will cease to be enough to support the cost of the service, which will cease, and those devices become nothing more than interesting mementos, or they'll have to raise the cost of their service to a market rate.

There are dozens of competitors in the SIP marketplace and great deals to be had.  The OBi devices can run any of them.  And new competitors to GV may be emerging in the XMPP universe.  I've seen mention of Live Messenger and a Skype gateway.  With the two SP channels, and extra configurable gateways, the OBi will let you combine the best features and prices of multiple services.

So, quit yer bellyachin'!

[frankb]

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

Are you referring to Lavarock7's problem?

[atbglenn]

I was pulling my hair out yesterday trying to figure out what was wrong with OBi/GV. Glad it wasn't on my end. Just goes to show you, you can't rely on free GV service. I still keep Vonage's $4.99 pay as you go plan as a backup just in case google decides to axe GV..

[Ostracus]

There are dozens of competitors in the SIP marketplace and great deals to be had.  The OBi devices can run any of them.  And new competitors to GV may be emerging in the XMPP universe.  I've seen mention of Live Messenger and a Skype gateway.  With the two SP channels, and extra configurable gateways, the OBi will let you combine the best features and prices of multiple services.

The Obi202 supports a HD codec. IBLC which I believe Skype uses as well. So either, at least the call quality will improve. or Skype will soon be another "parlor trick".

[QBZappy]

http://en.wikipedia.org/wiki/Internet_Low_Bit_Rate_Codec

"iLBC is defined in RFC 3951. It is one of the codecs used by Gizmo5, webRTC, Ekiga, QuteCom, Google Talk, Yahoo! Messenger, Polycom IP Phone and Maemo Recorder (on the Nokia N800/N810) and many others."

This is perhaps to give the OBi more flexibility for future IM support as well.