Any Obi202s bricked with latest firmware upgrade?

(1/4) > >>

kitt:
I've been using obi202 with various voip services.
Just tried to configure an empty SP slot directly with my google voice account, per recent obihai announcement.
Obi told me I needed a firmware upgrade to do this
I read that a number of obi1xx devices are experiencing difficulty with this, including getting bricked.
Are obi202 devices doing OK with this firmware upgrade?

MikePA:
Quote from: kitt on September 26, 2014, 11:16:40 pm

Are obi202 devices doing OK with this firmware upgrade?

Yes.

SteveInWA:
There have been no reports of OBi 20x devices having problems with the recent firmware upgrades, and only 3 reports here for 1xx devices. 

Keep in mind that online forums tend to get the people with problems, and the many (tens of thousands?  hundreds of thousands?) of users who just use the product without problems don't post.

Mango:
Actually it's at least eight reports of problems with OBi1 firmware, not three.

JohnBowler:
I've upgraded to 3.0.1 (Build: 4350) without problem, this is an upgrade via the Obi itself (I hardly ever even look at ObiTalk these days).  I don't use ***6 or attempt to invoke an upgrade myself, just wait for things to come down automatically.

Auto firmware update is enabled, but the check line is:

IF ( $FWV < 3.0.0.3460 ) FWU http://www.obihai.com/firmware/OBi202-3-0-0-3460.fw

(Notice that is 3.0.0, not 3.0.1).  ITSP provisioning is disabled (I think that's only for ISP provided units) and Obitalk provisioning is enabled.  Consequently I assume the Obi is getting updates through ObitTalk (even though I don't use it) and ObiTalk isn't saying the device should be updated at this point.

I believe some people reporting problems had obtained build 4420 (or something like that).  I don't use GV for outgoing calls; GV dials my e911 number on my SIP which then distributes the calls to the VOIP devices I use, including the Obi.

Navigation

[0] Message Index

[#] Next page