International calls via SP2

(1/4) > >>

VANJ:
How can I setup a digit map such that only international calls (starting with 011) are sent via SP2, all other calls are sent via SP1?

Ideally, even the 011 prefix is not necessary since all international calls (country code + number) are longer than 10-digit US numbers so if the digit map can automatically route all 10+ digit numbers to SP2 that would be fantastic.

Help? Thanks

azrobert:
I'm assuming your Phone Port primary line is SP1.

Service Provider ==> ITSP Profile B ==> General
Change DigitMap To:
(011xx.|xxxxxxxxxxxx.)

Physical Interfaces ==> Phone Port
Add to DigitMap after the beginning parenthesis:
(Msp2)|

and

Add to beginning of OutboundCallRoute:
{(Msp2):sp2},

Now any dialed number beginning with 011 or any number longer than 10 digits will be routed out SP2.
18005551212 will be routed out SP2.

If you use ITSP B DigitMap:
(011xx.|[02-9]xxxxxxxxxx|xxxxxxxxxxxxx.)
Now any dialed number beginning with 011, any number 11 digits long not starting with "1" or any number longer than 11 digits will be routed out SP2.

VANJ:
Quote from: azrobert on March 05, 2013, 08:09:10 pm

If you use ITSP B DigitMap:
(011xx.|[02-9]xxxxxxxxxx|xxxxxxxxxxxxx.)
Now any dialed number beginning with 011, any number 11 digits long not starting with "1" or any number longer than 11 digits will be routed out SP2.


Let me wrap my head around this. Yes, my phone port primary line is SP1. So here is what I want

1. 10-digit number - Prefix with 1 and send via SP1
2. 1 followed by 10-digit number - Leave it alone and send via SP1
3. 10+ digit number NOT starting with 1 - Send via SP2
4. Any number starting with 011 - Send via SP2

How can I do this? I am almost there but haven't quite mastered the syntax yet, appreciate the assist.

Thanks

azrobert:
I'm starting over.

Service Provider ==> ITSP Profile B ==> General
Change DigitMap To:
(011xx.|[02-9]xxxxxxxxxx|xxxxxxxxxxxxx.)

Physical Interfaces ==> Phone Port
Add to DigitMap after the beginning parenthesis:
(Msp2)|

and

Add to beginning of OutboundCallRoute:
{(Msp2):sp2},

Now any dialed number beginning with 011, any number 11 digits long not starting with "1" or any number longer than 11 digits will be routed out SP2.

Explanations:

In ITSP Profile B DigitMap:

011xx. will match any number beginning with "011".
[02-9]xxxxxxxxxx will match an 11 digit number beginning with 0,2,3,4,5,6,7,8 or 9.
xxxxxxxxxxxxx. will match any number longer than 11 digits.
Above matches will be routed to SP2 by rule {(Msp2):sp2}.

In ITSP Profile A DigitMap:

1xxxxxxxxxx will match an 11 digit number beginning with 1.
<1>[2-9]xxxxxxxxx will match an 10 digit number beginning with 2 thru 9 and prefix it with "1".
Above matches will be routed to SP1 by rule {(Mpli):pli}.
011xx. is in both profiles, but rule {(Msp2):sp2} is before (left) of rule {(Mpli):pli} and therefore international calls will not be routed out SP1.

Felix:
I take advantage that international numbers never start from 1, and have the following digitmap:

PHONE Port - OutboundCallRoute: {(Msp1):sp1},{(Msp2):sp2}
ITSP Profile A General - DigitMap: (1[2-9]xxxxxxxxxS0)

ITSP Profile B General - DigitMap: ([2-9]xxxxxxxxxxx.)

This way, numbers starting with 1 go through SP1 (Google Voice). I also use S0 to start dialing after 11 digits. Anything that starts with 2-9 and is at least 11 digits, goes to SP2 (Call with us doesn't require or allow any prefixes before the country code).

It doesn't cover your first use case. My dad prefers it that way; but you can add <:1>[2-9]xxxxxxxxx to the first rule: (1[2-9]xxxxxxxxxS0|<:1>[2-9]xxxxxxxxx)

And, to accommodate 011 (assuming it's optional), you can change Profile B to ([2-9]xxxxxxxxxxx.|011xxx.)

Note, that I didn't test the changes - so I am sure I made a typo somewhere!

Navigation

[0] Message Index

[#] Next page