Help understanding Outbound Call Routing

<< < (3/7) > >>

xpr722946ghd:
Quote from: azrobert on May 08, 2017, 06:47:11 am

Transformation happens when a dialed number matches a rule, so it can occur in either the Phone Port DigitMap or the OutboundCallRoute. In your case transformation takes place in the Phone DigitMap.

Perhaps this is the source of my confusion.

The Phone Port Digit Map reads as follows.
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli)|(Msp2))

It is not performing any transformation is it?  At least not on the UK numbers beginning with 01, 02, or 07.  That transformation happens in the ITSP A digit map which gets read later in the sequence.  Or is it performing a transformation at this stage because it is calling Mpli rules in the first statement?  And now that Msp2 is added at the end it is performing any transformation listed there?

drgeoff:
Quote from: xpr722946ghd on May 08, 2017, 03:48:42 pm

Quote from: azrobert on May 08, 2017, 06:47:11 am

Transformation happens when a dialed number matches a rule, so it can occur in either the Phone Port DigitMap or the OutboundCallRoute. In your case transformation takes place in the Phone DigitMap.

Perhaps this is the source of my confusion.

The Phone Port Digit Map reads as follows.
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli)|(Msp2))

It is not performing any transformation is it?  At least not on the UK numbers beginning with 01, 02, or 07.  That transformation happens in the ITSP A digit map which gets read later in the sequence.  Or is it performing a transformation at this stage because it is calling Mpli rules in the first statement?  And now that Msp2 is added at the end it is performing any transformation listed there?


When another map is referenced it acts like a sort of macro.  So, yes the (Mpli) in the phone port digit map is doing exactly the same transformations and matching as if the contents of Msp1 (=Mpli) had been typed into the phone port digit map.

And in the same way, (Msp2) is doing the same as if its contents had been typed into the phone port digit map.

xpr722946ghd:
Perhaps the penny is finally dropping!

azrobert:
Here is a solution to all your requirements. Hopefully, I didn't make any mistakes. Dial 10 or 11 digits for N. America. Routing for Canada is based on area code. I got the list of area codes from a Web site and did a cut and paste with some editing to create the digit map, so there shouldn't be any typos. I don't know if the list of area codes is accurate.
http://www.areacodehelp.com/canada/canada_area_codes.shtml

ITSP A DigitMap:
(011xxxxxxxxx.S3|<07:011447>xxxxxxxxx|<0:04444>[1-2]xxxxxxxxx|<44:04444>[1-2]xxxxxxxxx|04444x.|011447x.)

ITSP B DigitMap:
(911|933|1(403|587|780|825|236|250|604|778|204|431|506|709|879|867|782|902|867|226|249|289|343|365|416|437|519|548|613|647|705|807|905|782|902|367|418|438|450|514|579|581|819|873|306|639|867|600|622)xxxxxxx)

ITSP C DigitMap:
((0800|0808|0500)xxxxx.S3)

ITSP D DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx)

Phone DigitMap:
 ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli)|(Msp2)|(Msp3)|(Msp4))

OutboudCallRoute:
{(18(00|88|77|66|55|44|33)xxxxxxx):sp1},{(Msp2):sp2},{(Msp3):sp3},{(Msp4):sp4},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<#:>):ph2},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}

drgeoff:
There was different source of Canadian area codes in my post at http://www.obitalk.com/forum/index.php?topic=12671.msg81438#msg81438.

But:

1.  If they are different, is one correct or are they both incorrect?

2.  Even if they are the same, that still does not guarantee they are correct.

:)

Navigation

[0] Message Index

[#] Next page

[*] Previous page