Local Calling is a feature that allows to charge the calls by local rates.
Detection if a call is local [only if Local Calling Enabled on Tariff or Destination Set is checked]
- If LRN is enabled for the Routing Group, and at least one prefix from matched Tariff/Destination Set has not null Area Name, the additional LRN lookup for CLI would be issued, and further Local Calling check would be done based on the received LRN CLI. Ignore LRN setting from Connection forces Local Calling check to use CLI instead of LRN CLI. Starting from 5.2
CLI Validation Rule configured on Tariff/Destination Set is applied to resulting CLI (LRN CLI for the 5.2 case above), if it does match OR is blank:
- A rate is looked up by CLD with usual prefix search and the area_name attribute of the resulting rate is expected to be neither null nor empty.
- All the rates with the same area_name are fetched from the Tariff and the CLI is checked against this set using usual prefix search. If the rate has been found, then the call is considered to be local. This search is solely for Local Calling check purposes so prices and intervals from the newly found rate are not used.
- If the call is local then the local_price_1, local_price_N, local_interval_1 and local_interval_N are used for billing and loss protection check.
CLI Validation Rule configured on Tariff/Destination Set is applied to resulting CLI (LRN CLI for the 5.2 case above), if it does NOT match:
- A rate is looked up by CLD with usual prefix search and the Area_Name attribute of the resulting rate is expected to be neither null nor empty.
- The local_price_1, local_price_N, local_interval_1 and local_interval_N are used for billing and loss protection check.
This procedure is exactly the same for the Destination Sets.
1. You have received some call with some CLD (38044555111) and CLI (380442111222)
2. System tries to find some appropriate prefix for the CLD number and gathers all possible prefixes from tariff.
3. Tariff is checked for Local Calling Enabled flag to be set. If yes - local calling check will be followed.
4. For >= 5.2 version the LRN Enabled would be checked for Routing Group. If it's enabled, then:
4.1 The fetched prefixes would be checked for area_name filled, if at least one prefix has it configured, additional LRN lookup for CLI would be sent, the Local Calling check would be done for every Routing Entry based on the received LRN CLI if no Ignore LRN checkbox is set for the corresponding Connection.
5. For example prefix 38044 has been found in the Tariff for the CLD number and area_name = "KV" for that prefix.
6. Then system tries to gather all possible prefixes with the same area_name = "KV" in that tariff.
7. When some prefixes with the same area_name found, system tries to find an appropriate prefix for CLI (380442) between them.
(Rate for the CLI will not be used in further charges and check is only for the identification of "Local calling".)
8. If an appropriate prefix for CLI (380442) detected then system tries to bill the call using the section "Local Calling" (of prefix 38044) instead of "Basic Parameters" section and call is considered as local.
9. The same scenario for each Destination Set from Routing Group Members that was matched the call attempt.
PLEASE NOTE, Area Name in the "Destinations" menu is not important for the "Local Calling" scenario, only the Area Name from rate/route is considered.
Example of validation rule:
(?=.*[a-zA-Z].*$) - if you set this rule, then all calls with alphabetic CLI will be recognized as non local calls.
1. There are 3 prefixes in tariff. Two of them (38044, 380442) use the area_name = 'KV' and one (38046) uses area_name = 'CN'.