I've discovered a bug in the processing of digit maps. Although I reported the bug to Obi tech support, they ignored the report and instead gave me generic instructions on how to configure an Obi device to work with a VOIP provider.
Here's the issue: The Obi digit map has a feature that allows you to append S and the a number to the end of a digit map sequence to decrease the interdigit timer when there is a match. Most of the time it works properly, but when appended to a string that starts with a "x.", it has a strange bug.
Here's an example of how it is suppose to work. With this digit map:
(911S0|x.)
You can dial any number with a 10 second dialing delay, but if you dial 911, the call will go through immediately. You can shorten that 10 second delay by making another modification to the digit map:
(911S0|x.S3)
Now, calls to 911 will go out immediately, and all other calls will go out in 3 seconds.
BUT- there's a bug here as well. If you pick-up the phone and wait more than 3 seconds before dialing, then the "x." portion of the digit map WILL BE IGNORED and the call will fail.
If you change the S3 to an S5, you'll experience the same issue after 5 seconds.
Now, if you use this instead:
(911S0|1x.S3)
Then you can call 911, which will go out immediately, or you can dial 1+any number and it will go out within 3 seconds. However, unlike the example above, if you pick up the phone and wait more than 3 seconds, the 1x. portion of the digit map WILL BE PROCESSED and the call will go through.
Can anyone tell me how I might bring this to Obi's attention?