GV stop working with my OBi110 since Since 5/8/2012 night. I tried different GV accounts with OBi, all get "Backing Off ", Backing Off (0s):TCP connection to 173.194.79.125 failed
nothing changes on my network, just stopped working .
need help please !
I've stopped working since last evening also.
Backing Off (3s):TCP connection to 173.194.68.125 failed
Quote from: jjw1368 on May 09, 2012, 03:49:31 AM
GV stop working with my OBi110 since Since 5/8/2012 night. I tried different GV accounts with OBi, all get "Backing Off "
nothing changes on my network, just stopped working .
Same exact thing has happened to me. Started the evening of May 8 and continues the next morning.
I have tried two Google accounts and resetting the SP1 config numerous times, but only Backing Off appears.
I think everyone is affected by this, since my OBi110 Status shows the same. I also have GV setup on Asterisk and is able to make and receive calls via Google Voice using this setup. Something is definitely wrong with the OBI/GV Interactions.
Edit: I quickly enable the second line on GV Settings. So if my GV number is dialed, the calls will come into my OBi110 on SP2 and my callers will not even aware that my GV number is not working. Also, switch my Phone Primary Line to Trunk group, which tries SP1 (GV) first, then SP2 (Anveo) and then VG3 (CallWithUs). I hope everyone has a backup line for instances like these.
Quote from: jjw1368 on May 09, 2012, 03:49:31 AM
GV stop working with my OBi110 since Since 5/8/2012 night. I tried different GV accounts with OBi, all get "Backing Off ", Backing Off (0s):TCP connection to 173.194.79.125 failed
nothing changes on my network, just stopped working .
need help please !
I also show backing off. I first noticed it around 11 PM EST.
I came here looking for answers, and am encouraged (slightly) that the same thing is effecting others.
same here it happen last night around 11:30 PM I was on the phone at the time.
Quote from: RFord on May 09, 2012, 03:58:54 AM
I think everyone is affected by this, since my OBi110 Status shows the same. I also have GV setup on Asterisk and is able to make and receive calls via Google Voice using this setup. Something is definitely wrong with the OBI/GV Interactions.
Edit: I quickly enable the second line on GV Settings. So if my GV number is dialed, the calls will come into my OBi110 on SP2 and my callers will not even aware that my GV number is not working. Also, switch my Phone Primary Line to Trunk group, which tries SP1 (GV) first, then SP2 (Anveo) and then VG3 (CallWithUs). I hope everyone has a backup line for instances like these.
I've no idea what any of this means, but I tried configuring SP2 and it is also Backing Off.
Ditto here, "Call Back" is displayed even though I don't use Google 2-Step verification. I went through the whole process to set it up and entered in the new password for it into my OBi, but that didn't seem to work either. Call Back still showed up. I've disabled 2-step on my GV account now and re-entered my old PW back into OBi in hopes these guys fix this thing. Just glad to know I'm not the only one.
We have multiple devices. 2 went down with Backing Off. I reactivated the device and reset the GV accounts with Obitalk. Still no good. Both were originally working - I set them up personally and used them
Are you setting up SP2 with GV? If so, you need another VOIP provider for that purpose. In my case I'm using Anveo and I also have CallWithUs (Voice Gate Account) for overseas calls. You should get a free DID from Callcentric and setup that for free incoming and fund the account for outgoing calls.
Quote from: nicmart on May 09, 2012, 04:31:07 AM
Quote from: RFord on May 09, 2012, 03:58:54 AM
I think everyone is affected by this, since my OBi110 Status shows the same. I also have GV setup on Asterisk and is able to make and receive calls via Google Voice using this setup. Something is definitely wrong with the OBI/GV Interactions.
Edit: I quickly enable the second line on GV Settings. So if my GV number is dialed, the calls will come into my OBi110 on SP2 and my callers will not even aware that my GV number is not working. Also, switch my Phone Primary Line to Trunk group, which tries SP1 (GV) first, then SP2 (Anveo) and then VG3 (CallWithUs). I hope everyone has a backup line for instances like these.
I've no idea what any of this means, but I tried configuring SP2 and it is also Backing Off.
GV down here also, glad I found this post, I spent a good amount of time trouble shooting.
I have 4 obi boxes all around the world and non are working anymore.
Same error with TCP connection to 173.194.70.125 failed
Correction - I have 8 boxes - with 6 in the USA. ALL state Backing off now.
I checked each of the GV accounts. They are fine. One is a verified account with Google, so its definitely not them purposefully shutting the numbers. This is an Obihai/Google issue.
I have 30 of obi110 in 25 locations in the usa all say the same thing backing off..
good luck obi ..let the force be with you :)
I just submitted a support ticket. I highly recommend everyone does so it is placed on a high priority as a major bug fix.
http://www.obihai.com/supportTicketForm.php
Same problem here. After 30 + days of trouble free service , suddenly I cannot connect to Google Voice. I made no changes to OBi or Google Voice. The status is " Backing off connection failed" Google Voice still forwards my calls to my cell phone correctly.
Support ticket submitted.
Same here. All three of my OBi-110's are showing "Backing Off (1s):TCP connection to 74.125.130.125 failed" Good thing I have Callcentric configured just in case this very thing ever happened. :o
BTW, Nothing is showing up on Google Apps Status Dashboard.
http://www.google.com/appsstatus
Same thing here, 2 different obi100's on two different internet connections: message "there is no service available to complete your call" when trying to dial out. (using two different google voice accounts) Submitted ticket
Same problem here. Submitted ticket. No GV working. :(
First time I've had a major issue since having Obihai service for about a year.
It occurs to me that there were novel transmission problems in my calls yesterday and the night before. I repeatedly had to reconnect calls because the calling party's voice became inaudible, and the other parties were complaining about poor voice quality. Signs of a system about to fail?
I have same problem. I have submitted support ticket, all please do the same.
Same thing here. Tried the same things as most of the rest of you. Genned new device-specific password. Turned off two-step verification. Checked I could initiate calls from the website using my callcentric account on SP2 as the initiating endpoint. Rebooted EVERYTHING. I'm starting to wonder if it's a DNS issue.
By the way, you might also want to consider posting this on the Google Voice forum. I did, at: http://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/SGrKe9UVyLI (http://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/SGrKe9UVyLI)
http://www.obihai.com/supportTicketForm.php (http://www.obihai.com/supportTicketForm.php)
Quote from: nang on May 09, 2012, 05:35:38 AM
I have same problem. I have submitted support ticket, all please do the same.
I am experiencing the same issue. I tried deleting the entry and adding again but to no avail.
Obihai are aware of this issue and are working on it now.
At this time, there is no need to make any changes to your device's configuration settings.
Same thing is happening to our account. No connection to GV this morning. Plus, all the Obi web pages load very slowly. And, no reply from my service request. Anyone actually hear from Obi yet?
Quote from: lalique on May 09, 2012, 06:45:27 AM
Same thing is happening to our account. No connection to GV this morning. Plus, all the Obi web pages load very slowly. And, no reply from my service request. Anyone actually hear from Obi yet?
Uh, did you try reading the post before you? OBi is aware of the problem and is working on it.
Quote from: OBiSupport on May 09, 2012, 06:18:12 AM
Obihai are aware of this issue and are working on it now.
At this time, there is no need to make any changes to your device's configuration settings.
Thanks for the update!
Please report back when OBI has a fix!
Since GV is working fine (I can forward calls to my cell), clearly this is a GV / OBi problem. And a big one. At about the 12 hour point of having no service, and until I had some issues this morning I had no idea I had issues. Then I came to the forum and saw this.
One would have hoped that OBi was aware of this last night, and they've been working on it since then, with a full team, versus having just started working on it this morning. I don't know which is the case, but hopefully they are 12 hours into the problem at this point and close to a solution.
This is really concerning as far as the reliability of OBi.
I see the OBiTALK portal has been taken down; users tinkering with their GV connections were probably why this site was having problems staying up, as both the portal and this forum are on the same server. (Perhaps use different servers in the future?) However, taking down the portal is keeping me from trying one promising workaround: the Simon Telephonics GV gateway (instructions at https://michigantelephone.wordpress.com/2012/04/15/how-to-use-the-simon-telephonics-google-voice-gateway-with-an-obihai-device-to-provide-caller-id-name-on-incoming-google-voice-calls/ (https://michigantelephone.wordpress.com/2012/04/15/how-to-use-the-simon-telephonics-google-voice-gateway-with-an-obihai-device-to-provide-caller-id-name-on-incoming-google-voice-calls/)).
That gateway had NO problems logging into GV this morning to give me my credentials (which I have saved), so it MIGHT work. However, since I can't get into the OBiTALK portal to redirect my OBi100 to the gateway, it seems the only way I can get around this is to use my OBi100's own web interface (dial ***1 for IP address), disable auto-provisioning (to keep OBiTALK from overriding it for now), and configure it manually. If this is going to be a lengthy outage (for both OBiTALK and the OBi/GV interface), how can I manually reconfigure the OBi100 to use the Simon GV gateway instead of GV directly?
Also, the boilerplate graphic on the OBiTALK "site down" page says "OBiTALK Calls are On-Line". Though that might be true of non-GV users, it is certainly *NOT* true for GV users. Is there any way to at least modify that page to tell the WHOLE truth?
The main page of the Obi site now says " OBITALK portal is down for maintenance and will be back on-line shortly. OBITALK calls are ON-LINE"
I hope this isn't a case where GV blocked OBi once they realized how their service was being used. One assumes that OBi and Google have a close relationship, that Google is well aware of the OBi device and its usage and that they work cooperatively together.
A firmware update was JUST posted minutes ago. I'm going to try it.
Same problem here..I am getting a 'there is no service available to complete this call' message since this morning. Glad I found this forum thread, I was going nuts trying to figure out what is going on. I cannot connect to the obi portal since its down for maintenance!!
The apparent silence from Obihai regarding this problem is what concerns me the most. They could at least make periodic status announcements, considering their GV link has already been down since last night.
New firmware (2711) has been posted AND it resolves the issue.
Go here: http://www.obitalk.com/forum/index.php?topic=9.0
download the file, and apply it per OBi's update instructions.
Or, you can pick up the attached phone and dial ***6 to update your OBi
FW update 2711 fixed Google Voice on all of my OBi110 units.
Quote from: Rick on May 09, 2012, 08:11:28 AM
New firmware (2711) has been posted AND it resolves the issue.
Go here: http://www.obitalk.com/forum/index.php?topic=9.0
download the file, and apply it per OBi's update instructions.
Or, you can pick up the attached phone and dial ***6 to update your OBi
+1. Used ***6 method to update firmware; calls now go thru both ways. Thanks!
May still try the Simon gateway later; I'd been considering it to add incoming Caller ID Name data. And forwarding GV to my cellphone worked throughout the outage, so that's important in case this ever happens again.
There is a new software update available that should fix the issue.
Please dial ***6 from the attached phone to update your OBi.
There is no need to make any changes to your device's configuration settings.
Is Google starting to play the cat & mouse game with the OBI users like AOL and Yahoo used to do at some point with 3rd party IM clients (Trillian for example) that reverse engineered their chat protocols?
Given that it took a firmware fix, that implies to me that GoogleVoice made a change that blocked OBi. That tells me that OBi is not working closely with Google on an ongoing basis. That really concerns me, as a person that bought this device SOLELY to eliminate my landline and use GV. OBi needs to:
1) Explain what happened and why it took 12 hours to fix.
2) Explain their ongoing relationship with GV and reassure their user base that going forward this should not happen again.
Or, tell us why it has nothing to do with changes that GV made.
Just spoke to Obihai. All phones will update manually. If not, dial ***6. The main portal site is up and working as well.
Also they implied that Google's change was sudden and they clearly did not expect it. I did state the same concern as the previous post. The only answer I got was a cool "It works now."
Hopefully this stuff doesn't happen again.
That's not an acceptable answer. I hope OBi will reassure us all soon, because if they aren't working with Google hand in hand then it throws their box into the "nice, but I can't rely on it" category.
I can't say if my service stopped during the night of 5/8 but did notice it this morning. Interestingly,I went to the OBITALK portal to try to log in but saw that the portal was temporarily down for "maintenance" and would be open soon. When I finally did log in i saw a icon prompting me that there was a firmware update for my primary number.I clicked and downloaded the firmware and lo and behold was able to place an outgoing call. I have had my device since late 2011 and other than the occasional echo and intermittent dial tone when first starting to place a outgoing call I have had no issues.
I would like to know if the port line indicator is supposed to stay solid green at all times or just when making/receiving a call.
Hope this helps.
Quote from: wpollock on May 09, 2012, 02:02:23 PM
I would like to know if the port line indicator is supposed to stay solid green at all times or just when making/receiving a call.
The LINE Port indicator should be solid when the LINE Port is not in use but is available/ready for use. When it's in use, the LINE Port indicator should blink slowly. When there is an incoming call, the LINE Port indicator should blink rapidly.
It'll be a bummer if Google moves to block Obi. But I've gotten my money back many times over so I won't cry too much.
What's everyone expecting? That Google should give them free phone service for the rest of their lives, no matter how they use it?
Some of these responses just crack me up - it's as though some people believe there is an obligation by either Google and/or Obihai to provide them with free phone service forever. What planet are some of you from???
I'll just port my number to Callcentric and still be ahead.
Quote from: Rick on May 09, 2012, 01:34:48 PM
That's not an acceptable answer. I hope OBi will reassure us all soon, because if they aren't working with Google hand in hand then it throws their box into the "nice, but I can't rely on it" category.
Isn't all of VoIP like that?
I other individual with a warped sense of entitlement. Only a moron would believe the nonsense you are talking spewing below. Google Voice can disappear at any time as Google see fits. If you brought the device thinking you will enjoy free GV calling into infinitum, only shows how foolish you are. Google and/or OBiHAI owes you nothing and OBiHAI did not say anywhere that the device will forever offer free GV calling. You better return the device if that is your expectation. Enjoy while it last, because Google can stop GV at anytime or make it a totally paid service. Your asinine comments just makes me want to puke. BTW, where you the guy who wanted to switch over your entire Church Organization to GV/OBi?
Quote from: Rick on May 09, 2012, 12:29:43 PM
Given that it took a firmware fix, that implies to me that GoogleVoice made a change that blocked OBi. That tells me that OBi is not working closely with Google on an ongoing basis. That really concerns me, as a person that bought this device SOLELY to eliminate my landline and use GV. OBi needs to:
1) Explain what happened and why it took 12 hours to fix.
2) Explain their ongoing relationship with GV and reassure their user base that going forward this should not happen again.
Or, tell us why it has nothing to do with changes that GV made.
Well said!! GV is only a small part of this great ATA, something a few individuals fail to realize.
Quote from: SeaObi on May 09, 2012, 02:52:13 PM
It'll be a bummer if Google moves to block Obi. But I've gotten my money back many times over so I won't cry too much.
What's everyone expecting? That Google should give them free phone service for the rest of their lives, no matter how they use it?
Some of these responses just crack me up - it's as though some people believe there is an obligation by either Google and/or Obihai to provide them with free phone service forever. What planet are some of you from???
I'll just port my number to Callcentric and still be ahead.
Anyone still having an issue after updated the firmware? Still getting the error when I dial a number.
Of course I love to use GV for free, but I'm ready to pay IF their rates are competitive with other VOIP service like voip.ms and callcentric (I already have accounts with those guys for international, 411/911, and as a backup for times like this morning when GV/Obi was busted.)
Obihai should start providing affordable VOIP service. Or partner with some VOIP provider for re-branded service. They understand that people who buy the OBi devices are cheap and want to keep costs down.
Quote from: Boston on May 09, 2012, 03:30:49 PM
Anyone still having an issue after updated the firmware? Still getting the error when I dial a number.
Yeah, mine was still broke. I went in to check my unit, it was already on the newer firmware (They must have done a force push out) and my profile for GV was completely gone. I had to rerun the Device Configuration from the Portal.
ronio
RFord:
Your comments are unacceptable on this forum. Attacking people when you differ in opinions isn't ok, nor is use of words you used.
OBi is not a VoIP provider. OBi produces a hardware box that they say works with GV. While the free status of Google Voice in 2012 (which Google has committed to, so no, they won't just start charging) is only guaranteed until 12/31/12, no where does OBi say that there device may not work with GV at all. Not a question of money, it's a question of functionality. In fact, OBi says on their site: Free calls from your home phone with an OBi and Google Voice. The asterisk on the word "calls" explains that the calls are free through 2012. Nothing about the box not working with GV at all, which was the case.
If GV blocked OBi devices permanently, OBi would likely have major financial issues as many/most owners would seek to return the device, under warranty, for not performing as advertised. So yes, I have an expectation that OBi has some relationship with GV that allows them to stay abreast of changes and keep functioning. This 12 hour outage has me concerned.
What firmware update? I woke up with green status off and service not available on SP1. 6 hours later when I came home light was back on and Sp1 worked fine. I dialed ***6 and got 'firmware unavailable'.
So did the fw get auto updated unattended? Or is this working just due to Obihai's end? How do I find out what my current firmware is since it doesn't say in Obitalk?
Thanks, Synchron 8)
Quote from: Ronio on May 09, 2012, 04:19:18 PM
Quote from: Boston on May 09, 2012, 03:30:49 PM
Anyone still having an issue after updated the firmware? Still getting the error when I dial a number.
Yeah, mine was still broke. I went in to check my unit, it was already on the newer firmware (They must have done a force push out) and my profile for GV was completely gone. I had to rerun the Device Configuration from the Portal.
ronio
Mind is still broke. When I tried to use ***6, it replies "No update avaialble". When I try download the firmware maually, the IP address that I obtained through the phone won't get me to the log in page. I am still dead in the water.
Quote from: synchron on May 09, 2012, 04:49:22 PM
What firmware update? I woke up with green status off and service not available on SP1. 6 hours later when I came home light was back on and Sp1 worked fine. I dialed ***6 and got 'firmware unavailable'.
So did the fw get auto updated unattended? Or is this working just due to Obihai's end? How do I find out what my current firmware is since it doesn't say in Obitalk?
Thanks, Synchron 8)
Yes, it seems that OBi has the power to push out firmware updates to the OBi boxes. They pushed it out to everybody (even those that had explicitly turned firmware updates off). This has a lot of people concerned and I think that OBi just lost a bunch of customers due to the now obvious mandatory tie to OBi servers....
They told me on the phone that the upgrade was a 'push' and done by itself.
Also....if Google shut down GV (They do shut businesses with a shock on occassion) that only means one less VOIP provider. OBI is multifunctional with different VOIP providers. So I am not sure they would have to honor the returns. The device would work, and GV is not Obihai, the decision by Google to shut GV would be beyond Obihai's control.
The larger concern here is Obihai can't afford to get caught like this again. They need to make sure their developers are in constant communication with GV devs so they can expect, plan and adapt quickly to major coding changes like last night.
Quote from: Ronio on May 09, 2012, 04:19:18 PM
Quote from: Boston on May 09, 2012, 03:30:49 PM
Anyone still having an issue after updated the firmware? Still getting the error when I dial a number.
Yeah, mine was still broke. I went in to check my unit, it was already on the newer firmware (They must have done a force push out) and my profile for GV was completely gone. I had to rerun the Device Configuration from the Portal.
ronio
Thanks man that worked for me.
Quote from: SeaObi on May 09, 2012, 02:52:13 PM
It'll be a bummer if Google moves to block Obi. But I've gotten my money back many times over so I won't cry too much.
+1 !!
Quote from: SeaObi on May 09, 2012, 02:52:13 PMSome of these responses just crack me up - it's as though some people believe there is an obligation by either Google and/or Obihai to provide them with free phone service forever. What planet are some of you from???
+1 !!
I don't understand the
demanding tone of some of us. I believe Obi is doing the best they can without any input, interaction, or the benefit of advance notice from Google. RonR said he'd bet the farm "there is absolutely no relationship nor any communication between Obihai and Google -- and never has been." While he doesn't strike me as a Farmer, I think he'll get to keep his farm. :D
If Obihai gradually improves their equipment, functionality, and customer service, eventually they might be that big company that either gets to work directly with Google or that gets bought by Google! :)
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.
Quote from: frankb on May 09, 2012, 06:19:07 PM
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.
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.
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.
Quote from: RonR on May 09, 2012, 06:23:34 PM
Quote from: frankb on May 09, 2012, 06:19:07 PM
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?
Quote from: frankb on May 09, 2012, 07:18:38 PM
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
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.
Quote from: RonR on May 09, 2012, 07:33:06 PM
Quote from: frankb on May 09, 2012, 07:18:38 PM
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.
Quote from: frankb on May 09, 2012, 07:46:54 PM
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.
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.
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)
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.
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.
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.
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
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'!
Quote from: Rikin on May 10, 2012, 03:37:06 AM
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?
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..
Quote from: A_Friend on May 10, 2012, 04:48:23 AM
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".
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.
For HD you will need an actual HD phone too and of course the other party needs to be set up for HD otherwise it's pretty useless. HD is probably not that useful at this point.
All my Obi 110 devices have been setup for months now and previously worked good.
One (1) OBi110 is located in Pennsylvania USA is connected through Comcast and Echo test is working. I can call and receive calls from another OBi110
I have dialtone but receive "No Service Available" error
I have tried to upgrade software with *** 6 but says no upgrade available.
I have three (3) other OBi110 boxes in Europe and they are working OK and we have successfully upgraded firmware.
So what to do with box that still is NOT working?
@Wickabell - Please contact Obihai support.
They will help you troubleshoot & get your device working.
Support Request Form: Click Here (http://www.obihai.com/supportTicketForm.php)
Email: support@obihai.com
Phone: +1.408.634.5904
Sounds like automatically pushing these firmware updates is not such a good idea as they can brick some units. Obihai can't make sure that the user is not fiddling with the settings at the time or just by pure coincidence unplugging the power, or suffering a power outage, etc.
A much better approach would be to notify the users (via email perhaps) that a required firmware update is available and let the user decide when to apply it. The notification should be clear about what has changed and why, in this case it should make it very clear that "GV service will not work until he new firmware is installed".
I am glad yesterday one even outage event was helped out by my second line at Callcentric + ipkall number.
The GV was down in the morning, but the 2nd line with Callcentric free account worked and we were not affected as much as last time.
I don't blame Obihai too much on this as this events means that OBihai is good for a techie like me, but not ready for mass media. Obihai is less reliable than vonage or landline cord, but similar to better than cell phone.
Quote from: dhobi on May 10, 2012, 10:21:30 AM
Sounds like automatically pushing these firmware updates is not such a good idea as they can brick some units. Obihai can't make sure that the user is not fiddling with the settings at the time or just by pure coincidence unplugging the power, or suffering a power outage, etc.
A much better approach would be to notify the users (via email perhaps) that a required firmware update is available and let the user decide when to apply it. The notification should be clear about what has changed and why, in this case it should make it very clear that "GV service will not work until he new firmware is installed".
Mine seemed to get bricked by just being on the phone at the moment.
Quote from: frankb on May 10, 2012, 01:35:49 PM
Mine seemed to get bricked by just being on the phone at the moment.
Ha! There you have it. If that bricks it then it's really a poor plan for Obihai to push firmware updates. If there's a required firmware update just play a message when the user picks up the phone, send an email, etc. there are many ways you can let the user confirm the action.
Does anybody know why this FW update was needed and jusified to be AUTOMATICALLY pushed?
I have my OBI devices for quite a while since 2011 and never needed to update the FW and it worked fine until now.
2 obi110 devices I have oversea failed to update as a result of this push and now cannot be used unless I fly over to fix them .
I'm certainly not defending the automatic push of the fw. Just thinking out loud. I wonder if Obihai got blow back from google because of all these Obi devices trying to register to google voice and failing for whatever reason (backing off). The failure was probably a result of something google changed, but nevertheless the devices started failing to register, perhaps causing stress on google voice servers. Result: Slam the fix in to appease google. This is just speculation. I haven't read all the posts, so if someone else has mentioned this possible scenario, pardon.
It's really going to get interesting if and when google decides to monetize their investment in google voice and domestic calls are no longer free. This forum is more entertaining than most TV on my overpriced cable. LOL
Quote from: infin8loop on May 10, 2012, 06:32:22 PM
This forum is more entertaining than most TV on my overpriced cable. LOL
Yeah, we need a ObiTV box for free cable.
@goodobi, @frankb
Please contact Obihai customer service.
We can help you troubleshoot the issues associated with your units.
Support Request Form: Click Here (http://www.obihai.com/supportTicketForm.php)
Email: support@obihai.com
Phone: +1.408.634.5904
Quote from: dhobi on May 10, 2012, 06:35:00 PM
Quote from: infin8loop on May 10, 2012, 06:32:22 PM
This forum is more entertaining than most TV on my overpriced cable. LOL
Yeah, we need a ObiTV box for free cable.
Roku. ;D
Like almost all of you I had issues with my OBI110 today. Can't quite remember if it was yesterday or day before that it was working just fine. I was not able to get the OBI attendant when I tried to dial from SIP client on my PC which had the OBI110 set as gateway. Upon checking OBITalk Web, both SP's were registered and working fine and OBI110 was showing as offline. When calling from attached phone I got the same message as posted by mvg1...
Quote from: mvg1 on May 09, 2012, 06:47:26 PM
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.
I also noticed the update firmware indicator next to my OBI device entry was gone. Can't quite remember if I had initiated the update, so decided to manually upload the latest firmware via the fw file thinking the pushed fw may have caused issues. This did not help either.. Removed the OBI110 from my OBI account and added it back, added both SP lines back and both connected/registered but then from OBI110's web interface I noticed the OBITalk Service Status (system status) was showing "Backing Off". I was now able to make calls from my GV account however from OBI110, but not using my SIP Client.
MY FIX (if this helps you): With all pieces mostly working and having removed and re-added the unit with my OBITalk account, I decided to remove it's gateway reference for the OBIApp device. As soon as I had done that, the OBI110 showed up as online on my OBITalk account. Tried to access OBI Attendant and confirmed it worked via the phone and when I added the OBI as a gateway again and dialing from OBIApp.
No I will have to monitor if when the fw is updated, I may need to remove any gateway reference to my OBI before rebooting it and/or letting it register with the new fw.
Quote from: frankb on May 10, 2012, 05:27:54 AM
Quote from: Rikin on May 10, 2012, 03:37:06 AM
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?
I'm referring to:
"Backing Off ", Backing Off (0s):TCP connection to 173.194.79.125 failed