News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Setting Obi200 - Digitmap

Started by boon1, December 05, 2014, 10:07:11 AM

Previous topic - Next topic

boon1

Hi,

I'm newbie on Obi200. I've googled for information related to setting up the OutboundCallRoute, DigitMap and X_InboundCallRoute. I've tried and not successful.

Here is what I tried to accomplished.

1) Using Freephoneline to make all Canadian calls as well as [1800#,1866#...] and redirect using SP1 (Primary)

2) Using GV on all US calls redirect using SP2

3) Block some 'unwanted telemaketeers #' and '1900xx' calls

Note: Item #1 and #2 above are working for now. Item #3 is not working

Below are the setup which I've made based on my research. Some of it I do not know the meaning at all  ;D . Please advise as I know something is missing here.

Physical interfaces - PHONE 1 - OutboundCallRoute
{(Mcanada):sp1},{(Musa):sp2},{(*98|911|933):sp1},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**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}

Voice Services -> SP1 Service -> X_InboundCallRoute
Voice Services -> SP2 Service -> X_InboundCallRoute

{(MTelemarketers)|?:},{ph}

User Settings - User Defined DigitMaps
Label: canada
DigitMap: (<1:>905xxxxxxxS0|<1:>289xxxxxxxS0|<1:>647xxxxxxxS0|<1:>416xxxxxxxS0|<1:>519xxxxxxxS0|<1:>613xxxxxxxS0|<1:>705xxxxxxxS0|<1:>807xxxxxxxS0|<1:>011xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55)xxxxxxx|!1900xxxxxxx)

Label: usa
DigitMap: (860xxxxxxx|407xxxxxxx|1[2-9]xx[2-9]xxxxxx)

Label: nocalls
DigitMap: (!1900xxxxxxx)

Label: Telemarketers
DigitMap: (?|x|xx|xxx|xxxx|xxxxx|xxxxxx|4161111111)


Thank you
Boon



azrobert

#1
Label: Telemarketers
DigitMap: (?|x|xx|xxx|xxxx|xxxxx|xxxxxx|4161111111)


GV sends an 11 digit Callerid, so use 14161111111 or 1?4161111111
x|xx|xxx|xxxx|xxxxx|xxxxxx| are used to block SIP Scanners.
GV does not use the SIP protocol, so these are not needed for SP2.
You duplicated "?" in the user DigitMap and inbound route.

See: http://www.obitalk.com/forum/index.php?topic=8802.0
The SP you point the call at must be defined as SIP, so use SP1.

boon1

Thanks azrobert for the quick response.

Does that means I update the settings as the following?
ie.

Voice Services -> SP1 Service -> X_InboundCallRoute
{(MTelemarketers)|?:},{ph}

Voice Services -> SP2 Service -> X_InboundCallRoute
ph

Label: Telemarketers
DigitMap: (x|xx|xxx|xxxx|xxxxx|xxxxxx|1?4161111111)



I would also need suggestion on the followings: Are the parameters correct?

User Settings - User Defined DigitMaps
Label: canada
DigitMap: (<1:>905xxxxxxxS0|<1:>289xxxxxxxS0|<1:>647xxxxxxxS0|<1:>416xxxxxxxS0|<1:>519xxxxxxxS0|<1:>613xxxxxxxS0|<1:>705xxxxxxxS0|<1:>807xxxxxxxS0|<1:>011xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55)xxxxxxx|!1900xxxxxxx)

Physical interfaces - PHONE 1 - OutboundCallRoute
{(Mcanada):sp1},{(Musa):sp2},{(*98|911|933):sp1},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**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}

azrobert

#3
It looks good.

I don't know Freephoneline's callerid format, but if it's 10 digits
1?4161111111 will work for both SP1 and SP2.

{(*98|911|933):sp1} will work.
FYI when you enclose an argument in parentheses it becomes a DigitMap and you can use reserved characters like "x" and "?".
If you are only using literals you don't need the parentheses like this: {*98|911|933:sp1}
You didn't post your Phone Port DigitMap, but you should include "*98|933|".
"911" is already in the default PP DigitMap.

{**0:aa},{***:aa2} are defaults and will work.


boon1

Hi azrobert,

Quote from: azrobert on December 05, 2014, 01:59:06 PM
.....
You didn't post your Phone Port DigitMap, but you should include "*98|933|".
"911" is already in the default PP DigitMap.
......

I'm using the following:-
Service Providers --> ITSP Profile A General --> DigitMap
(*xx|911|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)


Any idea the one in red would work for below digitmap? What I try to accomplished is that if I dial 211, it'll automatically dial 18883411001.

User Settings - User Defined DigitMaps
Label: canada

DigitMap: (<1:>905xxxxxxxS0|<1:>289xxxxxxxS0|<1:>647xxxxxxxS0|<1:>416xxxxxxxS0|<1:>519xxxxxxxS0|<1:>613xxxxxxxS0|<1:>705xxxxxxxS0|<1:>807xxxxxxxS0|<1:>011xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55)xxxxxxx|!1900xxxxxxx)

azrobert

First, I want to make a suggestion.
I like to remove unused code because it can only cause problems.
I would remove the following from the ITSP Profile A/B DigitMap:
xx. - This will match 1 or more digits. If the dialed number only matches this rule you will get a 10 second delay before the call is routed. It can also cause a 2 second delay with numbers that match another rule.
(Mipd) - This will match a dialed IP address. Most people do not need this rule.
[^*#]@@. -  This is intended to match a URI. Again, most people do not need this rule.

You still didn't post the Phone Port DigitMap, so I think you don't understand its significance.

When you dial a number the Phone Port DigitMap validates the number. The ITSP DigitMaps only come into play if they are referenced by the PP DigitMap. If the number matches a rule in the PP DigitMap it is passed to the PP OutboundCallRoute.

This is the OBI200 default PP 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))

(Mpli) points to the primary line DigitMap. The default primary line is SP1, so the ITSP A DigitMap will be included with the PP DigitMap.

Now to answer your question.
211 and 311 will not match any rules in the Phone Port DigitMap, but they will match rules xx. or [^*#]@@. in the ITSP A DigitMap. Since these rules are open ended (will match 1 or more digits) there will be a 10 second delay.

{(Mcanada):sp1} should transform the number and route the call like you want.

If you remove the rules like I suggest above and change the PP DigitMap to:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|211|311|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))

Now when you dial 211 or 311 there will be a 2 second delay instead of 10 seconds.
When you dial 10 or 11 digit numbers there will be NO delay instead of 2 seconds.




azrobert

#6
I see a couple of mistakes in your code, but they are not causing any problems.

When the Phone Port DigitMap processes the dialed number, <1>[2-9]xxxxxxxxx will change a 10 digit number to 11 digits BEFORE it's passed to the Phone Port OutboundCallRoute.
You will never get a 10 digit number passed to the outbound route (because it's been changed to 11 digits), so rules 860xxxxxxx and 407xxxxxxx in (Musa) will never match a dialed number.
This is not causing a problem because rule 1[2-9]xx[2-9]xxxxxx will match the number.

The S0 suffix in (Mcanada) will not do anything. You can only override the timer with rules in the Phone Port DigitMap. I'm assuming you are not referencing (Mcanada) in the Phone Port Digitmap.

If you  follow my instructions in my previous post you will have no delay on 10 and 11 digit numbers.

azrobert

The following is how I would code your outbound configuration. I removed ALL unused code. You can use all, some or none of this code. I apologize if I missed something.

Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.|1011xx.|**0|***|222222222)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp2):sp2}

Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(905|289|647|416|519|613|705|807)xxxxxxx|(905|289|647|416|519|613|705|807)xxxxxxx|<1:>011xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (860xxxxxxx|407xxxxxxx|1[2-9]xx[2-9]xxxxxx|011xx.)

The Phone Port DigitMap will validate rules for all trunks. Nothing is changed in this DigitMap.
I eliminated the User Defined DigitMaps canada and usa.

You can now dial 10 or 11 digit Canadian numbers.
I assume you want to dial 1011........ to route international calls to SP1 and 011....... to SP2.

boon1

Quote from: azrobert on December 06, 2014, 08:09:12 AM
The following is how I would code your outbound configuration. I removed ALL unused code. You can use all, some or none of this code. I apologize if I missed something.
.....
Please don't apologize if you missed something. I should apologize for asking too many 'dumb' questions  ;D

Yes, all the outbound configurations are working!!!! thanks!!!

Quote from: azrobert on December 06, 2014, 08:09:12 AM
....
This is the OBI200 default PP 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))
.....
Finally I found the Phone Port DigitMap (Physical Interfaces >> PHONE 1 >> DigitMap) and yes, the PP Digitmap on my Obi200 is the same as what you've posted

Quote from: azrobert on December 06, 2014, 08:09:12 AM
.....
Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.|1011xx.|**0|***|222222222)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp2):sp2}
.....
Sorry for my ignorance. What is the "222222222" for ?


Lastly (hopefully :D) I've 2 more questions which I need help. I've tried many ways but still not successful.

1) How can I prevent from dialling certain numbers ? eg. "1900" calls or any specified numbers?

2) How can I configure for the inbound configurations (ie for blocking calls) ? How should I configure that.

drgeoff

#9
You should have a quick read of http://www.obitalk.com/forum/index.php?topic=9104.0 and bookmark it for future use when azrobert isn't on hand to give you a speedy reply.  :)

That tutorial is hot off the press so don't feel ashamed that you didn't notice it earlier.

azrobert

222222222 is the OBi echo test.
It is routed to pp which is the OBiTalk network.
You coded blocking 1900 calls correctly, but you put them in the wrong place.
It must be in the Phone Port DigitMap.
I've included it in my example above.
I think you were blocking inbound calls by CallerID correctly.
We are going out for dinner now, so I don't have time.
I'll be back in a few hours.

boon1

Quote from: drgeoff on December 06, 2014, 04:38:08 PM
You should have a quick read of http://www.obitalk.com/forum/index.php?topic=9104.0 and bookmark it for future use when azrobert isn't on hand to give you a speedy reply.  :)

That tutorial is hot off the press so don't feel ashamed that you didn't notice it earlier.

Hi drgeoff, thanks for the links. I think I came across this link before but I do not understand most of it. Anyway, will read more and do more research  ;D

boon1

#12
Quote from: azrobert on December 06, 2014, 04:50:09 PM
222222222 is the OBi echo test.
It is routed to pp which is the OBiTalk network.
You coded blocking 1900 calls correctly, but you put them in the wrong place.
It must be in the Phone Port DigitMap.
I've included it in my example above.
I think you were blocking inbound calls by CallerID correctly.
We are going out for dinner now, so I don't have time.
I'll be back in a few hours.


Hi azrobert, the blocking of inbound calls by CallerID seems to be working. The incoming call would go to VM directly. As for 1900 calls, it seems to be working as when 1900 is dialed, it would route to SP2 which is my GV and prevent it from dialing out.

Thanks for all your help!!! Hope you had enjoyable dinner. ;D

As of now, everything I hope to accomplish are fulfilled.
1) Canadian # routed to SP1
2) US # routed to SP2
3) International calls - updated the DigitMap and use 011 routed to SP1
3) Inbound calls - Blocked (tested with 1 # only. Need to see if more # are coming)
4) 1900 - prevent this # from calling out

GAKW

I just got my obi200 and trying to configure my device. I am trying to setup in the following way:
1. Canadian and local numbers, 911, VM through freephoneline.ca SP1
2. USA numbers through GV SP2
3. international numbers through localphone.com SP3
I already have all the accounts.

This is what I am thinking

Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.|1011xx.|**0|***|222222222)

OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp2):sp2},{(Msp2):sp2},{(Msp3):sp3}
>> Added sp3,

Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(905|289|647|416|519|613|705|807)xxxxxxx|(905|289|647|416|519|613|705|807)xxxxxxx|<**1:>xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
Remove manual 1011 dialing, added **1 dialing

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (860xxxxxxx|407xxxxxxx|1[2-9]xx[2-9]xxxxxx|<**2:>xx.)
Remove manual 011 dialing, added **2 dialing

Service Provider -> ITSP Profile C -> DigitMap:
DigitMap: (<00>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx)|<011:00>xx.|<**3:>xx.)
Added this entry. Intention is that international calls preceeded by 011 or 00 like SP3 (but localphone only likes 00). Also SP3.

My obi200 is 2 days old and this is my first attempt at setting this up. Appreciate your comments.

azrobert

#14
I'm impressed! You use the exact same coding method as I do. Validate the dialed number in the phone digit map without changing anything then use separate rules in the outbound route. This is your 1st try configuring your OBi. It took me a long time to evolve to this method. You must be a programmer or had experience with dialplans.

Anyway, I just found a couple problems with your code. One isn't really a problem. You duplicated SP2 in the outbound route. The only real problem I found is you didn't validate the "**n" numbers in the phone digit map, so they will be rejected. Add "**[1-3]xx.S3" to the phone digit map.

If you want to eliminate some code see:
http://www.obitalk.com/forum/index.php?topic=8208.0

You don't have to use Trunk groups for failover, use it just to route calls.
Your outbound route will look like this:
{**0:aa},{***:aa2},{(Mtg1):tg1}

Your Trunk Group will look like this:
Trunk List: pp,sp1,sp2,sp3
DigitMap: (Mph)

I suggest getting your example working then try the trunk group if you want.  

Edit:
You are validating "1011xx." in the phone digit map, but I don't see where it's used in the ITSP digit maps. Maybe I'm just blind.

GAKW

@azrobert - Thanks. I reuse all your code since I was recommended that you were the expert (and this is a good way to begin when I have no idea what I am doing). Apologies for my lack of etiquette and not indicating the original source (long day at work and then demanding wife trying to get me of the computer  :-[

This is the new version of the entries
Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.|**0|***|222222222|**[1-3]xx.S3)
>> Removed 1011 that I dont use. Added **[1-3]xx.S3

OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp2):sp2},{(Msp3):sp3}
>> Removed duplicated SP2. For now not simplifying more.

Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(905|289|647|416|519|613|705|807)xxxxxxx|(905|289|647|416|519|613|705|807)xxxxxxx|<**1:>xx.|<211:18883401001>|<311:4163922489>|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
No change from last post

Service Provider -> ITSP Profile B -> DigitMap:
DigitMap: (860xxxxxxx|407xxxxxxx|1[2-9]xx[2-9]xxxxxx|<**2:>xx.)
No change from last post

Service Provider -> ITSP Profile C -> DigitMap:
DigitMap: (<00>(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx)|<011:00>xx.|<**3:>xx.|<**3011:00>xx.)
Added transformation for localphone international long distance when dialing **3011etc to 00etc

Let me know if you spot any issues.
Something I dont understand well.
What happens if I dial an usa/canada area code that is not defined in the table? what is the significance of many, many usa area codes or canada area codes not been included?

azrobert

Quotedemanding wife trying to get me of the computer
I know what that is like. LOL

After a number is dialed the Phone Port DigitMap gets control.
If the number matches a rule it is validated and it is passed to the OutboundCallRoute.
If the number doesn't match a rule, it will fail and you will get a Busy tone.

The DigitMap analyses the number as it's being dialed.
If the dialed number matches rule "011xx." there will be a 10 second delay.
"x." will match zero or MORE digits.
The DigitMap doesn't know if you are going to dial additional digits, so it waits.
Change the rule to "011xx.S3" and the delay will be 3 seconds.
You need a delay.
This delay only occurs in the Phone Port DigitMap processing.

OutboundCallRoute:
Processing moves left to right.
If the dialed number matches an ITSP DigitMap it is routed to the specified destination and processing stops.
If the dialed number doesn't match any ITSP DigitMap, you will get an IVR message something like "No routes available".
If the Phone Port DigitMap was coded correctly you should never get this message.

905|289|647|416|519|613|705|807 numbers with or without country code will be routed to SP1. Country code will be removed.

860 and 407 numbers plus all other 11 digit numbers not included in the SP1 list, will be routed to SP2.
1[2-9]xx[2-9]xxxxxx will match any 11 digit number.

10 digit numbers not included in the SP1 list, will be routed to SP3.
<1>[2-9]xxxxxxxxx will match any 10 digit number and add a "1" prefix.
<00> will also add a "00" prefix.
1xxxxxxxxxx will NEVER be used because 11 digit numbers will be routed to SP2.
This is probably a mistake.

I make plenty of mistakes and typos.
The best way to proceed is just try the above configuration and see what happens.
You can't break anything.
The worst that can happen is the call will be routed to the wrong provider.
Look at the OBi Call History to make sure the call was routed correctly.

To access Call History:
Log directly into the OBi using the local interface.
Key the IP address of the OBi into a Web Browser.
Hit Enter
The UserID and default Password are both "admin".
Click Status on the left column.
Then click Call History.





GAKW

Thanks a lot to azrobert and boon1!!
After more reading and some testing, I think I understand a bit more. I also made some updates since there were some routing that was not working as i expected. This one is working as I intended :)
This is the new version of the entries for the record

Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.|00xx.|**0|***|222222222|**[1-3]xx.S3)
>> Adding 00xx. in case I want to use the default strange international localphone dialing prefix

OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp3):sp3},{(Msp1):sp1},{(Msp2):sp2}
>> Reorder this. Including specific rules first:
a. International (only if starts with 00, 011 and **3). Else
b. Canada (defined by a set of area codes). Else
c. USA. All NA numbering not included on above

I have specific rules for 

Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(236|604|778|250|905|289|647|416|519|613|705|807)xxxxxxx|(236|604|778|250|905|289|647|416|519|613|705|807)xxxxxxx|<**1:>xx.|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
Added more canadian codes, removed 211 and 311 since I am not sure what those are for (service I dont use) and the redirection was to number not local

Service Provider -> ITSP Profile B -> DigitMap:
(1xxxxxxxxxx|[2-9]xxxxxxxxx|<**2:>xx.)
Removed specific area codes. Any NA numbering could go here but hoping routing order resolves most canadian with sp1. Also as usual manual **2

Service Provider -> ITSP Profile C -> DigitMap:
(00xx.|<011:00>xx.|<**3011:00>xx.|<**3:>xx.)
Reverse order of **3011 and **3 alone since i think more specific should go first. Remove usa dialing (unless with **3)

@boon1, my phone is a "modern" cordless phone in which you type the number and then press "call" to dial. Do I still need the S3? Again it seem to be working just fine.
Thanks for your help again!

azrobert

If the dialed number matches a rule that ends with "x.", there will be a 10 second delay unless something has recently changed in the firmware.
You can use "00xx.S1" with your phone for a 1 second delay.
You can't use "00xx.S0" because the call will be prematurely routed as soon as the OBi received the 1st digit after "00".
The default for rules that don't end with "x." is a 2 second delay.

GAKW

Thanks azrobert for the explanation. I dont know i will connect an old style phone somewhere in the house so I will use S3.
Also, I disabled provisioning through obitalk and sw updates. Should I disabled ITSP provisioning?

Final Mapping for the record

Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.S3|00xx.S3|**0|***|222222222|**[1-3]xx.S3)
>>> Added S3

OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp3):sp3},{(Msp1):sp1},{(Msp2):sp2}
>>> Reorder this. Including specific rules first:
a. International (only if starts with 00, 011 and **3). Else
b. Canada (defined by a set of area codes). Else
c. USA. All NA numbering not included on above

Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(236|604|778|250|905|289|647|416|519|613|705|807)xxxxxxx|(236|604|778|250|905|289|647|416|519|613|705|807)xxxxxxx|<**1:>xx.|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
>>> List of local numbers and most used canadian codes.

Service Provider -> ITSP Profile B -> DigitMap:
(1xxxxxxxxxx|[2-9]xxxxxxxxx|<**2:>xx.)
>>>  Any NA numbering could go here but hoping routing order resolves most canadian with sp1. Also as usual manual **2

Service Provider -> ITSP Profile C -> DigitMap:
(00xx.|<011:00>xx.|<**3011:00>xx.|<**3:>xx.)
>>> International dialing with 00 or 011. Digit replacement to 00 for localphone