SIP phones no longer connected after 3.2.1 (Build: 5794EX) Saturday 1/21/18
BlakeN:
Hi All,
Any help would be greatly appreciated. It appears that both of my OBI 200s were updated automatically with software yesterday [3.2.1 (Build: 5794EX)]. After the update neither of my SIP phones will connect - found this way when I entered my office this evening. After research of forum see that updates to OBI 200 were pushed yesterday. My last call received on my phone was yesterday. I verified and current s/w seems to match. Both OBIs external lines are connected just fine (2 goggle voice and one Anveo). I am getting Failed(Authenticate) errors on Cisco phones. I have two OBI 200s with two lines each. I have Cisco SPA514G phones connected to them - I believe one line of each OBI to each phone (2 lines programmed on each phone). I have been using these without any trouble for years and have made no changes to config. I did try rebooting my router, phones and Obi devices with no resolution. Thanks in advance for any advice.
ProfTech:
Wow. :( Did you happen to have a backup of the .xml config for the Obi's? You could make a new backup and then compare/diff it to the old one.
RFC3261:
Quote from: BlakeN on January 21, 2018, 05:58:11 pm
Thanks in advance for any advice.
Not exactly a "fix" (just a workaround), but it seems that adding fw.obihai.com to your bind RPZ zone(*) (to prevent the device from updating) and then force loading one of the previous firmwares is a workaround for now. SIP phones work again.
We will have to wait and see if this was an accidental breakage that will be resolved with a further firmware update, whether one will be forced to stay on the older firmware (forever?), or whether one will need to investigate alternative solutions (other than the OBi devices).
(*) bind (named) RPZ zones can be used to block DNS requests for specific or generic targets. They are used by some to block lookup to known bad actors (or advertisement sources). As is typically the case, there are typically many ways to accomplish the equivalent thing, but when one is already using RPZ, it becomes an obvious choice in these cases.
BlakeN:
Hi All,
Thanks for the ideas. I do have a backup. I set this up in 2015. I don't see any real differences in the configuration. Everything carried through. As I said I tried reseting passwords on both sides in case that did not carry through. Thats not saying there is some obscure setting somewhere. There are lots of parameters as you know. The XML formatting changed between exports in 2015 and now so the diff is a bit hard to read - meaning it is not easy to see the differences.
Is the November 3-2-1-5757 (10.4MB) version the one I want?
Can I blacklist fw.obihai.com in my router to accomplish the same thing? I am not familiar with RPZ zones.
Thanks for the help!
TheLliez:
Same problem here. Something happened this weekend. My 202 is on firmware 3.2.1. and my SIP phone does not register anymore.
Navigation
[0] Message Index
[#] Next page