Setting Obi200 - Digitmap
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:
Quote
demanding 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
Navigation
[0] Message Index
[#] Next page
[*] Previous page