Look, I respect your interest in learning. I know you want to try to make something out of your OBi, but you've now been at this for four days since your first post in this discussion topic. Let me please just offer some perspective:
The OBi 202 can do lots of tricks, but it is challenging to learn the many quirky ways required to "program" it. It's not as powerful as Asterisk (PBX). The 202 isn't suited to be a "collector/distributor" in and out, when managing multiple (>2) destinations. Routing all your calls from one OBi to another places a dependency on that first OBi. If you are out of town, as you mentioned, with the 1022, depending on the 202 to work, but there's a power outage, internet problem, etc. at the 202's site, then you are SOL.
I could have gotten this running in 10 minutes or so, after first setting up working ITSP extensions or sub-accounts (Granted, your ITSP and their support resources seem to blow in that regard).
The easiest, most reliable, and technically simple solution is to manage the extensions at the ITSP. Local-based PBXing is ok, if you want a hobby, but, considering the advances in cloud-based VoIP telephony, it's outdated and a waste of time.
With just a bit of annoying form-filling, you could switch to, for example, Callcentric, set up as many extensions as you need, and quickly set up "call treatments" to route inbound calls to whichever SPs on whichever OBi devices you control. You can have up to fifty-one (!) extensions, at no extra charge. That means, you can do what I have done: clone inbound call handling behavior of four DIDs to three OBi devices, a wireless IP phone system, and even a simple ATA running a 1947 Western Electric 302 rotary dial phone.
Drgeoff and I do get bitchy some times, but we do have a lot of experience, and I don't shy away from telling a poster that they're wasting their time on a proposed solution.