User avatar
By WelshPaul
#4274
Below are the firmware release notes (in ascending order) for the Obihai OBi2xx & OBi3xx Series Universal Adapters. These release notes describe what new features, enhancements and bug fixes are contained within a specific firmware version.

To view the very latest release notes for the Obihai OBi2xx & OBi3xx Series Universal Adapters, click here.
User avatar
By WelshPaul
#4275
Supported Products:
  • OBi200
  • OBi202
  • OBi300
  • OBi302
Firmware 3.1.1 (Build: 5491)
January 19, 2017

Features and Enhancements:
  • 64 hex digits, i.e. 32 byte WPA-PSK support.
  • New parameter called “DeviceInfo.WAN.OpenSSLCiphers” to control the ciphers used for SSL connections.
  • DFS support at 5GHz for OBiWiFi5G wireless adapter accessory.
Bug Fixes:
  • Continual re-transition of Un-REGISTER requests until timeout, ignoring server response.
  • ACS server cannot read Device.Status.PhonePort.{i}. object.
  • Accept a URL as a DHCP option 66 value.
User avatar
By WelshPaul
#4313
Supported Products:
  • OBi200
  • OBi202
  • OBi300
  • OBi302
Firmware 3.1.1 (Build: 5562)
February 15, 2017

Features and Enhancements:
  • Include DigiCert SHA2 Secure Server CA certificate in firmware.
  • FaxDetectionMethod now supports CNG or V.21 preamble.
  • Support custom CA cert installation using provisioning.
  • Added WiFi platform information for the OBiWiFi and OBiWiFi5G.
  • Added MOS to X-RTP-Stat header.
  • Added Thawte CA G3.
Bug Fixes:
  • Device reboots when SSRC changes from the first to the second incoming RTP packet.
  • Fail to switch to fax mode (T38 or pass-through) under some circumstances.
  • The combination of conflicting WAN and LAN IP address and enabled LLDP could create an infinite boot loop.
User avatar
By WelshPaul
#4396
Supported Products:
  • OBi200
  • OBi202
  • OBi300
  • OBi302
Firmware 3.1.1 (Build: 5589)
March 15, 2017

Features and Enhancements:
  • Replace DigiCert SHA2 Secure Server CA certificate with DigiCert Global Root CA in firmware.
Bug Fixes:
  • When sending keep alive to the proxy server, it does not follow current TCP/TLS channel; it only sends it over UDP channel.
  • Tel-event RTP payload type does not change according to a peer reinvite; it stays at the original value established during original invite.
Who is online

Users browsing this forum: No registered users and 0 guests

Hi guys, I wonder if you could help me, I've been…

I am surprised somebody as knowledgable as yours…

OBI1062 issues

I was wondering if the issue is also present when …

Why would you waste your time on this when you can…