Menu
naf firmware

Crowdsourced updates for Obihai ATAs and IP Phones

Learn More
About

Why use third-party firmware?

Read on for more information about the problems this third-party firmware solves, or skip to firmware downloads if you want to get started right away.

So what is this all about?

You are likely here because you own an OBi device. Traditionally, OBiTALK was designed as a remote configuration tool for your OBi hardware. A hardware owner sets up a desired outcome/configuration on OBiTALK, and the OBiTALK system was able to update the hardware configuration next time it called home. There has always been a way to directly configure OBi hardware via logging in via a web interface, but it was always a bit complicated and prone to complications for some configurations, e.g. Google Voice and its authentication process. Recently, the company has announced that several OBi devices, specifically the 2XX models, will enter End of Life in 2023. There are some uncertainty what will become of OBiTALK after the 2023 deadline, but it seems clear that OBiTALK will not be able to further configure OBi hardware for Google Voice. There are of course other VoIP providers besides GV, and many think that OBiTALK will remain, much as it is today, a terrific way to set up OBi hardware for these other services. But nothing is for certain.

This new firmware for your OBi device, like other community developed firmwares for e.g. routers and Android phones, makes the current/future functioning of the hardware a bit more independent of the company that sold you the hardware. With it, your OBi device is less dependent on OBiTALK, especially for those that wish to set up their OBi device to use GV after the End of Life deadline. Whether there are advantages for users of other, non-GV VoIP services is unclear. This new community-created firmware will continue to grow and evolve, likely increasing the useful life of the hardware, and adding a few capabilities right now.

-written by Klaberte on DSLReports

History

On 19 June 2018, Google decommissioned XMPP servers so OBi100/110 don't work any more, even with the third-party firmware. While it's possible to make the 100/110 work, it's not that easy. If anyone likes to work on this project, please discuss it at DSLReports.

Today

Still are good features in the third-party firmware for OBi2/3, OBiPHONE, and now OBi5. Also adds a SSH server, allows unlocking of vendor-customized devices, and allows Caller ID contact list.

Downloads

arrynrob - for OBi200/OBi202/OBi212/OBi300/OBi302

If your current firmware version is less than 5853, just flash arrynrob directly.
If your firmware is 6259 or greater, you must install stock 5921EX (alternate link) first, then install bypass-uboot-mod.
If your firmware is >= 5853 and < 6259, you must bypass uboot by installing bypass-uboot-mod. Then, you can install arrynrob. DO NOT flash bypass-uboot-mod from 6259 or above, or you will be going to recovery mode (which also allows you to flash any firmware you want, but it just doesn't look as cool).
md5sum OBi302-3-2-2-6259-signed-fw-bypass-uboot-mod.fw = 59229dd211edb52d9f2e49729cee9794

Please read above installation instructions before install arrynrob!
Download - OBi2xx-3-2-2-8680EX-arrynrob11.fw
md5sum OBi2xx-3-2-2-8680EX-arrynrob11.fw = 7ef2a2d316e42c9c3d010ba7ec5deee3
Changes:
  1. update clear_zt_params and param_dump to support hw_vers 1.5
  2. the changes from arrynrob10:
  3. enable dropbear ssh server. default root passwd = "obi".
  4. (NEW) included a version of wget that supports https
  5. patch OBiapp to bypass "zero touch" forced configuration. added clear_zt_params util to clear old zero touch params
  6. patch OBiapp to use /scratch/contacts.xml for caller id number to name translation lookup.
  7. patch OBiapp to bypass signed firmware check when loading new fw
  8. patch OBiapp to bypass GVSIP provisioning lock
  9. patch OBiapp to bypass 30x models GV initialization block

taoman1 - for OBi2000 series

Installation instructions:
  1. To go to a modded fw from stock, flash to OBi2000-6-2-3-4907-signature-bypass.fw first.
    md5sum OBi2000-6-2-3-4907-signature-bypass.fw = 24d0bcad8601d96b5f6b05120181c967
  2. Next, install OBi2000-6-2-3-5330-taoman1.fw.
    md5sum OBi2000-6-2-3-5330-taoman1.fw = 03f7cf28f0094296bed48cfe5d3e4f22
Changes:
  1. enable dropbear ssh server. default root passwd = "obi".
  2. patch OBiapp to bypass "zero touch" forced configuration. added clear_zt_params util to clear old zero touch params.
  3. patch OBiapp to bypass signed firmware check when loading new fw
  4. patch OBiapp to bypass GVSIP provisioning lock
Mod implemented using a new technique of adding code to the padding at the end of an ELF segment instead of overwriting functions inline, because this fw uses oauth in more places.

olisom - for OBi1022/OBi1032/OBi1062

Installation instructions: If you wish, try to skip directly to Step 3. If you have an old firmware version, it may work.
  1. First, ensure you are not using build 4858. If you are, then flash to different version such as OBiPhone-5-1-11-4983EX.fw
    md5sum OBiPhone-5-1-11-4983EX.fw = b10d7c73d8898028fac8698e6d5516b6
  2. Next, install OBiPhone-5-1-11-4858EX-noshell-signed.fw
    md5sum OBiPhone-5-1-11-4858EX-noshell-signed.fw = 123bd1842a64ab967644e34e6a7d144c
  3. Now, you may install olisom firmware: OBiPhone-5-1-11-5312EX-olisom5.fw
    md5sum OBiPhone-5-1-11-5312EX-olisom5.fw = c2a744a067447a78a348ecd17795c757
Changes:
  1. add dropbear ssh server. default root passwd = "obi"
  2. patch OBiapp to bypass "zero touch" forced configuration. added clear_zt_params util to clear old zero touch params
  3. patch OBiapp to bypass x509 signature check for new fw

ssyspro - for OBi5 series

Installation instructions:
  1. To go to a modded fw from stock, flash to OBi5xx-4-0-5-7707-noshell-signed.fw first.
    md5sum OBi5xx-4-0-5-7707-noshell-signed.fw = 0205d029107d603379eaba37ca6d3956
  2. Next, install OBi500-4-0-5-5903EX-ssyspro5.fw
    md5sum OBi500-4-0-5-5903EX-ssyspro5.fw = 1949638ca7161904fbda0da795b8eec9
Changes:
  1. enable dropbear ssh server. default root passwd = "obi".
  2. patch OBiapp to bypass "zero touch" forced configuration. added clear_zt_params util to clear old zero touch params.
  3. patch OBiapp to bypass signed firmware check when loading new fw
  4. patch OBiapp to bypass GVSIP provisioning lock
  5. NEW: patch OBiapp to fix the bug where OBi forgot to set the TLS SNI hostname resulting in "No Response From Server" when attempting to connect to GV

aa2k - for VVX D230

Installation instructions:
  1. Flash stock 7-0-0-6932 (alternate link), then noshell-signed, then aa2k.
MD5s:
VVX-D230-7-1-3-9112-aa2k1.fw = c15d73707d3062b5f0508ebcbcc6b5b3
VVX-D230-7-1-3-9112-noshell-signed.fw = c88265af24a66a60d1df5e295e93095f

Changes:
  1. enable dropbear ssh server. default root passwd = "obi"
  2. patch obiapp to not kill dropbear or overwrite root password
  3. patch obiapp to bypass "zero touch" forced configuration. added clear_zt_params util to clear old zero touch params
  4. patch obiapp to bypass x509 signature check for new fw

naf - for OBi100/OBi110

Download: - OBi1-1-3-0-2886-naf8.fw
md5sum OBi1-1-3-0-2886-naf8.fw = e0496c80d5f308ace35871412ba62133
Notes for use: see naf's post on DSLR.
Changes:
  1. add globalsign cert (root for GIAG3)
  2. remove firmware downgrade check
  3. oauth token request override (not that xmpp works anymore)
  4. syslog key/cert dump during backup

Disclaimer

These firmwares, like the official Obihai firmwares, are provided without warranty. Standard precautions apply, such as do not install firmware over a wireless network connection.

Support

Where to get support

Obihai does not support OBi100/OBi110 ATAs (and doesn't really support their other products either).

VoIP Tech Chat

DSLReports hosts one of the busiest VoIP forums on the internet, which is the forum where this firmware was first discussed and published.

OBiTALK Community

The OBiTALK Community is a forum specific to users of OBi products. It has largely been abandoned by Obihai but the users are sometimes helpful.