202 and the new update
Lavarock7:
Thanks, who knows. I'll just chalk it up to gremlins. As I daid, I just deleted the one service provider and re-entered it and it worked. Strange that one screen would just disappear though. I used ***6 to update.
MikeHObi:
When I performed the update, I didn't see the same problem, but I did notice something.
After restarting my SP3 - anveo was showing failure to authenticate. So I went into the sp, checked the settings and hit save. after the save, it showed connected.
giqcass:
I have had a little weirdness when I was messing around with dial plans. I got some kind of error page as the OBi rebooted but it would go away after a few seconds and a page refresh. I have done all updates manually. I have also been backing up my settings but I have not had to use a backup yet. I feel like the boot time is a little longer on this firmware but it might just be my impatience as I never actually timed it.
CoalMinerRetired:
As of this morning I'm getting this error on the System > System status pages:
XML Parsing Error: not well-formed
Location: http://192.168.1.xxx/DI_S_.xml
Line Number 283, Column 58:
<value hash="417db31c" type="input" default=" " current="" >
---------------------------------------------------------^
For the record, this error was not present last week when I first applied the update. And it also means one cannot see or get into the main system status page.
giqcass:
That is the error I was getting at reboot when I was adjusting dial plans. As I said before it just went away on its own for me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page