As noted, the rules are processed in order. In looking at the Flowroute documentation it is somewhat vague about the requirements. They mention 10 or 11 digit dialing, but then specifically specify: "If you need to allow for 7-digit local dialing, an additional route must be configured for your specific local Area Code in the following format:
NXXXXXX, as shown in the highlighted example below. Make sure that you replace
1206 in the example with your own area code prepended with
1. "
The above seemingly implies that they really want to see 11 digits for local, and long distance. So the first rule might read extensions = blank (all), groups = blank (all), length= 7, prefix = blank (none), route = FlowRoute, Strip = 0 and prepend = 1XXX where XXX is YOUR area code.
When you create the INTL, you would create a rule using the extension of interest for 102, and use the following:
Flowroute uses the E.164 format, which can be up to a fifteen-digit number. The number is typically formatted as [Country Code] + [Telephone Number (NPA-NXX-XXXX)]. Do not dial the North American Numbering Plan Administration (NANPA) format of using the ([Country Code] + 1). This will instead cause the number to be recognized as an international call.
For example,
- Test call to the USA: 17024797000
- Test call to the Philippines: 6322451234
For clarity, you might consider creating two rules for International dialing. One, which would precede the other would allow certain extensions and the following would be the same rule, but would preclude all extensions. As the first rule might contain extension 102 and then see 102 first, the second rule blocking 102 would not come into play. You will again note in their statement above, that they have included the "1" in national dialing.
As a result, and assuming that all extensions need local/national dialing, you need to create a 7 digit rule and prepend 1XXX as noted earlier.
You need to create a 10 digit rule and prepend 1, routed to FlowRoute
You need to create an 11 digit rule and prepend nothing, routed to FlowRoute
(In the above rules you need to specify the length of each rule to make the prepend explicit)
You need to create an International rule using extensions desired to allow and using a prefix (your choice, but if use to 011...use it) and strip 3 and prepend nothing, routed to FlowRoute
You need to create an International rule using all extensions to deny and using a prefix (your choice, but if use to 011...use it) and strip 3 and prepend nothing, Blocked on all.
(In the above rules, the length is variable and is therefore not needed. The 011 is what makes the rules unique and not applicable to the earlier local/national rules)
If emergency numbers are also with FlowRoute, you need to go to Emergency numbers with 3CX and install and specify the route and 3CX will automatically place these at the top of the order.
You also need to be aware of NANP. This is a number plan used in North America where the code "1" is dialed ahead of the area code. As you know, the "1" is used to reach all locations in the US and Canada, but it is not simply limited same, but also brings into play much of the Caribbean area where international long distance charges may apply. You cannot use the 3CX call blocking if there is a need to call these areas as I think it will take precedence over the rules and then block ext.102 regardless of what the rules say. Nevertheless, they should be examined (in security) and those countries or areas where international calling is not needed should be checked as this will help to prevent unwanted charges.
