Help setting up call routes for OBi202
ianobi:
This may help with part of the TV project if it involves Android:
http://www.obitalk.com/forum/index.php?topic=10617.msg69876#msg69876
jadog:
Thanks! I'll check it out.
ProfTech:
To AZRobert; I see the OP got it working but I will just throw in a couple tidbits here. Trunk groups in the Obi are indeed "interesting". I won't go so far as to say they don't offer some extra capabilities but interesting none the less. I wanted to use a trunk group with my 110 as soon as I got it. I got it working the way I wanted but RonR sent me a different config that gave the same result. After analyzing what he sent I could see where some of the oddities were coming from. The default map setup in the 110 has adds/subtracts in the SP1/SP2 and Obitalk <ob>xxxxxxxxx, <1>[2-9]xxxxxxxxx slots. When using a trunk group, the Obi can make multiple passes through the sp slot in it's algorithm to build the final dial string. So it can get confusing quickly.
Anyway, I find it more intuitive [easier to keep track of what is going on] to put all of my "paste-ups" [adds/subtracts] in the phone port digit map instead of the ITSP Profile [A/B] DigitMap. The only thing I put in the trunk digit map is the correct/actual map for that trunk. According to the docs, the final place the Obi looks to see if it can route a call when a trunk group is involved is the sp digit map anyway.
You can also put paste-ups in the outbound call route if needed but I haven't found a need for it.
Navigation
[0] Message Index
[*] Previous page