I hadn't seen this thread when I was trying to update....
For some reason today, I visited obitalk...and saw that both my 110 and 202 were in need of updates. I tried the 202 first, it failed via obitalk. Tried again, still no go. Started looking around on alternatives.
Ended up trying through the web interface, except I was on my 110 because I wanted to move where syslog was going to. Also updated it to use local ntp servers, instead of
pool.ntp.org.
had to reboot before I could do firmware update, then did firmware update.
No problems that I can see with that.
So, I then went to my 202, moved its syslog, had already changed it to use local ntp, except that I had moved my local ntp servers so updated that too.
It didn't say that it required a reboot after I made those changes, could see syslog output at new location immediately after I had submitted the change. But, I rebooted the 202 first, and then did the firmware update.
Things looked alright, shows version 3.0.1 (4109), except the interface shows "reboot required". So, I rebooted again. It still says "reboot required".
Didn't see anything about this on the new firmware post, wonder what's changed....
GV is working, I had deleted sipgate as SP2 a couple of weeks ago (don't recall which device needed update when I had visited then, but it was only one of them and it updated successfully via obitalk
Can't tell why its saying reboot required...
Noticed that both "reboot required" and "config current" are accessed as "./caution.png"....
The Dreamer