Can't restore configuration from backup made today
OZOi:
@CoalMinerRetired, no I haven't. But that's exactly my experience.
The problem is - OBi creates broken backup files. Sometimes it's truncated, sometimes it's missing some parameters, and sometimes it even has broken XML fragments (see my post above). Try to make several backups in a row (without changing configuration in between) and compare those saved files. Because actual configuration was not changed, they should be the same (except time stamps, of course). But they are not... :(
Saving backup files was broken sometime after January 2012... Before that it was working well. I can restore configuration using those old files without any problem.
Now, if you feel desperate (as I do) and need it to fix it, you have to go and manually edit broken files in hope to restore their XML integrity. I did it with the last file (it took a lot of my time) and now, instead or making changes in web console and then save the next version of backup file to be able to restore it later, I have to edit configuration directly in that file and then restore it into OBi... That's weird! But I don't see any other options now. I can't save configuration backup, without the need of manually correcting them again :(
zapattack:
If using IE, try Firefox, or Chrome, or whatever else might work to do a backup.
You should not get partial files.
Remember Passwords are not backed up, as well as a few other items, but Dial Maps should be.
OZOi:
@zapattack, thanks a lot for useful advice. I've made several backups using Chromium, instead of my default IE and it looks like OBi can make them work. Now I have to remember to use different browser to make backups, than I use to configure OBi... :) Restoring works fine with IE though.
About keeping passwords within configuration file. I need to keep them in the file. So, when I restore some old configuration - OBi should work immediately, without need for second reboot, required after entering password manually... There is absolutely no any security problem for me in my environment, and I don't share my backup configuration files with anyone. It'd be very, VERY nice if OBI allowed me to save my passwords in those backup files. An option, which offered that (among other backup options), would be very useful. Iit wouldl save my time. Why backup configuration file saves last dialed number (which has absolutely nothing to do with configuration) and not passwords, which are actually part of configuration?
Unfortunately current support of passwords, saved within configuration files, is half-broken. I add these tags into my backup files manually:
<ParameterValueStruct>
<Name>AuthPassword</Name>
<Value>myPass</Value>
</ParameterValueStruct>
While it always works well for SP2, for some weird reason, it doesn't for SP1. It'd be nice to see at least some fix here. :)
zapattack:
Glad your backups are working.
From a security perspective, having passwords in an easy to read XML document is not good practice.
BUT, if you want to keep them in the same document, put them in your Speed Dial list!!
Nothing checks to see if the data in there is a real number...
OZOi:
Do you mean to keep passwords handy to be able to copy paste them from speed dial entires to appropriate AuthPassword fields? If so, remembering passwords is not a problem. The problem is, I have to enter passwords manually and make second (unnecessary, IMHO) reboot every time I change configuration, using different providers... So, I change configuration using old backup file and reboot. Then I have to enter passwords and reboot again. :(
In my environment there is absolutely no security risk in keeping those credentials in configuration files, that I want to maintain. And I enter passwords into them manually. But even in this case (passwords are within configuration files), OBi doesn't honor them and simply discards :(
Earlier I've come to a wrong conclusion, that OBi can accept password for SP2, while discarding it for SP1. It was due to the case, when I switched between two configuration files, where second provider was the same. Let say I have configuration files: AB.xml and CB.xml (A, B, C are different VoIP providers). When I switched between those two configurations, the second provider (B) had no problems with login (because it was the same in both cases). Now I've made three configurations - AB.xml, CB.xml and CA.xml and it becomes obvious that:
1. OBi always discards AuthPassword value specified in configuration files
2. OBi keeps AuthPassword value from previous configuration, even if provider (account) was changed
I can create separate configuration file, that contains only credentials. For example:
<?xml version="1.0" encoding="UTF-8"?>
<ParameterList>
<O>
<N>VoiceService.1.VoiceProfile.1.Line.1.SIP.</N>
<P>
<N>AuthUserName</N>
<V>myAccount</V>
</P>
<P>
<N>AuthPassword</N>
<V>myPassword</V>
</P>
</O>
</ParameterList>
But, when I load it into OBi, only AuthUserName is accepted, while AuthPassword is always discarded. Why is that? Do they changed the name of the latter variable?
How to include passwords within configuration files now?
Navigation
[0] Message Index
[#] Next page
[*] Previous page