This is heavy lifting. So far, I'm not happy with the process or the results.
The AA prompts were easy (or at least they were after I consulted my Admin guide -- why it's part of the firmware upgrade and not the settings restore, I'll never know). As for restoring the backed-up settings, that didn't go well.
As predicted, the passwords didn't come over. I could fix the
voip.ms SP, but not the GV. I even created a new device-specific google password (I have two-step verification on), but it didn't work. Out of options, I used the Obitalk configuration portal to reinstall GV, which went on to lunch all my settings as well as the
voip.ms.
I deleted the 202 from my Obitalk console, turned off all the autoconfig and obitalk stuff and reinstalled the config file from the 100.
GV still works, without a password. I know the process was changed, but it's excessively mysterious. Isn't it documented, anywhere? I just wish there was a way to do it without Obitalk being involved.
As for poorly documented things... Using the 202 to replace a 100 meant I was hooking the "Internet" port to my router to attach it to the 'net as a peer to everything else on the local intranet, like my computers. Unfortunately, the web configuration interface considers that "accessing via the WAN" and you have to enable it, which I could only find documented buried deep in the "Obi Device Administration Guide." It's not the most user-friendly document. (If anyone is paying attention, it not only NEEDS, it DESERVES an index.)
One item still unaddressed is what happened to my digit maps. There's stuff that clearly isn't working now. At the very least it looks like I'm going to have to manually cut and paste between the two, and/or revisit some obscure OBi-incantations I haven't thought about in years.
