I have a obi302 in a home with elderly people that get confused and call 911 claiming the craziest of stories. Long story short, the cops were not amused the first time, nor the second, third, or tenth time. So I modified the dial string to the following:
([36]11S0 |<911S0:**MYNUMBER**> | <9911S0:911> | (MNANPA))
MNANPA is a macro for standard 7 and 10 digit dialing. The first part of the 911 intercept works in that it calls me if someone dials 911. However, if someone dials 9911 it is supposed to call the real 911 in the case of an actual emergency. However, its calling me instead. Its like its re-evaluating the string like 911 was actually dialed.
Is there an easy way to force 9911 to call the real 911 without redirecting to **MY NUMBER**.
I'm assuming this is the ITSP A DigitMap:
([36]11S0 |<911S0:**MYNUMBER**> | 9911S0 | (MNANPA))
I'm also assuming you're sending 911 to SP1
Physical Interfaces -> Phone1 Port
Add the following to the beginning of the OutboundCallRoute:
{(<9:>911>):sp1},
If you want an explanation, ask.
Yes, please explain.
You took the brackets off the 9911S0. Does that do something different?
What stops it from reprocessing the 9911 into a 911?
I assume the {(<9:>911>):sp1}, is forcing it to SP1 somehow.
1st the Phone DigitMap validates the dialed number.
The last rule (Mpli) includes the primary line's DigitMap.
Number transformation can happen here.
If the number matches a rule, the Phone OutboundCallRoute routes the call.
Number transformation can also happen here.
During the Phone DigitMap processing, your rule <9911S0:911> will convert 9911 to 911.
The Phone OutboundCallRoute will see 911, not 9911.
<911S0:**MYNUMBER**> will change 911 to your number and then it is sent to SP1.
My rule 9911S0 will leave 9911 unchanged during phone DigitMap processing.
The OutbounCallRoute will see 9911.
Rule {(<9:>911>):sp1} will remove the leading "9" and route 911 to SP1.
Thanks. Got it saved and rebooted. Will try it tomorrow when I have a chance.