InboundCallRoute Explained
azrobert:
I helped a newbie with a setup and he asked for an explanation of how the InboundCallRoute worked. I thought answering the question in a separate thread might help others.
This is the route he asked about:
{pvpham>(Msp1):sp1},{101>17771234567:aa},{ph}
The above rules are use to make calls from an Android phone using CSipSimple softphone. The first rule uses Sip2Sip service to make single stage calls by bridging an inbound call out SP1. The second uses Callcentric to make calls via the AA.
Rules are processed left to right.
When a rule matches a call, it is immediately routed to the destination.
Each rule has 2 tests and the format is:
{test1>test2:dest}
You can optionally have only 1 test like this:
{test1:dest} or {>test2:dest}
If you have 2 tests, both tests must be true to get a match on a rule.
If a test is enclosed in parentheses it is a DigitMap.
If it is not enclosed it is a LITERAL.
Rule {123:dest} is testing for literal "123"
Rule {(1xx):dest} is testing for literal "1" followed by 2 digits
Rule {1xx:dest} is testing for literal "1" followed by 2 alpha "x"
If a test is in this format (Maaa) it uses the DigitMap of a trunk.
Rule {(Msp1):dest} uses SP1 DigitMap for the test.
The tests have different meanings depending if it's a normal inbound call or an inbound call initiated by a softphone/ATA meant to be bridged.
Normal Inbound Call:
Test1 is the CallerID of the inbound call.
Test2 is your UserID of the service provider.
{101>17771234567:aa}
Callcentric sends the extension number as CallerID when a sub-account calls the main account.
101 is the extension number.
17771234567 is your Callcentric UserID.
If both these match the call is routed to the Auto Attendant.
Inbound Call meant to be bridged:
Test1 is your UserID
Test2 is the outbound phone number.
{pvpham>(Msp1):sp1}
pvpham is your Sip2Sip UserID.
(Msp1) is using SP1 DigitMap to match on the dialed number.
If both tests are true the call is bridged out SP1.
If both rules fail to match, the call is routed to the Phone Port.
OneForTheTeam:
Great writeup. Can this be made into a sticky?
QBZappy:
Bookmark showing examples of X_InboundCallRoute:
http://www.obitalk.com/forum/index.php?topic=7352.msg47397#msg47397
Since we don't have access create our own stickies, the above mentioned forum sub heading can be used as a community sticky. We won't need to ask the moderators to post anything of interest in that thread. I have already included azrobert's excellent explanation in that bookmark. Anyone can post there and build up that bookmark. Try to copy examples that offer a short explanation.
azrobert:
I had a mental lapse and called this an explanation of an OutboundCallRoute. I fixed my error.
pvpham:
azrobert,
Thanks. It helps me to understand a little better. Those codes now look less intimidating.
Navigation
[0] Message Index
[#] Next page