911 and the Obi110...the search continues...
RonR:
Quote from: Dixon on March 19, 2011, 08:16:59 am
Where does that go? Can you post the whole sequence?
It's not critical where it goes. Here's the original unmodified OutboundCallRoute from the OBi Device Administration Guide:
Code:
{(<#:>|911):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
jayd4wg:
not sure what happened...i thought i just bricked my OBi...but i'm back up and running (wierd problem after firmware upgrade and trying to set my IP to a static address on the network. I will be NATing a port to the Obi box so i have remote admin ability.
First time thru, i set up GV and SG manually...THEN i found the online portal/configurator under the Add a Device link...MUCH easier to set up the secondary SP.
I will be implementing this (the 911 routing) on monday when verizon shuts down my POTS and reprovisions FIOS wiith internet and TV...reduced my total spend in the neighborhood of 50-75 bucks a month. I'll be testing with the PSAP as soon as I implement (coordinated with them of course) as my e911 will be going thru sipGate. guys, thanks for your help...
Dixon:
So is this correct?
{911:sp2},{(<#:>:li)},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}{(<**8:>(Mli)):li}
RonR:
Dixon,
Routes have to be separated by a comma. You added the **8 route on to the end without a comma to separate it from the **9 route.
You also misplaced the ')' in the second route. It should be:
{(<#:>):li}
Just for cosmetic sake, I think it's a little 'prettier' with the **? routes in numeric order, but it's functionally correct either way.
Dixon:
{911:sp2},{(<#:>):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
Forgot to fix this part. So this should be right?
Navigation
[0] Message Index
[#] Next page
[*] Previous page