Obi202 redirect 911 to 10-digit emergency number, won't work with **1, **2, **3
CoalMinerRetired:
I've been testing the configurations to redirect 911 to a local ten digit emergency number listed here:
http://www.obitalk.com/forum/index.php?topic=3440.0
and here:
http://www.obitalk.com/forum/index.php?topic=339.0
For calls direct dialed from the phone on Port 1 or 2, (i.e., pick up phone, dial 911) it works as expected.
However, when I dial **1 + 911, it doesn't work. Same results with **2, and **3. (I'm not using the 4th SIP slot).
When I dial **1 + 911, I hear a 'ring back' tone for a very small slice of time, let's say 50 to 100 ms. Then I get a fast busy that immediately cuts off the ring back sound. Looking at the SP1 packet stats, it looks like some data packets were sent out when this occurs.
Any ideas for how to make this work with **1?
jimates:
The phone ports call route needs an exact match to route the call. When you prepend to 911 you are by passing the 911 rule you have in place. Since the dialed numbers do match a rule farther down the list, it is routed to the appropriate spx and delivered as 911 exactly.
You would need to add a rule to the itsp digit maps to route the call from there.
(<911:1xxxxxxxxxx>|(Mste))
I have a 911 rule in place for the phone port. And I have a 411 rule in place in the itsp digit map. I made the changes to my 411 rule and tested, it works as you desire.
mjstallion:
I have an Obi202 also, and I don't see where I should insert the 911 rule. This is my Outbound call route:
{([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}
jimates:
you can put it right in front if you want. I usually just put it second since that is where it started out with the Obi110.
Physical Interfaces -> Phone X -> OutboundCallRoute
{([1-9]x?*(Mpli)):pp},{(<911:1xxxxxxxxxx>):spX},{(<#:>):ph2},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
when you dial just 911, the call route processes it and sends the alternate number to the designated SPX, where the alternate number is then processed by the local digit map and sent out as a 11 digit number.
This is my phone 1 outboundcallroute
{(Mabc):},{([1-9]x?*(Mpli)):pp},{(<911:1814xxxxxxx>):sp1},{(<#:>):ph2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
In addition if you want to support the **X911 possibilities, you would add this rule to each of the ITSP Profile X General -> General -> DigitMap
(<911:1xxxxxxxxxx>)
This is mine for all my ITSP profiles
(<411:18003733411>|(Mste)). So it would look like this
(<911:1814xxxxxx>|<411:18003733411>|(Mste)) or without the 411 rule, (<911:1xxxxxxxxxx>|(Mste))
Example:
When dialing **2911, the {(<**2:>(Msp2)):sp2} rule, in the phone outboundcallroute, strips the **2 from the digits and sends the remainder (911) to the SP2 trunk; (where it is then processed using the local digit map for the ITSP profile that is designated for SP2) and the designated alternate number is dialed using SP2.
Remember, you can designate any of the 4 ITSP profiles for each of the SPx trunks. For example, it doesn't have to be ITSP Profile A for SP1 etc.
You can use a different alternate number for each of the 4 trunks by prepending **X to 911, because when using **X only the local digit map processes it and applies the rule, not the 911 rule in the phone port call route.
So, dialing 911 from the phone might call the emergency call center using the alternate number but dialing **3911 coould call your cell phone.
mjstallion:
I copy/pasted that and it didn't work. OBI dashboard still says 911 not configured, and dialing 911 gives me an error message on the phone.
Navigation
[0] Message Index
[#] Next page