SIP phones no longer connected after 3.2.1 (Build: 5794EX) Saturday 1/21/18
RFC3261:
Quote from: BlakeN on January 22, 2018, 12:29:01 pm
Is the November 3-2-1-5757 (10.4MB) version the one I want?
The 5757EX version is working for me (I suspect the non-EX version works too, but I have not tested it).
Quote
Can I blacklist fw.obihai.com in my router to accomplish the same thing?
Individual routers vary in terms of their capabilities. Blocking the DNS name (in my case via RPZ) appears to work for me for now. Blocking the IP address probably would work too, but may or may not work long term (the DNS name may change to a different IP at some point). Removing the OBI from the portal entirely also reportedly works to prevent auto-firmware updates.
If one presumes that one only needs a temporary solution (i.e. OBi will address the issue), any solution is probably adequate for today (and sometimes it is all about the now).
Blake4913:
Reverted to Nov 5757EX version and that solved the issue. It is goofy they both have the same version number. No config change needed. Just loaded software and it all came back to life. Now to see if my black list in my router firewall will keep software from updating again. Fingers crossed for now. Thanks again for the support. I sent in a support ticket to Obi. Hopefully they will resolve in new code.
Blake4913:
hmmm - I got the "Your OBi device doesn't have a valid support coverage so we're unable to view anything further on this device." response. I sent a very nice reply even though after spending about 4 hours of my time troubleshooting this I was not real happy with the response. If one of you have a device under warrantee or have Premium support it may be worth putting a ticket in. It appears Obi may still not be aware of the issue.
RFC3261:
Quote from: Blake4913 on January 22, 2018, 01:41:47 pm
hmmm - I got the "Your OBi device doesn't have a valid support coverage so we're unable to view anything further on this device." response.
Pretty sure that is the new normal response (close to reflexive?) for any device without a support contract.
Quote
It appears Obi may still not be aware of the issue.
Possibly. My guess (with zero evidence) is more likely that internal engineering is aware of it one way or another (as OBi once documented how to do the configuration (in a blog post long ago taken down) one would think they would expect some people were doing what they said to do), but that the support group has a policy to not invest support resources to even check unless you have a support contract.
If I had the time to invest (I certainly did not invest anywhere near 4 hours like you did) I might pay the $10 just to force a response, for $10 is less than two designer coffees.
BlakeN:
Trust me - I thought about saying I would be happy to pay them $10 to fix it. I put this together about 3 years ago. It probably took me 2 hours just to remember what I had done even though everything was backed up and I had drawn diagrams and tables of IP addresses, etc. It sucks to get old. But hey, it is better than paying Verizon $70/month for a POTS line. Thanks again for your insight!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page