December 12, 2017, 02:16:09 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 [2] 3 4 ... 10
  Print  
Author Topic: Firmware update for 20x series  (Read 188347 times)
Maurizio
Newbie
*
Posts: 1


« Reply #20 on: June 03, 2015, 07:08:00 pm »

+1 Same issue here with Obi 200, sp4 and Google Voice account.
Logged
corporate_gadfly
Jr. Member
**
Posts: 66


« Reply #21 on: June 20, 2015, 09:26:16 am »

ObiHai support -- Release Notes??
Yeah.. nothing from ObiHai.

Backup of device showed some new XML elements (related to Nest?):
Code:
Device.MiscFeature.Nest.
- NotifyNumber
- NotifyPeriodic
- NotifyEmail
- SmsServiceProvider
- SMSNotify
- EmailNotify
- CallNotify
and
Code:
OriginatingSeizurePolarity
TerminatingSeizurePolarity
Logged
Ostracus
Hero Member
*****
Posts: 581


« Reply #22 on: June 24, 2015, 02:01:35 am »

ObiHai support -- Release Notes??
Yeah.. nothing from ObiHai.

Backup of device showed some new XML elements (related to Nest?):
Code:
Device.MiscFeature.Nest.
- NotifyNumber
- NotifyPeriodic
- NotifyEmail
- SmsServiceProvider
- SMSNotify
- EmailNotify
- CallNotify
and
Code:
OriginatingSeizurePolarity
TerminatingSeizurePolarity

Looks interesting though. Could be useful for other purposes.
Logged
DrJay
Jr. Member
**
Posts: 43


« Reply #23 on: June 24, 2015, 07:28:38 am »

Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.

1. If there are no detailed release notes ("misc. bug fixes" is not detailed), I don't update.
2. If there are detailed release notes and I don't have any of the problems that the new release fixes, I don't update.
3. If there are detailed release notes and there are no new features that add real value for me, I don't update.

I can stare at a yellow triangle for months and months without any effect on my pulse or blood pressure.  Tongue
Logged
WelshPaul
OBi Phone Beta Tester
***
Posts: 405



« Reply #24 on: June 24, 2015, 07:56:30 am »

I can stare at a yellow triangle for months and months without any effect on my pulse or blood pressure.  Tongue
You my friend will live a long and happy life.  Grin
Logged

For everything VoIP
www.ukvoipforums.com
RFC3261
Full Member
***
Posts: 129


« Reply #25 on: June 24, 2015, 09:54:30 am »

Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.

I believe the only really important rule (for all upgrades, whether they be iOS, Windows, or Obi) is:

0) If you do not have a spare "test mule" device (and many on this forum do, but many do not) and the device is "production" and working well, never, ever, be the first to upgrade.  Let others take the plunge and report failures.  Anecdotal reports of disaster should be discounted ("stuff" happens), but if there is a rash of complaints, wait for the issues to be understood, resolved, or workarounds provided.

Of course, if everyone waited until someone else tested first there would be no way forward, but there are always those who will serve as a vendors testers (whether they know they are guinea pigs or not).
Logged
restamp
Full Member
***
Posts: 193


« Reply #26 on: June 24, 2015, 11:41:19 am »

The last I heard, 4738 was the latest firmware for the 200 and 202 ATAs.  I am sticking with 4581 for now, based on several reports of some things not working correctly (for instance, SP4 configurations breaking) on the 4738 firmware.  But this begs the question:  What if I want to add a GV account to my device or change a GV password today?  I need to be on 4738 to do so, right?

So, what's the resolution:  Upgrade, change GV, downgrade?  Unfortunately, the ins-and-outs of configuring these OBis have become anything but simple since OBiHAI started changing the rules of the game, and what's to prevent them from issuing a future firmware update which prevents downgrading?  I really like the self-contained nature of GV under these OBis, but Ryan Tilton's OAUTH2.0 under Asterisk is looking more-and-more desirable as things progress.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3948



« Reply #27 on: June 24, 2015, 04:38:38 pm »

Reports of 4738 "breaking" GV configuration functionality proved to be incorrect.  The root cause was attempting to use the portal to configure an out-of-warranty device, when it had a down-level version of the firmware, and being told to purchase support to continue.  You can simply upgrade the firmware manually/locally, and then return to the portal to continue the GV setup process.  I've successfully tested this on two 200s and a 202 without issue.

More details on the procedure:  http://www.obitalk.com/forum/index.php?topic=10065.0
Logged

RFC3261
Full Member
***
Posts: 129


« Reply #28 on: June 25, 2015, 11:34:55 am »

... and what's to prevent them from issuing a future firmware update which ...
The honest answer is nothing prevents them from issuing a firmware update that does anything (well, achieving world peace is probably beyond their capabilities).  Or if they choose (and this would seem to me to be more likely at some point), simply stop issuing firmware updates (and support) completely for their older devices.

But FUD will rarely serve you well.

One must remember that this forum is going to attract those with problems, and issues.  For any update/change, there will be some which encounter problems.  As we have seen to this point, sometimes there are workarounds, and sometimes "stuff happens" to a particular device (there is a small percentage of iPhone bricking too at every iOS upgrade).
Logged
zorlac
Full Member
***
Posts: 203



« Reply #29 on: June 25, 2015, 11:32:10 pm »

Here are my personal rules for OBiHAI firmware updates. They have served me well for years. YMMV.
I can stare at a yellow triangle for months and months without any effect on my pulse or blood pressure.  Tongue
OK, so what FW version are you currently running?
I want to download & save the older FW versions that work while it's still possible.  Undecided
Logged
DrJay
Jr. Member
**
Posts: 43


« Reply #30 on: June 27, 2015, 02:37:29 pm »

 Tongue
OK, so what FW version are you currently running?
I want to download & save the older FW versions that work while it's still possible.  Undecided

I am currently enjoying a bottle of OBiHAI 3.0.1 (Build: 4609). It's a full-bodied release with delightful notes of copper and polystyrene and just the slightest hint of ozone.

It pairs well with the bold flavors of DECT 6.0 cordless phones and even an occasional Samsung analog multifunction printer. The label doesn't suggest a serving temperature but I find it is best served between 22 and 26 degrees Celsius.

Cheers!

Logged
restamp
Full Member
***
Posts: 193


« Reply #31 on: July 03, 2015, 03:11:32 pm »

Is the latest firmware for the Obi20X devices still 4738 or has something newer been issued?

Aside from installing it, how do we find out what the latest firmware release is?

Have any release notes defining the firmware changes/fixes been released since 4581?

Does anyone know of anything that the latest firmware actually fixes?  Breaks?

TIA
Logged
evergreen
Jr. Member
**
Posts: 26


« Reply #32 on: August 07, 2015, 01:45:22 pm »

I took the plunge and updated to build 3748 and sp1 to sp4 are working just fine on an Obi202.  I just wanted to report back as I want to move away from reporting only when things go south.  Cheers.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 3948



« Reply #33 on: August 07, 2015, 02:07:04 pm »

I took the plunge and updated to build 3748 and sp1 to sp4 are working just fine on an Obi202.  I just wanted to report back as I want to move away from reporting only when things go south.  Cheers.

A high five to you, for reporting a smooth upgrade.  Enjoy!
Logged

corporate_gadfly
Jr. Member
**
Posts: 66


« Reply #34 on: August 08, 2015, 11:58:33 am »

I took the plunge and updated to build 3748
Transposed more than a few letters there. I have the latest firmware as 4738.

Interestingly, OBiHai has managed to squeeze more from less number of bytes in the firmware. Dating back to October 2012, the firmware has been approx. 13MB in size. I.e., all the way until 4581. The 4738 firmware is 10M.

Go figure.
Code:
size: 10958100
md5sum: 5aa19e2d5d8a14c188b2a47d92bd2f25
Logged
Taoman
Hero Member
*****
Posts: 931


« Reply #35 on: February 24, 2016, 10:55:53 am »

Software version level: 3.1.0 (Build: 5135)

fw.obihai.com/OBi202-3-1-0-5135.fw

Version level: 3.0.1.4738

fw.obihai.com/OBi202-3-0-1-4738.fw

Logged
Taoman
Hero Member
*****
Posts: 931


« Reply #36 on: May 14, 2016, 03:53:07 pm »

Software version level: 3.1.0 (Build: 5264)


http://fw.obihai.com/OBi202-3-1-0-5264.fw

« Last Edit: May 15, 2016, 07:16:05 am by Taoman » Logged
chicobiker
Newbie
*
Posts: 16


« Reply #37 on: May 14, 2016, 09:20:57 pm »

Let my 200 do the automatic update today for 5264 with no issues so far. Just FYI.
« Last Edit: May 22, 2016, 06:51:42 am by chicobiker » Logged
restamp
Full Member
***
Posts: 193


« Reply #38 on: May 15, 2016, 12:01:17 am »

Actually, the correct link to the 3.1.0 (Build: 5264) firmware is

http://fw.obihai.com/OBi202-3-1-0-5264.fw
Logged
Taoman
Hero Member
*****
Posts: 931


« Reply #39 on: May 15, 2016, 07:18:08 am »

Actually, the correct link to the 3.1.0 (Build: 5264) firmware is

http://fw.obihai.com/OBi202-3-1-0-5264.fw

Thanks for the correction, restamp. That'll teach me to copy and paste. Maybe.  Wink
Logged
Pages: 1 [2] 3 4 ... 10
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC