SoftwareVersion 1.3.0 (Build: 2824) (Sept 4, 2013)
QBZappy:
@OZOi,
Have you tried asking obi support for a copy of the firmware. I'm betting that they would do it for you simply to have you report back that the customer service is great. (NB: Some firmwares are not backward compatible)
azrobert:
Quote from: OZOi on September 13, 2013, 02:48:31 pm
The problem here is - it's a custom FW
I don't think it matters if it's a custom FW. Build 2776 was not an official release, but I was able to download it.
Log into your OBi via the Web. You will be presented with a System Status page. The build number is listed next to SoftwareVersion.
OZOi:
@QBZappy, good advise :) Next time I'll be a bit smarter and will ask tech support to allow me to download custom FW to my computer,
@azrobert, it's not a common build number (4 digits). Build ID for that custom FW is comprised with 13 digits and characters plus date/time stamp.
Good news. I've run the roulette and won. Apparently the new build included the fix for my problem :) No need for that custom FW anymore (which I can't restore now)...
Smee:
Quote from: OZOi on September 13, 2013, 07:15:18 pm
Good news. I've run the roulette and won. Apparently the new build included the fix for my problem :) No need for that custom FW anymore (which I can't restore now)...
So out of curiosity, what issue where you having that was fixed by the custom firmware and seems to be included in 1.3.0 (Build: 2824). Might help others out in the future if running older firmware since we aren't getting release notes with these updates.
Smee
OZOi:
It's problem with ZRTP. Any SIP client supporting ZRTP crashed OBi device (call in or out). Reported here in May, 2012.
Navigation
[0] Message Index
[#] Next page
[*] Previous page