What's wrong with this pattern?
MichiganTelephone:
obiliving, thank you, that looks like what I was originally trying to do. I'll give it a try in a little bit and let you know.
MichiganTelephone:
Quote from: obiliving on February 09, 2011, 08:13:56 am
Back to what you wanted to do. You don't care about who's calling (from OBi's point of view); you only want to check if a 11-digit number is called and let it go to sp1. Here is 1-way I can think of:
{>(1xxx xxx xxxx):sp1}, {>(<ob> xxx xxx xxx):pp}
Note how the second rule pre-pend the 9-digit number before sending it to pp (OBiTALK) trunk.
Please give it a try and let us know how it goes.
That appears to be working exactly as I wanted it to. ;D I assume the spaces are optional, correct? Anyway, thank you very much for clarifying this. This unit has some very advanced routing capabilities but understanding how to actually use them can be a bit of a challenge (well, at least for me, but then again I'm not always the brightest bulb on the tree!)
obiliving:
Space is legal and optional in digit maps and call routing rules; added just to
make it more readable.
One last comment...
In the general peering syntax: some-caller > some-callee,
the '>' is optional if 'some-callee' is empty (i.e., any called number) for InboundCallRoute.
In other words, without '>', the argument (if not empty) is treated as the caller-number.
In most cases you only specify the "some-caller" party without the '>'.
OutboundCallRoute for PHONE Port and AA, on the other hand, has very similar syntax but
you only specify the 'some-callee' part without the '>'.
MichiganTelephone:
Thank you again, obiliving. That helps my understanding of this quite a bit. I've added a link to this thread from my article (revised again ::)) so that anyone else who wants to know how this works will be able to find it.
Navigation
[0] Message Index
[*] Previous page