Obi box just stopped working sometime yesterday or today, and when I logged into the site there was a message about needing to change my Obi Google setup to use the same password I use with Google Voice. I'm not understanding this. I'm logged into Google Voice right now, so obviously the password is correct, and the email is definitely the same, and there's no indication from Google that there's anything wrong. But when I try to set up Google Voice on my dashboard here, I keep getting a message that the device can't be confirmed. Do I need to just do a factory reset on it? TIA
Read and follow these instructions completely:
http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460 (http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460)
Quote from: SteveInWA on May 09, 2016, 04:39:25 PM
Read and follow these instructions completely:
http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460 (http://www.obitalk.com/forum/index.php?topic=8560.msg56460#msg56460)
Thanks for the reply. I did go over the steps there but things are still not working. However, I did notice this time when I went to my dashboard page a big notice about an important update being available that's necessary to continue using GV, but it said I have to pay for another year of support to get it...? Sound right? The latest firmware for the 110 on the Latest Firmware page is dated Aug 2014, which I definitely have, and when I pressed ***6 on the phone the automated message said there was no further updates available. So I guess let me search around and see how much I have to pay out to ransom the device. :-\
Quote from: imno007 on May 09, 2016, 05:14:17 PM
the Latest Firmware page is dated Aug 2014, which I definitely have,
If that was the case you wouldn't get prompted to update your firmware. Here is the latest version:
http://fw.obihai.com/OBi110-1-3-0-2872.fw (http://fw.obihai.com/OBi110-1-3-0-2872.fw)
Download and install manually. Then reconfigure your GV configuration.
Either your reading comprehension skills suck, and/or you were too lazy to search through the forum. The very first thing I said in my linked set of instructions was:
Quote
Note: If you haven't upgraded the firmware on your OBi device in the past year or longer, then you must upgrade it now, so that your device includes support for Google's approved authentication protocol. You can download the latest firmware for free, regardless of the age of your device, here in the forum's firmware section.
The firmware is here: http://fw.obihai.com/OBi-latest.fw (http://fw.obihai.com/OBi-latest.fw)
Simply download it, then log into your OBi's local web page to upload and install it. Dial ***1 on your OBi-attached telephone keypad to hear your device's IP address, then enter that IP address in your web browser, and go to System Management --> Device Update-->Firmware Update to install the current firmware.
Quote from: SteveInWA on May 09, 2016, 05:29:51 PM
Either your reading comprehension skills suck, and/or you were too lazy to search through the forum. The very first thing I said in my linked set of instructions was:
Quote
Note: If you haven't upgraded the firmware on your OBi device in the past year or longer, then you must upgrade it now, so that your device includes support for Google's approved authentication protocol. You can download the latest firmware for free, regardless of the age of your device, here in the forum's firmware section.
The firmware is here: http://fw.obihai.com/OBi-latest.fw (http://fw.obihai.com/OBi-latest.fw)
Simply download it, then log into your OBi's local web page to upload and install it. Dial ***1 on your OBi-attached telephone keypad to hear your device's IP address, then enter that IP address in your web browser, and go to System Management --> Device Update-->Firmware Update to install the current firmware.
My reading comprehension skills are fine. I assumed, though, that you were linking to the latest firmware shown on the Latest Firmware updates page, which looked to me to be from August 2014. Seems like a reasonable assumption to me. If the latest update really were from August of 2014, why would I have wanted to install it? In retrospect, I can see now that the latest date was either just never updated for whatever reason, or maybe what I was seeing was simply the last
edit date for the post rather than the actual date of the latest firmware. Whatever. Anyway, thanks for the update, if not the attitude.
Quote from: Taoman on May 09, 2016, 05:27:32 PM
Quote from: imno007 on May 09, 2016, 05:14:17 PM
the Latest Firmware page is dated Aug 2014, which I definitely have,
If that was the case you wouldn't get prompted to update your firmware. Here is the latest version:
http://fw.obihai.com/OBi110-1-3-0-2872.fw (http://fw.obihai.com/OBi110-1-3-0-2872.fw)
Download and install manually. Then reconfigure your GV configuration.
Read my last post above. Also, I've had this device for more a few years now and this is the first time it hasn't updated automatically for me, so yeah, it just wasn't something that seemed likely to me at the time: that I needed to do a manual update. And unfortunately it also happened to coincide with some other major internet issues I was having, (just got a new modem 2 days ago to fix it), so firmware just didn't seem the likely culprit at first. My mistake, obviously.
And after all that....
QuotePrevious version identical to the update. Firmware not modified.
Well then, you can simply ignore that ominous-sounding advertising message if you don't want to buy a year of telephone support. As long as you are now at the current firmware level, and you are starting with a factory-reset OBi, and you follow the instructions, you'll have a "happy ending".
Okay, got it working again. I'm still not sure why it stopped working, since there never was a problem with my GV password, I'd never changed it, and I obviously didn't have to do a firmware update, but all's well that ends well. I shut down the PC, reset my modem, reset the OBi, then used another browser to do the update. Just mentioning all of this for the record, but I'm pretty sure the problem was with the browser. I have Ghostery installed on FF and I think it was blocking some necessary script, because the GV confirmation step was appearing as a separate page, not as a popup. And yes, I had read that it was a popup, I just wasn't clear on that it had to be a popup. Heh, it was an old post. Anyway, when I switched to Chrome (no Ghostery or other addon's), it was a popup and I got the confirmation.
Sorry to any staff if it seemed like I was jumping to conclusions on the whole have-to-pay-to-update thing, but in my defense I did get that big yellow popup saying there was some very important update I needed - and there obviously wasn't a new upgrade. I'm guessing it was some just some old,outdated message making a reappearance.
Quote from: SteveInWA on May 09, 2016, 07:03:26 PM
Well then, you can simply ignore that ominous-sounding advertising message if you don't want to buy a year of telephone support. As long as you are now at the current firmware level, and you are starting with a factory-reset OBi, and you follow the instructions, you'll have a "happy ending".
Yep, see my last message above. Thanks
There's been a lot of grousing here and there about the message regarding the fee. It's essentially an advertisement, inviting you to pay for another year of technical support, but it's worded to sound like it's mandatory, which it isn't.
@imno007 : can you please share how you finally got it to work?
I have done all of those steps you mentioned and still am stuck on the same page even after trying on multiple different machines and browsers.
On clicking "Google Voice Setup" button in the Obitalk portal, shows a list of approved providers and then clicking on Google Voice just takes me back to the previous page.
@SteveInWA: I did the device reset and followed the instructions in the link you gave to your tutorial steps - my firmware was already at the same version. After factory reset of Obi110 and then adding back to portal, I am trying to setup GV but the result is same. Clicking on Google Voice Setup brings me back to the same portal page.
Appreciate your help - Thanks!
See: http://www.obitalk.com/forum/index.php?topic=11384.0 (http://www.obitalk.com/forum/index.php?topic=11384.0)
@SteveInWA : Hats off to you for the quick and detailed replies!
Yes, that's exactly what's happening to my Obi 110 as well.
Obi to Obi calls are working fine though - will watch that thread for your replies.
Thanks!
This is a solution for the OBI 100 device: http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954 (http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954)
Thanks @yorktown - that worked perfectly!
Quote from: yorktown on May 18, 2016, 10:00:18 PM
This is a solution for the OBI 100 device: http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954 (http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954)
Thank you sir, came home to no GV today, and your link solved it. I didn't have to delete and re-add devices. It just started working.
OK, having followed this thread, I have made sure I have the latest firmware on my Obi110, but it still refuses to login to Google Voice. Before the updated firmware, it would fail and say "backing off" in the status page. Now, after the firmware update, it says "service not configured" in the SP1 Service Status on the portal's home page. However, when I check the Google Voice login credentials under the SP1 service profile, I see the proper Google email address and password entered.
So, why am I getting a message that the service is not configured, and what do I need to do to rectify this?
Thanks.
Quote from: sirwatkyn on June 24, 2016, 05:47:32 AM
OK, having followed this thread, I have made sure I have the latest firmware on my Obi110, but it still refuses to login to Google Voice. Before the updated firmware, it would fail and say "backing off" in the status page. Now, after the firmware update, it says "service not configured" in the SP1 Service Status on the portal's home page. However, when I check the Google Voice login credentials under the SP1 service profile, I see the proper Google email address and password entered.
So, why am I getting a message that the service is not configured, and what do I need to do to rectify this?
Thanks.
Read and follow the full instructions: http://www.obitalk.com/forum/index.php?topic=11384.0 (http://www.obitalk.com/forum/index.php?topic=11384.0)
Steve, thanks for reply and link.
I have to use ObiTalk to reset my Google credentials, rather than doing this on the device's home page? If I use ObiTalk, won't it also reset a lot of other custom settings from the configuration home page? I always heard that ObiTalk overwrites device settings. I have custom ring settings, etc., that I don't wihs to lose.
Thanks again.
Yes, you must use the OBiTALK portal to configure an OBi to use Google Voice.
You have two choices:
1) Convert over to managing your device from the portal, which will overwrite the local configuration, and you will need to manually update your custom settings, or
2) Backup your local device settings on the local web page interface. Then attach the device to the portal, configure Google Voice, and then remove it from the portal and restore your local settings.
Steve:
OK, I remain flummoxed.
I tried to go to ObiTalk page to provision Google Voice, but wind up in the mentioned circular loop, warning me that my firmware may be out of date, even though I have updated to the latest, as per your link. ObiTalk shows neither my Google Voice (SP1) as connected nor does it have any information on my VOIP.MS (SP2) account, which is connected and running properly.
What steps are necessary to resolve this now? I can't understand what could have happened to make Google Voice suddenly inaccessible, after it's worked perfectly previously. I assume that it must be something on the Google side, as there were no changes to my Obi. I had had "insecure" logins turned on in my Google account for this number, and previously everything worked just fine.
Now, I've gone from connected, to "backing off," to "not configured" after the last firmware update.
Please excuse if this issue is redundant, but I would like to resolve this as quickly as possible.
Thanks again.
Quote from: sirwatkyn on June 24, 2016, 08:53:16 AM
Steve:
OK, I remain flummoxed.
I tried to go to ObiTalk page to provision Google Voice, but wind up in the mentioned circular loop, warning me that my firmware may be out of date, even though I have updated to the latest, as per your link. ObiTalk shows neither my Google Voice (SP1) as connected nor does it have any information on my VOIP.MS (SP2) account, which is connected and running properly.
What steps are necessary to resolve this now? I can't understand what could have happened to make Google Voice suddenly inaccessible, after it's worked perfectly previously. I assume that it must be something on the Google side, as there were no changes to my Obi. I had had "insecure" logins turned on in my Google account for this number, and previously everything worked just fine.
Now, I've gone from connected, to "backing off," to "not configured" after the last firmware update.
Please excuse if this issue is redundant, but I would like to resolve this as quickly as possible.
Thanks again.
I don't know what you've done wrong, but deleting the device off of the OBiTALK portal, factory-resetting it, and then following the **5 procedure to add it back would be the best way go get back up and running. It's time to bite the bullet and clean up whatever configuration issues are causing the problem.
Once again, read and follow the instructions, including the complete instructions to configure Google Voice at the bottom of this linked post: http://www.obitalk.com/forum/index.php?topic=11384.0 (http://www.obitalk.com/forum/index.php?topic=11384.0)
Quote from: SteveInWA on June 24, 2016, 07:38:45 AM
Yes, you must use the OBiTALK portal to configure an OBi to use Google Voice.
You have two choices:
1) Convert over to managing your device from the portal, which will overwrite the local configuration, and you will need to manually update your custom settings, or
2) Backup your local device settings on the local web page interface. Then attach the device to the portal, configure Google Voice, and then remove it from the portal and restore your local settings.
There is a third option which is a variation on the first of those. Before changing to permanently using the portal's Expert mode you can backup your settings to a file and import that settings file into the Expert mode.
OK, here's the latest:
I have factory reset the Obi110. I have deleted and added again the device to the ObiTalk portal. The ObiTalk portal can configure my VOIP.MS account, no problem. BUT, it still refuses to add my Googe account, instead constantly returning with the warning that my device or software may be out of date. Yet, this is after flashing the latest firmware, as provided in your link (http://fw.obihai.com/OBi110-1-3-0-2872.fw). I'm assuming this is the correct firmware?
In any case, I can't imagine what else to do, as the unit has been reset from scratch and re-added to ObiTalk. Since the VOIP.MS account works perfectly, I'm assuming I have no hardware problem.
If you have another good idea to try, I'm happy to hear it.
P.S. Would it be of any use to go back to the Google security settings and re-enable using "secure" settings, rather than the option for older "insecure" devices?
Quote from: sirwatkyn on June 24, 2016, 10:07:28 AM
OK, here's the latest:
I have factory reset the Obi110. I have deleted and added again the device to the ObiTalk portal. The ObiTalk portal can configure my VOIP.MS account, no problem. BUT, it still refuses to add my Googe account, instead constantly returning with the warning that my device or software may be out of date. Yet, this is after flashing the latest firmware, as provided in your link (http://fw.obihai.com/OBi110-1-3-0-2872.fw). I'm assuming this is the correct firmware?
In any case, I can't imagine what else to do, as the unit has been reset from scratch and re-added to ObiTalk. Since the VOIP.MS account works perfectly, I'm assuming I have no hardware problem.
If you have another good idea to try, I'm happy to hear it.
P.S. Would it be of any use to go back to the Google security settings and re-enable using "secure" settings, rather than the option for older "insecure" devices?
By now, there are a bazillion different threads about this issue, and unfortunatelyh, you read an old, and now-out-of-date link. The firmware build you need is 2886. If you followed my instructions, which I linked in my last post, you would have updated to the "latest" build, which is 2886.
http://fw.obihai.com/OBi-latest.fw (http://fw.obihai.com/OBi-latest.fw)
Thanks for that updated firmware link.
Well, now, progress to report, but a new problem. Google has been properly provisioned and is working perfectly on SP1, but, now, after the firmware update, my VOIP.MS account refuses to register correctly, and ObiTalk reports: "Failure: 403 Forbidden." I have checked the login credentials and passord, and they're correct, and I have chosen several of the different server options listed by Obitalk for this provider, but none register correctly and all return the above warning.
Any idea on what's wrong now and how I should proceed?
Many thanks. I really appreciate your help and patience.
That error message most likely means that you didn't enter the correct SIP user name and password. These may be different than a user name and password to access your voip.ms account portal page. I don't use voip.ms, so one of the other folks here might be able to answer that.
Meanwhile, you ought to be able to log into your voip.ms account and look at your SIP user name and change the password, and then use those values.
Steve:
Many thanks. Now successful all around.
It turned out that the problem was that VOIP.MS had updated their password requirement to 8 digits from 6, but would accept logins from existing devices. So it worked until the Obi firmware was updated and ObiTalk tried to reprovision the system using the old 6-digit password. Once I established a new 8-digit password, everything worked perfectly.
Thanks again.
Grrrreat! I'm glad you got it all sorted out.