DigitMap rules in ITSP B not working in ITSP A
azrobert:
Quote
Just curious, why not simply add (Msp2) to Phone DigitMap?
I think you meant (Msp1) since (Msp2) is you primary line.
Good question. It shows you are thinking. In most cases you can add (Msp1), but you might get in trouble when transforming numbers and your setup will. When you transform a number in the phone DigitMap, the OutboundCallRoute will see the transformed number, not the original dialed number.
When you dial 211 it is transformed to 14163974636 and will not match (Msp1) in the OutboundCallRoute. It will match (Mpli) and be routed to SP2.
Quote
In fact, why is Mpli included and not Msp1-4?
Msp1-4 are include in the DigitMap and OutboundCallroute, but with the **1-4 prefix. To include these in the DigitMap without a prefix wouldn't accomplish anything without rules in the OutboundCallRoute. All the default ITSP DigitMaps are the same, so to include these in the OutboundCallRoute without a prefix will take precedence over the primary line rule and route the call to the wrong trunk.
ProfTech:
The way(s) the Obi digit maps process calls can be a bit curious but you are correct, {(Mpli):pli} does not have to be in the outbound call route. It's use there merely simplifies things in certain cases. I like to put all "paste ups" like your <611:14164772010> in the phone port digit map. Then in the service provider map put exactly what is acceptable [and what you want to be used] for that provider. What is in the sp map isn't used by the Obi at all unless A:the service provider is part of a trunk group or B: you reference it in either the Phone map or Outbound call route or C:the sp is the primary service provider [this is why I don't put paste ups in the sp map]. Trunk groups are a whole different subject.
A simple example:
Phone Map: (911|<611:14164772010>|1[2-9]xx[2-9]xxxxxx) - allows you to dial 911, 611[replaces it with 14164772010, and standard 11 digit dialing beginning with 1.
sp1 map: (1[2-9]xx[2-9]xxxxxx)
Outbound call route: {911:sp1},{1[2-9]xx[2-9]xxxxxx:sp1}
IF sp1 is the primary line then:
Outound call route could also be {911:sp1},{(Mpli):pli} (we are referencing what we put in the sp. field)
Note that 911 isn't specified in the sp1 map. It isn't required but can be there for clarity. The outbound call route has control. If the Obi sends something that is "illegal" to the sp the sp will respond with some sort of error.
Important note : The outbound call route is processed in left-to-right order. That is why 911 is listed by itself and is first. Consider this Outbound call route:
{911:sp3},{14172234567:sp2},{1[2-9]xx[2-9]xxxxxx:sp1}
14172234567 falls in the map for sp1 but since it is first in the order it will be sent to sp2. Everything else gets sent to sp1.
This last note allows you to send certain numbers or groups of numbers to a specific service provider without dialing **2,**3, etc as is the default in the Obi. The first match wins.
illicit:
Thank you both for the informative replies.
I setup our Linksys PAP2T NA back when I was beginning high school. Configuring it was a pain as I barely understood how it worked.
Now that I'm past uni, and using an Obihai I'm beginning to understand more how digit maps and routing work. They're no longer random numbers that I'm copy pasting & mixing matching from random threads LOL.
Configuring has now gone from being a chore to actually quite fun. I can make complex rules and look forward to doing more with the device.
Oh how far VoIP has come for me, it's been almost a decade since I switched over.
Is there anything else you 2 could suggest doing to get more out of the Obihai? I use FreePhoneLine for CAN calling and Google Voice for US & international. What more can I do with this nifty piece of tech?
ProfTech:
It's kind of a broad statement but I like to put everything into Notepad before ever trying to put it into the Obi. Then after looking at the whole picture I sometimes can say, I can simplify by doing this... a little differently. I usually list the ITSP map first
ITSP map nnnnnnnn - this is what is valid for the service provider.
then the phone map has to look like this yyyyy in order to be able to dial and/or transform certain numbers
lastly the outbound call route to make it all happen.
I mostly use the default maps to show me the correct syntax not specifics. The downloadable admin guide is very helpful when learning also.
azrobert:
Quote from: illicit on September 04, 2017, 02:31:58 pm
What more can I do with this nifty piece of tech?
I use a free service to make tollfree calls. GV doesn't work with some tollfree numbers. Actually, GV will not work with any number that uses early media.
You can have failover when a trunk is down. If freephoneline is down, you can automatically route Canadian numbers to GV and possibly visa versa. You would use a Trunk Group to accomplish this.
Navigation
[0] Message Index
[#] Next page
[*] Previous page