Dashboard just updated my OBi110 firmware.
Hardware Version 3.4
Software Version 1.3.0 (Build: 2872)
Seems to work fine...
:)
My 2 OBi110's (HW ver 3.4) are still on 1.3.0.2868 and I was not prompted to update the firmware.
Quote from: LeoKing on August 24, 2014, 03:08:21 PM
My 2 OBi110's (HW ver 3.4) are still on 1.3.0.2868 and I was not prompted to update the firmware.
If you try to activate a new SP specifying GV, it will force an update (presumably so that it can use the new authentication framework).
The latest one available for general download seems to be build 2824. Any idea what the URL is for the newer build(s)?
Quote from: goldie26 on September 07, 2014, 02:28:54 PM
http://fw.obihai.com/OBi-1-3-0-2872.fw (http://fw.obihai.com/OBi-1-3-0-2872.fw)
Thanks, but that link gives me a 404, page not found.
I suspect that Obihai is having server problems this weekend. Try again in a couple of days. Or, press ***6 on your attached telephone to check for an update.
Quote from: Huib on September 07, 2014, 02:49:53 PM
Thanks, but that link gives me a 404, page not found.
This should work better for you:
http://fw.obihai.com/OBi110-1-3-0-2872.fw (http://fw.obihai.com/OBi110-1-3-0-2872.fw)
Quote from: Taoman on September 07, 2014, 03:47:27 PM
This should work better for you:
http://fw.obihai.com/OBi110-1-3-0-2872.fw (http://fw.obihai.com/OBi110-1-3-0-2872.fw)
Yup, it sure does :) Thanks
I just updated to Ver 1.3.0 (Build 2872) posted in this thread and now the GV service I had configured and working on SP1 shows "Service Not Configured" although all the parameters seem unchanged.
The voip.ms service I had configured on SP2 seems unaffected and is still working.
I tried to go back to the older firmware I was running and got "Firmware downgrading is prohibited ". I hate when companies do that but rather than vent, I'd like to get things working again.
Any solutions/suggestions deeply appreciated.
Hi, how can I see my current firmware level? Thanks much.
Quote from: Cajun1 on September 11, 2014, 04:18:56 PM
Hi, how can I see my current firmware level? Thanks much.
There are probably other ways, but can either use a web browser, and connect to your Obi direction (http://<ip_address>) which shows you the system status, and a bit down the page, the firmware level, or you can use expert mode from the Obitalk and from the left panel, select status/system_status) which shows you the same info (sometimes I have found you have to refresh the system status a few times due to timeouts).
anybody knows the change log for this? I never solved the random caller ID detection problems I am having here and I hope that a fix may improve the behavior
I believe that to enable the new Google format you must:
1. Delete your device from the portal
2. Do a paper clip reset on your Obi
3. Add your device back at the portal
4. Select Google as the service provider for sp1. Haven't been through the procedure yet so can't give details.
5. Add your service provider back on SP2. You will need your password info
The whole process shouldn't take more than 30 minutes.
Quote from: antani1971 on September 12, 2014, 12:03:20 AM
anybody knows the change log for this? I never solved the random caller ID detection problems I am having here and I hope that a fix may improve the behavior
Obi has been a bit lax regarding changelogs for their recent firmwares (i.e. not providing them at all). Even when provided, there are examples of a single line that says "Various bug fixes (and enhancements)", which has not been helpful to know if your particular issue has been addressed. This (lack of detailed changelog) is not unique to Obi (unfortunately). To do better would require assigning an engineer to sanitize the details of the bugs fixed in a way meaningful to those not steeped in the internal codes (and hide details of specific customers). And while I would like better changelogs (and I would also like a list of bugs that are known, and will eventually be addressed), I understand that the engineers priority would be to work on fixing bugs (and creating enhancements) rather than satisfying my curiosity.
I was able to reconfigure Google Voice on my OBi202, OBi110 and OBi100 without deleting my device from OBiTalk and without resetting the OBi devices. After the update to OBiTalk method for provisioning Google Voice, I went into SP2 on each of the devices, when I attempted to update and save changes I was prompted to complete the firmware update. After the firmware update was completed, I was able to update the Google Voice configuration on SP2 using the new method.
The ability to update the Google Voice configuration without deleting my devices from OBiTalk was a much appreciated time saver as I have multiple VoIP service providers on each of the devices. The OBi202 has Vestalink on SP1, Google Voice on SP2, VoIP (for Home #) on SP3 and VoIP (for Home Office) on SP4.
Thanks RFC, for the info to be able to see my IP address.
I have both an obi100 and an obi200 that have google voice as SP1 and callcentric as sp2....I never deleted google voice...when I try to go and edit the settings I get notified I need to do a firmware update...I allow it...time goes by and it notifies me that it failed...rinse lather repeat on the other device....oh and ***6 says no update available on both devices. Way to go obihai!
Quote from: FameWolf on September 13, 2014, 11:10:03 PM
I have both an obi100 and an obi200 that have google voice as SP1 and callcentric as sp2....I never deleted google voice...when I try to go and edit the settings I get notified I need to do a firmware update...I allow it...time goes by and it notifies me that it failed...rinse lather repeat on the other device....oh and ***6 says no update available on both devices. Way to go obihai!
Delete your devices from the OBiTALK portal, then factory-reset them, and add them back to the portal. When you configure Google Voice again, it should download the new firmware successfully.
<edit> I actually just tried this on my ancient, hardware version 2.8 OBi 110. It upgraded to the version before 2872 (sorry, I forgot to write it down). I had to manually update it by downloading the firmware file ( http://fw.obihai.com/OBi110-1-3-0-2872.fw ) and using the local web interface. So, YMMV, but in the end, it can be updated.
Ever since I was forced to upgrade, my Obi 110 v2.8 will not phone home to Obi or work at all. I deleted it from ObiTalk and have hard reset, soft reset, you name it. A tcpdump below shows the only traffic generated by the device...
19.268590 arp who-has 192.168.2.114 tell 192.168.2.114
19.518773 arp who-has 192.168.2.114 tell 192.168.2.114
20.635648 arp who-has 192.168.2.5 tell 192.168.2.114
21.728723 arp who-has 192.168.2.1 tell 192.168.2.114
21.729160 192.168.2.114.10000 -> 54.241.160.4.10000: udp 46
21.730977 192.168.2.114.10000 -> 54.241.160.4.10000: udp 94
22.220542 192.168.2.114.2656 -> 74.122.204.5.123: udp 48
26.838646 arp reply 192.168.2.114 is-at 9c:ad:ef:ff:b:c
Any ideas? Support has been less than helpful.
I saw a post I think on this forum from Obi that gave the steps to load firmware into a bricked Obi. Can you access the admin page(s) using a crossover cable? I would try installing build 2872 that way and see what happens. You may want to look for the post from Obi first, though. Can't remember the exact steps.
*edited* If your power light is flashing red/green go here to follow the instructions & load 2872.
http://www.obihai.com/support/troubleshooting/alt
Hmmmm...so this is a little unfortunate. Apparently, it is now impossible to use an OBi110 with Google Voice without the OBiTalk portal. Sigh....
I suppose, it's impossible unless you happen to know what the portal is doing, and do similar things to the OBi110. I would guess it's something to do with getting an OAuth token then storing it in the unit. Still...this is annoying. I want to be able to do everything to my device locally, and not rely on/disclose anything to another party. Rats. Well, what can you expect for $50 I guess?
BTW...I really think that's what it's doing, getting an OAuth token. Some of you posters were saying it was a "completing the firmware update." Call that what you will, but I call it updating firmware when you change the stored program, and this would SEEM to be merely a configuration change.
OAuth(2) is MORE secure than the old way, and doesn't expose your password over the wire ALL THE TIME.
Yes, you now need to set up Google Voice via ObiTalk. It does NOT get in the way of you doing Expert Config or other changes.
Why are you so opposed to ObiTalk?
When ObiTALK is unavailable (as simple as a routing snafu where Google is accessible but they aren't, or in particular, if Obihai were to go out of business) and I want to change my ATA, what then? Why are Obihai's servers necessary to fetch my token? Why can't the OBi110 fetch it itself? Is Obihai merely passing that token through, or are they storing somewhere?
I'm not questioning the authentication strength of OAuth versus whatever was being used before, I'm questioning why it needs to go through a third party, and all the security implications THAT has. If you trust Obihai to do everything fine every time, that's great. I'm sure that's what the Target, Home Depot, Anthem, etc. folks thought too. Obihai seems to be one link in the chain which shouldn't need to be there.
I would even be semi-happy if Google Voice could be set up, then be able to change the admin password on my device and delete it from ObiTALK. But if you do that, it deconfigures your GV ("Service not configured"), and resets your admin password to the default of "admin". If you don't delete it from ObiTALK, it resets your password to what it thinks it should be and reboots your OBi. That in itself is quite troubling, because that implies they're STORING MY DEVICE'S ADMIN PASSWORD IN PLAINTEXT. Ask ANYONE who programs things which are supposed to be secure, such as password handling routines, and they will explain that NO password should even show up on the page after provisioning, yet it appears on the ObiTALK page after I click on the device name in my dashboard! It's not even obscured by asterisks or anything, so anyone happening to see my monitor can now screw with my OBi110. "Expert config" sucks because it reboots the box after EVERY change; you can't batch up a few (pages of changes) and THEN reboot. I don't want my firmware being updated potentially every day, but once again, if you vary from the Obihai Rx, you're slammed down, your changes are reverted, and your box gets bounced. Even if you change that in "Expert mode" on the Web site, logging directly into the device begs to differ, it says it will still probe every 86400 seconds. ( I don't know what was happening when I looked, but now Disabled/Disabled seems to have been pushed to my device)
I believe(!) you can turn off device provisioning, just not delete it from ObiTalk.
SteveInWa will probably drop by with more info.
I also don't believe that ObiTalk is needed for call routing to/from GoogleVoice.
Quote from: lrosenman on March 05, 2015, 06:22:25 PM
I also don't believe that ObiTalk is needed for call routing to/from GoogleVoice.
I have yet to get anything but "Service not configured" when trying to set up GV outside of the ObiTALK portal. If you have been able to do so, I'm all eyes on how to do that.
SETUP *MUST* be done on the portal, HOWEVER, once setup, you should be able to turn off the provisioning via ObiTalk, and you must not DELETE the Obi from the portal.
Huh....would you look at that? I see different results tonight. I apologize...Disabled for FW update and Disabled for autoprovisioning is now working; last night it didn't seem to be so.
Glad I could help.
Keep in mind:
The OBiTALK portal method of setting up Google Voice was developed specifically to not supply your login credentials to Obihai. So, the argument about the Target and Anthem data theft is moot.
When you use the portal to sign up, it is using Google's OAUTH 2.0 setup routine. If you were paying attention, you would have seen that it opens a new browser window, directly logged into your Google, not OBiTALK, account, where Google asks you, the person signed into your Google account, if you would like to give your device permission to use a service on your Google account. This is a normal, direct, TLS-secured web browser session between your computer's web browser and Google...not Obihai. When you agree, the secure token exchange takes place. Obihai never gets your password, and the only thing that you have done is to grant your OBi device to access a service on your Google account.
By the way, Obihai has leveraged this same system to now support direct import of your Google Contacts to a OBi 10x2 IP phone's address book.
This is a far more secure method of configuring the device than giving Obihai your Google password.
As Irosenman explained, after you have done this, the OBiTALK portal has no further communication with your OBi device at all, with regard to Google Voice calling.
Azrobert did a nice job writing up how to use this procedure to configure GV, and then "go offline" by backing up your device configuration, if you so desire.
http://www.obitalk.com/forum/index.php?topic=8685.msg57331#msg57331
Oh, yes, I was quite aware of the session popping a new tab (in my case) for Google to ask me to authorize three permissions on the first pass, and a single one on a subsequent pass. I know my Google credentials were never touched by anyone except me and an instance of Firefox. That's not in question. The problem remains, where does the TOKEN go? Under what circumstances can the token be used to authenticate as me? Does the token go first to Obihai's server(s) and THEN to my OBi110? You seem to say it somehow makes it straight from Google's servers to my OBi110. It does not seem that way offhand, because the next step is to confirm that my GMail address is the one intended, THEN my OBi110 can log into GV. Yep, I plead ignorance at the moment because I haven't broken out neither tcpdump nor Wireshark yet.
It still remains a nearly indisputable fact that passwords should never be stored, but that's what ObiTALK does with the admin password for my device.
I'm pretty sure this will prove a very good read, how to detach from ObiTALK. Thank you very much for that.
Dude: just use a unique, strong password for your OBiTALK portal account. BFD.
No, nobody is going to get into hacking the token exchange procedure here.
I'm not concerned with the token being stored, and sent to the device during provisioning updates. However, passwords not being stored anywhere is kind of moot, as it has to be stored somewhere. If you use online provisioning, if that password wasn't stored, then it would be erased upon update of the provisioning.
BTW, Hey Steve (aka Bluescat).
Quote from: Willy-Bill on March 15, 2015, 10:44:57 PM
I'm not concerned with the token being stored, and sent to the device during provisioning updates. However, passwords not being stored anywhere is kind of moot, as it has to be stored somewhere. If you use online provisioning, if that password wasn't stored, then it would be erased upon update of the provisioning.
BTW, Hey Steve (aka Bluescat).
Hey Willy-Bill! Do I know you? My cat in my profile photo is Willie, btw.
I'm not sure what point you are making, but I think you are referring to password entry during the process. Just to clarify: when a user goes through the OBiTALK portal to set up OAUTH 2.0 authentication, Obihai is not involved in the user's Google password exchange. The user first signs on to their Google account, on a typical Gmail or GV web page, which is a authenticated and encrypted channel between Google and the user's browser. Obihai isn't involved in that at all. After the user is signed in, as indicated by various session cookies, the user logs into the OBiTALK portal in another browser tab, and kicks off the OAUTH 2.0 setup. At this point, OBiTALK sends a request to Google to grant OBiTALK permission to access a service on the (already signed-on) Google user's account. Then, the user gets a pop-up window, on a new, secure Google web page, already signed into their Google account. This pop-up is where the user says "yes, OBiTALK can access service xyz on my account", and after that point, the secure token is transferred from Google to OBiTALK to the device. So, at no point does Obihai have the user's Google password. In fact, right after performing this procedure, the user can change their Google password, and not have to go through the setup again.
At any time, a Google user can view and, if necessary, revoke this permission, here:
https://security.google.com/settings/security/permissions
I hope this helps.
I updated the firmware on my OBi110 to 2872 and now when I'm in the middle of a phone call the device likes to reboot itself, which also terminates the call. I've done a reset and that didn't fix the problem. At this point I'd be satisfied with downgrading back to the older (working) firmware but alas, it is nowhere to be found! Help?
Quote from: -DC- on March 31, 2015, 06:44:17 PM
I updated the firmware on my OBi110 to 2872 and now when I'm in the middle of a phone call the device likes to reboot itself, which also terminates the call. I've done a reset and that didn't fix the problem. At this point I'd be satisfied with downgrading back to the older (working) firmware but alas, it is nowhere to be found! Help?
Your issue is unrelated to the firmware upgrade, or to this discussion thread. I haven't seen any significant reports from a large number of 110 users with this symptom. It's more likely due to a home network issue. I suggest you start a new discussion specific to your issue.