Digitmap or OutboundCallroute to control what SP to use
Hortoristic:
Can someone explain the difference of ITSP Profile A > General > Digitmap or Physical Interfaces > Phone1 Port > OutboundCallRoute - what the differences are?
It seems for example when I want to make when I dial 01144 call out on SP2, I can use either way?
Wont both these methods make any number I dial with 01144 dial out on SP2? Is one way better than the other?
ITSP Profile A > General > Digitmap
(*xx|1xxxxxxxxxx|<1360>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|<**2>01144xx.|[^*]@@.)
Physical Interfaces > Phone1 Port > OutboundCallRoute
{<**2>01144xx.},{911:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
ianobi:
There is a basic difference between a DigitMap and an OutboundCallRoute.
The DigitMap decides what number format is acceptable to that ITSP Profile.
The OutboundCallRoute decides where a number is routed to.
Using your example, in this rule:
ITSP Profile A > General > Digitmap
(*xx|1xxxxxxxxxx|<1360>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|<**2>01144xx.|[^*]@@.)
<**2>01144xx. says if you dial a number beginning 01144xx, then prepend that number with **2. This rule does not send the call anywhere.
In this rule:
Physical Interfaces > Phone1 Port > OutboundCallRoute
{<**2>01144xx.},{911:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
{(<**2:>(Msp2)):sp2} says if a number begins with **2 and matches the DigitMap for Msp2, then remove the **2, then send the call out via Service Provider 2. Again the rule {<**2>01144xx.} would not send the call anywhere.
It is useful to imagine the DMP (Digit Map Processor) making two passes. First it passes the number you dialled through all of the DigitMaps finding the best match, then doing any indicated transforming such as prepending **2. Second it passes that transformed number through the OutboundCallRoute Looking for a matching rule, which may do more transforming, such as removing **2, then sending the call out to the relevant service provider.
Using the more simple example of an Obi110 RonR explained that there is really only one big Phone Port DigitMap and one big Phone Port OutboundCallRoute. Both of these reference to other DigitMaps, Msp1, Msp2 etc, so if we change Msp1 we are changing the overall Phone Port DigitMap and overall Phone Port OutboundCallRoute.
I believe the above still holds true for the Obi202 Phone Port DigitMap, but it may have two Phone Port OutboundCallRoutes.
It is possible to put routing rules directly into the OutboundCallRoute, but this would soon become very messy and hard to control. Hence the Obi modular way of using what appear to be separate DigitMaps for each Service Provider / trunk.
There are other considerations such as how the Primary Line affects routing and trunk groups, but let’s leave them be for now :)
I recommend reading the first post here:
http://www.obitalk.com/forum/index.php?topic=513.msg3001#msg3001
Do not read the rest, it gets very confusing ::)
Ostracus:
Quote from: ianobi on September 30, 2012, 02:04:19 am
I believe the above still holds true for the Obi202 Phone Port DigitMap, but it may have two Phone Port OutboundCallRoutes.
It does.
Phone 2:
Code:
{911:sp3},{([1-9]x?*(Mpli)):pp},{(<#:>):ph1},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Phone 1:
Code:
{911:sp3},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Trivial differences though.
ianobi:
yes, I see the # is dealt with differently to allow the phones to call each other.
On reflection, I think the OBi202 must have one big DigitMap for phone1 and a separate big DigitMap for phone2. This would be needed to allow for each having its own Primary Line. Although both would contain the same trunk DigitMaps (Msp1,Msp2 etc,) you could allocate different routings to get to each trunk DigitMap. It would be perverse, but you could use **1 for Msp1 in phone1's Digit map and **7 for Msp1 in phone2's DigitMap.
In this respect I guess the OBi202 is really just two OBi100's bolted together.
Hortoristic:
You said both of my examples won't make a call that is dialed on SP1 as 01144, and redirect it via SP2 - I'm seeing odd results when I put the <**2>01144xx. in the ITSP Profile A -> General > Digitmap setting.
It really does seem to be dialing out SP2 when I dial the UK number from SP1, in call history it shows:
From PH1 To SP2(011441903300093)
So changing the digitmap in ITSP seems to have been the right place -
Quote
ITSP Profile A > General > Digitmap
(*xx|1xxxxxxxxxx|<1360>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|<**2>01144xx.|[^*]@@.)
In my call history, when I dial a UK number begging with 01144, my history shows: From PH1 To SP2(011441903300093) - so it really does seem to be dialing my call out on SP2.
<**2>01144xx. says if you dial a number beginning 01144xx, then prepend that number with **2. This rule does not send the call anywhere.
Quote
Physical Interfaces > Phone1 Port > OutboundCallRoute
{<**2>01144xx.},{911:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
{(<**2:>(Msp2)):sp2} says if a number begins with **2 and matches the DigitMap for Msp2, then remove the **2, then send the call out via Service Provider 2. Again the rule {<**2>01144xx.} would not send the call anywhere.
Navigation
[0] Message Index
[#] Next page