Obi202 redirect 911 to 10-digit emergency number, won't work with **1, **2, **3
jimates:
the dashboard is not going to show 911 as configured unless you do it with Obitalk using the settings from the accounts at the dashboard.
If you copied and pasted, did you change SPX to the correct trunk you wan to use; SP1, SP2, SP3 or SP4? Is there service on the designated trunk?
And did you replace the xxxxxxxxxx with the number you want to call when you dial 911?
With that calling rule in the digit map there is no reason it won't work.
Note, the other day when I did some pasting it only pasted the first line and not the whole thing. Make sure the full configuration gets in there.
CoalMinerRetired:
jimates, I followed what you posted, and to experiment did it with a variation using a User Defined Digit Maps, actually two different User Defined Digit Maps.
Physical Interfaces -> Phone X -> OutboundCallRoute
Yours:
{([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}
Mine:
{(<911:>(MlocalA911)):sp1},{([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
My User Defined Digit Map to make this work:
User Settings > User Defined Digit Maps
User Defined Digit Map2:
Label: localA911
DigitMap: (<:1xxxxxxxxxx>)
Did the same in my three ITSP Profiles.
Yours:
(<911:1xxxxxxxxxx>|(Mste))
Mine:
((MlocalB911)|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
My User Defined Digit Map3
Label: localB911
DigitMap: (<911:1xxxxxxxxxx>)
My conclusions:
It all works together, but I observed some flakiness. Seeing that I made sure to test all combinations of 911, **1 (or 2 or 3) + 911, to make sure one route didn't break the other one.
Flakiness: Dialing 911, either directly or **X + 911 is dependent on some interdigit timing effects, and on more than a few occasions the call didn't go through (I heard the beginning of the first ring back tone, then that was immediately interrupted by a fast busy). I experimented with an S0 after the 911, but no observable difference.
I did this mostly to see if I could make it work, and to become more familiar with things. The good part about this is you go from having the ten-digit magic numbers configured inline in six different places to two different places (encapsulated in the right word), for ex. making it easier to change to test with a non-emergency number. I couldn't figure out a way to make it all work with one User Defined digit map, maybe that is the next session.
The other insight I arrived at is probably no one in my household is going to first dial **1 before dialing 911. So unless I can get it all to work with one user defined digit map, I'll revert to only having the direct 911 work, and the **1 will get a GV error message.
One more useful thing I learned is how the sequence in which the digit maps and outbound call routes are processed. Until you pointed it out, I had assumed a digit map is executed recursively. That is not so. They are processed once each in this order:
1. Physical line digit map.
2. Physical line outbound call route.
3. ITSP profile digit map.
That's it. On the plus side, there are several powerful syntax command characters available that are not used in any default digit map or call route, such as S0 as a suffix. Haven't experimented with these yet.
CoalMinerRetired:
An update, I got all this working using one user defined digit map.
New User Defined Digit Map (My #2 UD Digit Map)
Label: local10digit911
DigitMap: "(<911S0:12159999999>)" ---> Include everything between the "", ie., opening and closing (), and note the S0 (S Zero) after 911.
Physical Interfaces > Phone 1 Port > Phone Port > OutBoundCallRoute:
First rule: {(Mlocal10digit911):sp1},{existing rules.... }
For Phone 2 Port: change sp1 to sp3 (or whatever needed)
To make **1 + 911 (and **2 + 911 and **3 + 911) work:
ITSP Profile A, B & C (I'm not using D) > General > DigitMap:
Add (Mlocal10digit911)|
As in: ((Mlocal10digit911)|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Note on "S0" Digit Timer suffix on 911 element: I'm not entirely clear this made a difference, but I suspect it does for me. In testing I was sometimes getting random and unrepeatable "We could not complete your call" responses from GV. I suspected this was from some timing thing, so I tried the S0 Digit timer suffix and so far haven't heard any 'could not complete' messages.
I like this method, it's clean and compact and it encapsulates the ten-digit local 911 number into one place from five or six, outside of the service or physical port digit maps and call routes. Makes it easier to change the number for testing or experimenting.
se1961:
WOW thanks so much for this solution, which worked like a charm for me, after trying for most of the day to get other solutions to work. :) :) :)
JackJack:
Thanks CoalMinerRetired! Worked for me as well.
Navigation
[0] Message Index
[#] Next page
[*] Previous page