News:

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

Main Menu

Trouble setting up GV & CallCentric for E911

Started by TonyZObi110, March 09, 2013, 06:52:26 PM

Previous topic - Next topic

TonyZObi110

Hello, I'm an OBi110 newbie.
I was able to set up GV on SP1 and CallCentric on SP2. My goal is to use GV for all inbound and outgoing and CallCentric/SP2 for 911 only.
I've tested both outgoing SP1/SP2 separately successfully by first setting Outbound settings > phone primary to SP1 and calling a test number and repeating with Outbound settings < phone primary set to SP2.
When I set phone primary to SP1 and dial 911 I get a busy signal. I expected 911 to be automatically routed through SP2/CallCentric.

I've set  OutboundCallRoute as follows but 911 still rings busy. Help!
{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

TonyZObi110

never mind.. I just needed to remove the 911 string from the digitMap regexp. so now DigitMap is
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

ianobi

911 is in this DigitMap for a reason:

Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

It means that as soon as you finish dialling the second"1" the whole 911 number is instantly matched and passed to the Phone Port OutboundCallRoute to be processed. This rule {911:sp2} Should have sent 911 direct to sp2 as was intended. By removing 911 from the Phone Port DigitMap you are now relying on a xx. rule in your Primary Line DigitMap to match the 911. This will introduce delays and changes to digit maps could stop it working altogether.

In summary, these two rules should work fine for you:

Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

Physical Interfaces > PHONE Port > OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}

If it's not working for you, then more testing to find the real problem is required. You could substitute 911 with 411 or 611 for testing purposes and check on your web page > Status > Call History to see how it is routing. Remember to change back to 911 after testing.

atraum

I'm currently setup with SP1 Google, SP2 Anveo & SP3 Callcentric.  Will be leaving Anveo soon and already have everything else good on Callcentric.  If I replace {911:sp2} in
OutboundCallRoute
{911:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}

with {911:sp3} will it now use sp3 for outgoing 911 calls or are there other items to change in the DigitMap configs?

ianobi

atraum,

The change you detail should work fine. As you have an OBi202, there are two Phone Port OutboundCallRoutes, so {911:sp3} needs to replace {911:sp2} in both of them.

atraum

ianobi - Thanks for your quick response, appreciate it!!