Technical : DigitMaps and the OutboundCallRoute
plugger2:
Quote from: RonR on March 27, 2011, 10:57:34 pm
Your first example simply sends XXXXXXX out the SP2 port. No DigitMaps anywhere are evaluated. Of course it's accepted. The second example isn't valid. The terminal specifier has to be PH, AA, LI, SPx, or PP. It can't be a trunk group. I'm guessing the OBi simply ignored it.
OK, we are clearly not on the same page. The syntax above is valid, and it works as you would expect. OBi certainly does not ignore it. The call is directed to the trunk group, which is evaluated in order, looking for an available physical trunk, according to trunk group rules.
Try it and get back to me.
RonR:
plugger2,
You might want to do some reading on page 115 of the OBi Device Administration Guide (Version 23.03.11: 23 March 2011) under the heading of 'Outbound Call Route Configuration':
The general format is:
OutboundCallRoute := rule OR {rule},{rule},….
Note that the curly braces may be omitted if there is only one rule in the route. The OR operator is NOT part of the parameter syntax; it is used here to separate alternative values only.
A rule has the following format:
rule := callee-list : terminal
where
callee-list := callee|callee|callee| … (vertical bar separated list of 0 or more callee object)
callee := number OR embedded-digit-map OR @ (@ = any number)
terminal := PHx OR AAx OR LIx(arg) OR SPx(arg) OR PPx(arg) (arg object is optional)
The OutboundCallRoute sends calls to a terminal (port), not to another DigitMap or Trunk Group.
plugger2:
LOL. And you might want to do some reading on trunk groups, p76, paragraph 2 (my emphasis):
"Up to 4 trunk groups can be configured on an OBi device. Each trunk group is conceptually another trunk with its own DigitMap. A trunk group and its associated DigitMap are referenced using the short name TGn and (Mtgn) respectively, where n = 1, 2, 3, 4. They can be referenced in other digit maps and call routing rules so that calls may be routed to a particular trunk group."
Looks like OBi have to update the info on p115 to bring it up to date. :-)
RonR:
I think you're going to find that the syntax they're referring to is:
{(Mtg1):sp2}
although at this hour, I can't think of what this could possibly be good for (but it fits the syntax rules). :)
plugger2:
Quote from: RonR on March 28, 2011, 12:33:31 am
I think you're going to find that the syntax they're referring to is:
{(Mtg1):sp2}
although at this hour, I can't think of what this could possibly be good for (but it fits the syntax rules). :)
Nope. It's just what it says -- you can put tg1, tg2 in a routing rule, and it's treated just like any other trunk for routing purposes (except of course it will resolve ultimately to a physical trunk according to the rules as described -- unless of course there is no available physical trunk in the list with a "legal" digitMap for the call.)
The syntax above will work, as you say, but I can't figure out what it would be useful for, either. So we agree on something! ;-)
I suggest you try it out for yourself, and you'll see there is nothing ambiguous or mysterious about the paragraph on p76.
Edit: Oh, and BTW, the description of the list of acceptable terminals on p115 is also not up-to-date regarding voice gateways (vg1, vg2, ...). These can now also be used as terminals in routing rules. So there's two bugs in the p115 documentation we've uncovered in this thread alone. :-)
Navigation
[0] Message Index
[#] Next page
[*] Previous page