Devices with very old firmware will no longer be able to connect.

Started by OBiSupport, June 03, 2022, 10:13:10 AM

Previous topic - Next topic

drgeoff

Are you accessing that Status page via your dashboard at obitalk.com or directly locally from the OBi's onboard webserver?

Locally you can backup the configuration to a file and restore from it after a reset.  However passwords are not saved in that file and if using GV I expect that needs reconfiguring too.

IIRC, beginning several firmware versions ago they do not accept a downgrade firmware.

My separate post about the meaning of "connecting" was intended for anyone coming to this thread and not specifically for you.  TBH you are a hijacker and should have started a new topic.

(I'm not sure if Obihai has actually done the server update yet.  I have an OBi100 and an OBi110 both on 2886 firmware and as I type this they are still connected to my dashboard.)


Taoman

Quote from: HDFLucky on June 16, 2022, 03:42:02 PMSince I can't reload the same firmware version, are there older versions available that I could downgrade to and then try the update again?

You can try but as drgeoff mentioned, you may not be allowed to downgrade. I assume you are not using Google Voice since you mentioned seeing a Registered status for your SPs and not "Connected" for a GV trunk. Any older version of the firmware won't work for Google Voice trunks.

But if you want to give an older version a try here is the url to download it:
http://fw.obihai.com/OBi202-3-2-2-5921EX-332148940.fw

Edit: For some reason the link I posted doesn't seem to open directly from my post (at least for me). But if you copy the link and paste it in a new tab it should work.
Hmmm. It looks like the link I posted omits the http:// when trying to open directly from my post??

HDFLucky

Quote from: drgeoff on June 16, 2022, 04:00:52 PMAre you accessing that Status page via your dashboard at obitalk.com or directly locally from the OBi's onboard webserver?
Neither, I was accessing by directly typing the ip address of the OBi202 into the browser. I had forgotten it could be accessed from the dashboard (though it looks different). When I try it that way, I get a similar result and am still unable to read off-hook status ("Cannot retrieve requested information from the device now. Please try again later." error).

And you're right, this did turn out to be a thread hijack. I was so taken aback at what happened that I didn't stop to think where I was posting. I apologize.

After sleeping on it, I've decided to try a total reset, as you suggested earlier. I'm fully backed up now, and recorded ITSP customizations etc. If it fails to restore dial tone, then I'll try the firmware downgrade (if it's possible).

@Taoman: I saw the same thing as you, but I can manually copy the link and it works. I'll try it as a last resort (I only use GV on my mobile phone, not with OBi).

drgeoff

Quote from: HDFLucky on June 17, 2022, 03:40:23 AM
Quote from: drgeoff on June 16, 2022, 04:00:52 PMAre you accessing that Status page via your dashboard at obitalk.com or directly locally from the OBi's onboard webserver?
Neither, I was accessing by directly typing the ip address of the OBi202 into the browser.
There is no method other than the two I provided as choices.  Typing the IP address of the OBi202 into a browser IS accessing directly locally from the OBi's onboard webserver.


HDFLucky

SUCCESS! Resetting the OBi202 and then restarting restored dial tone. :)  But after importing my backup config file it was gone again! :(  I finally found that the problem was caused by having PrimaryLine set to a trunk group... even if it was set on Phone1 when using Phone2. ???  This previously worked fine. I'll have to rethink my  trunking but at least I'm back in business. Thanks to all who offered suggestions.

Taoman

Quote from: HDFLucky on June 17, 2022, 02:08:16 PMI finally found that the problem was caused by having PrimaryLine set to a trunk group... even if it was set on Phone1 when using Phone2.

You must have been on an old firmware version before you updated if that was working for you. Setting your PrimaryLine to a TG hasn't worked for the last few versions of the firmware including the current one. It's a definite bug and I wouldn't count on it ever being fixed.