Dialplan: Possible to enable both 7-digit and 10-digit dialing?
Lynx:
Ahh ok. So it's the 2 second delay that is allowing for both 7-digit and 10-digit dialing.
If I want to forgo 10-digit dialing in favor of faster 7-digit dialing, would using S0 in the dial plan like this work so that there's no delay after dialing?
(*xx|1xxxxxxxxxxS0|<1aaa>[2-9]xxxxxxS0|<011:**300>xx.|xx.|(Mipd)|[^*]@@.)
mrjoe:
If you put longer numbers before shorter ones there is no need for any S2/4 etc. as digit maps are read from left to right (as Ianobi told me) so short numbers will not interfere as the Obi reads the longer one first and connects.
Sounds complicated but it's not. :)
ianobi:
Let’s take a step back here! I think I said that the Phone Port OutBoundCallRoute was processed rule by rule from left to right. The same might be true of DigitMaps, but I don’t know that for sure. All I know about DigitMaps is that the best matched rule is used, maybe if two are equal, then the left to right rule may apply.
Back to the original question:
Short answer: This will work, i.e. no delays for eleven digit numbers starting with 1 or seven digit numbers starting with 2-9:
(*xx|1xxxxxxxxxxS0|<1aaa>[2-9]xxxxxxS0|<011:**300>xx.|xx.|(Mipd)|[^*]@@.)
OBiNerd answer: If it’s only for GV, then most of these codes are not needed. The aim here is to achieve an Exactly Matched (EM) rule with no other rules in the Indefinitely Matched (IM) state. As you dial each digit these rules: xx. and [^*]@@. will always be in the IM state. From the point of view of digits, they both mean any digit followed by any number of digits. When another rule such as 1xxxxxxxxxx is in an EM state, then there will still be the 2 second delay because of other rules in the IM state. (Assuming no S0 additions).
Consider this DigitMap for GV:
(1xxxxxxxxxx|<1aaa>xxxxxxx|011xx.)
The first two rules will send the called number out to GV with no delay as soon as an Exact Match is achieved as there are no rules in the IM state. (I know I have sacrificed ten digit dialling).
Alternatively:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.)
The first two rules will send the called number out to GV with no delay as soon as an Exact Match is achieved as there are no rules in the IM state. The third rule will have a 2 second delay as the second rule will be in the IM state after seven digits. Some would recommend putting S4 after the third rule in case people are dialling a ten digit number very slowly.
I can see no function for these rules in a GV DigitMap:
xx.|(Mipd)|[^*]@@.
GV experts please comment!
@ Lynx – I’m not sure what the *xx rule is for in your suggested DigitMap as it seems to conflict with Obi Star Codes.
I’m sure that we all feel better for having a good DigitMap workout :)
jimates:
all of my ITSP profiles (google voice and CC) use the same digit map.
User defined digit map "Ste" which is
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)
7, 10 or 11 digit dialing. I never use 11 digit dialing as the Obi or google voice always add it, and I make no international calls.
ianobi:
Thanks for your input jimates. There's a lot to be said for removing redundant rules from DigitMaps. The xx. and @@. type of rules simply slow things down. A well crafted DigitMap does not need them.
Navigation
[0] Message Index
[#] Next page
[*] Previous page