What about 911?? Your Obi can call a Local Emergency Number when you dial 911
jimates:
What about 911?
This question has come up many times, not only for use with the Obi but for everyday use with SIP services that do not provide 911 service. The Obi is flexible enough in it's features that we can compensate for that by having it dial any assigned number when we press 911 on the phone.
You can check with your local 911 center or local police dept. for a local 7 or 10 digit number you can call for emergency service. You can then create a rule for the Obi. When you dial 911, the Obi will call the other number instead of 911.
Make sure you get an EMERGENCY NUMBER, not the non emergency number, or just a number for a dispatcher. Make sure they understand what you NEED. You don't want some phone ringing on a desk while they clean the donut powder from their shirt before answering the phone.
Also, once you get the number and set it up you should make an appointment with the call center to "test" your setup.
That should provide the equivalent of 911 service, not E911. You will still have to give your information/address when calling but at least your call will be to the right place.
Make your Obi call a Local Emergency Number when you dial 911.
-- Managing from the device's web interface
These edits are made from the Obi Web Interface.
Dial * * * 1 from the phone connected to your Obi to get the IP address.
Enter the IP address in your browsers address bar to access the Obi's web interface.
If you want to manage your device from it's web interface you should turn off the Auto Provisioning. With Auto Provisioning on, the settings from the Obitalk Portal take precedence and any of those changes made from the web interface will be over written upon reboot of the device. You can't use both to manage your Obi.
When making changes from the web interface you must submit your changes by clicking "Submit" at the bottom of each page. You will be prompted to reboot after clicking "Submit". You do not have to reboot until after all of your selections have been made, but you must click "submit" before navigating away from each page.
From the Obi's web interface
System Management > Auto Provisioning > Auto Provisioning = Disabled
---------------------------------------------------------------------------
-- Managing from the Obi Expert Configuration at the Obitalk Portal
When making changes from the Obi Expert Configuration, you need to uncheck both the "Device Default" box & the "ObiTalk Settings" box. You must submit your changes by clicking "Submit" at the bottom of each page, before you navigate away from the page. You do not have to reboot the device, the device will automatically reboot after the submission on each page.
This configuration is only for the Obi110. There is another section below for configuration of the Obi100.
The default action of the Obi110 is for 911 calls to go out on the LINE port unchanged. This guide covers the 3 most common desired changes to the 911 setting.
This is the full default OutboundCallRoute for firmware 1.2.0 (Build: 2101), it may be shortened in the examples below.
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2}
,{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
A -- If your SIP provider has 911 service and you just need to direct 911 to the proper SIP line,
this edit will change the default action so 911 calls will go out on a designated SIP line.
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default call route
...,{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
edit the first rule to remove the default 911 routing - remove |911
...,{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
add the new rule - add {911:spX}, - substitute the desired sp designation (sp1 or sp2) for spX
...,{911:spX},{<#:>:li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
no spaces, and note the comma between the rules
.
B -- If you want to set it so that pressing 911 dials an alternate number, and sends the call out on a
designated SIP line, make this edit to the Phone's OutboundCallRoute
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default call route
...,{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
edit the first rule to remove the default 911 routing - remove |911
...,{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
add the new rule - add {(<911:1xxxxxxxxxx>):spX}, - (substitute your desired number for xxxxxxxxxx,
and the desired SIP line designation represented by spX)
...,{(<911:1xxxxxxxxxx>):spX},{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
no spaces, and note the comma between the rules
C -- If you want the call to remain going out on the LINE port but want it to dial an alternate number
instead of 911, you can make this small edit to the Phone's OutboundCallRoute.
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default call route
...,{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
edit to this - add the desired alternate number & the appropriate symbols (< > (<911:1xxxxxxxxxx>
substitute your desired number for xxxxxxxxxx
...,{(<#:>)|(<911:1xxxxxxxxxx>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2} .....
**Note: Pressing # on your phone's keypad will connect you directly to the LINE port.
From there you can place a 911 call normally, if you have service on that line that provides 911 service
Optional info for adding 411 to the Obi110
Step 1 - Add 411 to the digit map (without 411 added to the digit map you will get an extra 10 second dialing delay after pressing 411)
Setup Wizard > Outbound Settings > Phone DigitMap
default digit map
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
edit to add |411
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
Step 2 - Add the new rule to the OutboundCallRoute to dial a designated number when 411 is pressed
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default outbound call route
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1}
,{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
add {(<411:1xxxxxxxxxx>):spX}, - (substitute your desired number for xxxxxxxxxx,
and the desired SIP line designation represented by spX)
{(<411:!xxxxxxxxxx>):spX},{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1}
,{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
{(<411:18002464411>):sp1}, added to the front of the OutboundCallRoute will call "1800 BING 411" on SP1
Configuration for the Obi100
Since the Obi100 does not have a LINE port to use an existing PSTN based service you have to set it up to
dial out on one of the SP lines. The 911 reference already exists in the default digit map.
A -- If your SIP provider has 911 service, you just need to direct 911 to the proper SIP line,
this edit will set the action so 911 calls will go out on a designated SIP line.
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default call route
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
add the new rule - add {911:spX}, - substiture the desired sp designation (sp1 or sp2) for spX
{911:spX},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},...
no spaces, and note the comma between the rules
.
B -- If you want to set it so that pressing 911 dials an alternate number, and sends the call out on a
designated SIP line, make this edit to the Phone's OutboundCallRoute
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default call route
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
add the new rule - add {(<911:1xxxxxxxxxx>):spX}, - (substitute your desired number for xxxxxxxxxx,
and the desired SIP line designation represented by spX)
{(<911:1xxxxxxxxxx>):spX},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},....
no spaces, and note the comma between the rules
Optional info for adding 411 to the Obi100
Step 1 - Add 411 to the digit map (without 411 added to the digit map you will get an extra 10 second dialing delay after pressing 411)
Setup Wizard > Outbound Settings > Phone DigitMap
default digit map
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
edit to add |411
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|911|411|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(Mpli))
Step 2 - Add the new rule to the OutboundCallRoute to dial a designated number when 411 is pressed
Setup Wizard > Outbound Settings > Phone OutboundCallRoute
default outbound call route
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
add {(<411:1xxxxxxxxxx>):spX}, - (substitute your desired number for xxxxxxxxxx,
and the desired SIP line designation represented by spX)
{(<411:!xxxxxxxxxx>):spX},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
{(<411:18002464411>):sp1}, added to the front of the OutboundCallRoute will call "1800 BING 411" on sp1.
RonR:
jimates,
A couple of comments regarding the approach you took to substituting a local emergency number for 911:
1. The {911:sp1}, (or {911:sp2},) routes in the PHONE Port > OutboundCallRoute will never be used because '911' won't exist when the OutboundCallRoute is evaluated. '911' will have been replaced by '8145255040' by that time. If these routes were ever used, then '911' itself, not the replacement number, would be sent out SP1 (or SP2).
2. When the OutboundCallRoute is evaluated, it will be working on the number '8145255040', not '911'. Whichever port's DigitMap best matches '8145255040' will determine the port used, not the fact that '911' was replaced by '8145255040' in the SP1/ITSPA DigitMap. In your case, it's apparently going out SP1 as you want it to, but this may be an accident because your PrimaryLine is SP1 and it's actually matching the 'xx.' rule in your ITSPA DigitMap. This leaves a lot of uncertainty in what's going to actually happen when you dial '911' as you make changes to the ITSPA, ITSPB, and LINE DigitMap's or change your PrimaryLine in the future. In other words, this is a very fragile approach and is likely to get broken such that '911' may not go out the intended port.
An infinitely simpler and totally reliable approach is to leave all the DigitMap's as they were and simply do the substitution at the last minute in the OutboundCallRoute:
Default OutboundCallRoute:
{(<#:>|911):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}
New OutboundCallRoute:
{(<911:8145255040>):sp1},{(<#:>):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}
This guarantees that when you dial '911', the replacement number goes out the desired port.
jimates:
RonR,
At least I do test my configurations before I post them.
What you came up with does not work.
Why don't you help someone figure out the right way it should be, instead of telling them they are wrong, and then posting incorrect, unverified information that you say is right.
I am learning here. And will accept constructive criticism or help.
Did you look at the defaults or did you think I just came up with all that on my own. I took the default information and edited what I thought was pertinent. If 911 was in the call route or digit map pointing to li, then I tried to make it point to an sp.
Quote
1. The {911:sp1}, (or {911:sp2},) routes in the PHONE Port > OutboundCallRoute will never be used because '911' won't exist when the OutboundCallRoute is evaluated. '911' will have been replaced by '8145255040' by that time. If these routes were ever used, then '911' itself, not the replacement number, would be sent out SP1 (or SP2).
If the 911 references in the OutboundCallRoute won't ever be used, why were they there originally.
Quote
1. The {911:sp1}, (or {911:sp2},) routes in the PHONE Port > OutboundCallRoute will never be used because '911' won't exist when the OutboundCallRoute is evaluated. '911' will have been replaced by '8145255040' by that time. If these routes were ever used, then '911' itself, not the replacement number, would be sent out SP1 (or SP2).
911 isn't replaced with the other number until the ITSP DigitMap rule is processed. Doesn't the Phone Port OutboundCallRoute have to route the call to the correct ITSP (where I put the rule) before those rules apply?
I assumed the route rule would go in the OutboundCallRoute and the number would need to be in the DigitMap,. I figured that is why there were two place for the rules, one for routing rules and one for digit rules.
One thing you said is correct, the call goes out the ITSP that is set as primary. But only when other editing is in place.
The 911 rule in the Phone Port OutboundCallRoute must be removed or the call is sent to the LINE port. With no rule to send it to the LINE it defaults to the Primary ITSP. The 911 reference in the phone Port DigitMap could remain, but I saw no reason to leave it there.
I can have the ITSP DigitMap with the new rule in place for both ITSP's at the same time. With the call only going out the Primary line I kind of thought the same thing as you. But without removing the 911 reference from the Phone Port OutboundCallRoute that points 911 to the li, it fails. And trying to do it all in one place, like you did, does not work for me.
The call goes out immediately after the two second delay. Some variables did work but resulted in a delay varying form 10 to 20 seconds.
The only thing I need is a routing rule that forces 911 to the correct ITSP the same as it did to the li in the default. That way 911 can go out on the designated sp instead of the default.
Some people have a SIP provider just for 911. If they have that provider on the sp that is not the default, they will have to dial **2 911.
jimates:
I may be getting closer.
After using the call history to see which port it was going out on, instead of just assuming it wasn't working because of a failed call, I have it to where I can direct the call to either sp1 or sp2 no matter which is the default. But now it isn't processing my ITSP DigitMap rule for the alternate number.
My call history shows it goes out on the sp that I want. but now it shows it went out as 911
Before when I could only get it to go out the default, the call history showed it going out as the alternate number. Same DigitMap rule in the same place.
With call history showing that 911 passed through the ITSP and with this ITSP DigitMap (<911:8142489644>|1xxxxxxxxxx|<1814>[2-9]xxxxxx|011xx.|xx.)
I thought the first rule would process, and change 911 to 8142489644
But the Phone Port DigitMap must take priority and sends it out as is, without going through the ITSP rules.
this is what I have
Phone Port OutboundCallRoute
{911:sp2},{<#:>:li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
Phone Port DigitMap
([1-9]|[1-9][0-9]|**0|***|#|(Mpli)|**1(Msp1)|911|**2(Msp2)|**8(Mli)|**9(Mpp))
ITSP DigitMap
(<911:8142489644>|1xxxxxxxxxx|<1814>[2-9]xxxxxx|011xx.|xx.)
jimates:
I got it working using a combination of your setting and mine.
Phone Port DigitMap
default
([1-9]|[1-9][0-9]|911|**0|***|#|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
new
([1-9]|[1-9][0-9]|**0|***|#|(Mpli)|**1(Msp1)|911|**2(Msp2)|**8(Mli)|**9(Mpp))
Phone Port OutboundCallRoute
default
{(<#:>|911):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
new
{(<911:8142489644>):sp2},{(<#:>):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}
The ITSP DigitMaps can remain unchanged.
Navigation
[0] Message Index
[#] Next page