obi202 OutboundCallRoute issue

[ziggggy]

I am having an issue where 911 is not being routed properly on phone port 2 to sp1.

I have 2 DIDs with voip.ms and I have set up sp1 to use DID 1 and sp2 to use DID 2. I also set up phone port 1 to use sp1 and phone port 2 to use sp2. I only have 911 service on DID 1 (sp1) so I added an outbound call route on phone port 2 to redirect 911 to sp1. To test this, voip.ms has a 911 test number (555-555-0911) so I added an outbound call route for that as well. What I found is that when I dial the test number on phone port 2, it goes out through sp2 and not sp1. I believe I set it up correctly, but I can't figure out the issue.

Code Select Expand

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))

OutboundCallRoute
{911:sp1},{5555550911:sp1},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<#:>):ph1},{(<**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}

CallReturnDigitMaps
{pli:(xx.)},{sp1:(<**1>xx.)},{sp2:(<**2>xx.)},{sp3:(<**3>xx.)},{sp4:(<**4>xx.)},{bt:(<**8>xx.)},{bt2:(<**82>xx.)},{pp:(<**9>xx.)}

PrimaryLine
SP2 Service

[drgeoff]

Have your changes to the OutboundCallRoute been actioned on the device itself?  Log in to the 202's IP address on your LAN and use the onboard GUI to have a look.

[ziggggy]

It appears to be

[azrobert]

Routing an outbound call is a 2 step process.
The Phone Port DigitMap validates the dialed number.
Rule (Mpli) will include the rules in primary line's DigitMap.
All SP digit maps contain rule "<1>[2-9]xxxxxxxxx", so the Phone digit map will prefix the number with a "1".
You need to check for an 11 digit number.
You can combine the 2 rules like this:
{911|15555550911:sp1}

[ziggggy]

ah! Maybe that is it. I will try when I am back home.

This is the digit map for ITSP A (voip.ms)

Code Select Expand


DigitMap
(*75xx|*xx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*]@@.)

I need to spend a little more time reading how this works. I am a software engineer, so it doesn't look terribly complicated. I also have a localphone account that I want to use for international calls and so I have to figure out how to route all international calls through that service.

[azrobert]

Assuming Localphone is on SP3, just add this rule:
{(011xx.):sp3}

Notice that 011xx. is enclosed in parentheses. With the parentheses the argument becomes a digit map and the x's will check for digits. Without, it will check for a literal x.

There is a varying amount of delay when the phone digit map processes the dialed number. When a dialed number matches a rule the ends with "x.", there will be a 10 second delay. The easiest way to correct this is to change the phone port long timer.
DigitMapLongTimer: 3

[drgeoff]

I think Localphone use the 00 prefix for international.  They certainly do for me in the UK and ISTR even for US people too.

[ziggggy]

Routing an outbound call is a 2 step process.
The Phone Port DigitMap validates the dialed number.
Rule (Mpli) will include the rules in primary line's DigitMap.
All SP digit maps contain rule "<1>[2-9]xxxxxxxxx", so the Phone digit map will prefix the number with a "1".
You need to check for an 11 digit number.
You can combine the 2 rules like this:
{911|15555550911:sp1}

Thanks for the help. This solved it! I read the digit map call tutorial and i have a much better understanding of how this works. I actually created a user defined digit map for this so I can reference it from both phone ports 1 & 2