New firmware for Obi 200/202
GPz1100:
It's a bit of a catch 22. Auto provisioning can (and probably does) re-enable auto firmware update. So agreed, both, or better yet everything on that page should be disabled to ensure no spam from the mothership.
Kage:
Quote from: IterationIsFailure on January 21, 2018, 05:38:23 pm
I pulled DNS calls from the OBI. It contacts fw.obihai.com, which seems to indicate that is choke point to block. Time to test, ;D
Wouldn't it be possible to block fw.obihai.com in the host file or through the router and that would stop forced updates?
Mango:
Quote from: IterationIsFailure on January 21, 2018, 05:18:43 pm
I noticed my OBI202 update (without permission) earlier today to 3.2.1 (Build: 5794EX) contrary to having FW Updates disabled in the UI to prevent such behavior.
This has been a source of confusion and much criticism of Obihai for quite some time. The configuration to disable automatic firmware updates is:
System Management >> Auto Provisioning:
Auto Firmware Update >> Method: Disabled
ITSP Provisioning >> Method: Disabled
OBiTalk Provisioning >> Method: Disabled
Voice Services >> OBiTALK Service:
Enable: (Unchecked)
If you're particularly concerned, add !**5S0| as the first sequence of the DigitMap to prevent OBiTALK from being re-enabled.
Quote from: IterationIsFailure on January 21, 2018, 05:38:23 pm
So, I disabled OBiTALK in "OBiTALK Service Settings" and the unit now shows as "Offline" on the Obi website, but unsure what consequential problems I'll run into, such as the Google Voice configuration,
Google Voice configuration is the primary (only?) thing you can't do without OBiTALK, if you use the stock firmware. However, once it's configured, you generally don't need to mess with it. Also, as of today the OBi200/OBi202 firmware has been successfully hacked to allow offline configuration of Google Voice. No reports from anyone who tried it yet, but presumably it will work as well as the 100/110 hacks.
ProfTech:
I spoke too soon. After enabling TLS my Obi 200 started dropping calls. Switched it back to UDP and everything seems Ok. Since I don't know if TLS ever worked I can't say it was a problem with 5794 for sure. I just wanted to note the issue in case someone else runs into it.
ProfTech:
There may be light at the end of the tunnel. I am pretty sure auto update was turned off in my 200 because the "upgrade available" flag was showing in the portal for months. Then I used the portal to upgrade to 5757. I didn't notice immediately but after Obi sent 5775 I noticed Auto update was set to run every 24 hours. So GPz1100 may be right and they enabled it in 5757. However, I noticed yesterday after 5994 was installed Auto update is now turned off. Maybe Obi corrected the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page