News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

OBi110 firmware updated Aug-24-2014 to Ver 1.3.0 (Build 2872)

Started by bluechip, August 24, 2014, 02:23:20 PM

Previous topic - Next topic

bluechip

Dashboard just updated my OBi110 firmware.

Hardware Version   3.4
Software Version   1.3.0 (Build: 2872)

Seems to work fine...
:)

LeoKing

My 2 OBi110's (HW ver 3.4) are still on 1.3.0.2868 and I was not prompted to update the firmware.

RFC3261

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).

Huib

The latest one available for general download seems to be build 2824. Any idea what the URL is for the newer build(s)?


SteveInWA

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.



Newbie

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.

Cajun1

Hi, how can I see my current firmware level? Thanks much.

RFC3261

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).

antani1971

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

ProfTech

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.

RFC3261

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.

BigJim_McD

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.
BigJimMcD

Cajun1

Thanks RFC, for the info to be able to see my IP address.

FameWolf

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!


SteveInWA

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.

mascasa

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.

ProfTech

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