Help with outgoing international call routing
dhobi:
I just got an OBI100 device, read through the manual and I'm having a hard time figuring out how to set up proper call routing. Here's my setup:
SP1 - default, want to use only for US calls
SP2 - want to use only for international calls as SP1 is too expensive for that
For international calls, I wan to be able to dial the following formats from the phone:
011 44 1234567 (where 44 is the country code and used just as an example here)
00 44 1234567
+ 44 1234567
Any of the above I want to be routed to SP2, in other words re-written as **2 00 44 1234567, so I need the following substitutions:
011 --> **2 00
00 --> **2 00
+ --> **2 00 (not sure I really need this plus format, but I'm curious if it can be done)
Could you please help with what changes I need to make and where? I'm not sure about "Phone DigitMap" and "Phone OutboundCallRoute", whether I need to use both of them in conjunction or only one is enough and if so which one.
Also where would I make this change? In the "Setup Wizard" on the device directly or is there a way to do it via the OBITalk interface?
I wish there was an easy wizard to do this as I'm sure it is a very popular scenario.
dhobi:
Is there a way to debug the rules, in other words simulate dialing without actually making the phone call just to validate the routing?
I'm thinking that the following OutboundCallRoute rule will do, though I can't test it at the moment:
{((00 | <011:00> | <+:00>)@.):sp2}
Am I on the right track here?
RonR:
I prefer to leave the PHONE Port DigitMap and OutboundCallRoute unaltered if at all possible and do the translations on the PrimaryLine's DigitMap. Try this:
Service Porviders -> ITSP Profile A -> General -> DigitMap:
(<1aaa>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|1xxxxxxxxxx|<**2>(011|00|+)xx.|<8835100>xxxxxxxx|8835100xxxxxxxx)
where aaa is your local area code.
Service Porviders -> ITSP Profile B -> General -> DigitMap:
(<+:00>xx.|<011:00>xx.|00xx.)
dhobi:
Nice solution. I didn't know that the primary line's DigitMap gets evaluated first, before the OutboundCallRoute rules. So what's the order?
1. Phone Port DigitMap
2. Primary Line DigitMap (SP1 in my case)
3. OutboundCallRoute
4. Selected SP DigitMap (SP2 in my case)
5. anything else?
I think your approach is a bit more complicated and more error prone for the future if for example I delete SP1 and replace it with a different provider. I'd have to remember to then re-add the rules.
Any reason why modifying the OutboundCallRoute is a bad idea or just a matter of preference?
RonR:
Dialing a number from the OBi PHONE Port involves two distinct stages of processing.
The first stage is a digit-by-digit evaluation of the number being dialed. Evaluation is done on the PHONE Port DigitMap only. All references to other DigitMaps must be made indirectly from the PHONE Port DigitMap. The Digit Map Processor (DMP) returns the dialed number when the best matching rule is found, with possible transformation being performed by that matching rule.
The second stage is an evaluation of the number returned by the DMP using the OutboundCallRoute. The first matching rule found determines which trunk the call is routed through.
There is a tight coupling between the design of the PHONE Port DigitMap and OutboundCallRoute as they typically share the same DigitMap rules. This is why one must use careful consideration before making any changes at this level.
Making changes to the DigitMaps which have been segregated to individual trunk configuration areas (but indirectly referenced from the PHONE Port DigitMap), keeps things organized and clear what rules are associated with each trunk and actually simplifies future changes.
Navigation
[0] Message Index
[#] Next page