General


    Local Calling is a feature that allows charging calls local rates.  

Detecting if a call is local (only if Local Calling is Enabled on Tariff or if Destination Set is checked)


  • If LRN is enabled for the Routing Group, at least one prefix Tariff/Destination matches, and Area Name is not blank; then, LRN lookup for CLI will take place.  Local Calling check is done based on the incoming LRN CLI. The Ignore LRN setting from Connection forces the Local Calling check to use the CLI instead of the LRN CLI. Starting from 5.2


  • The CLI Validation Rule configured on Tariff/Destination Set is applied to the CLI (LRN CLI for the 5.2 case above) that is checked, if it does match OR is blank:

  1. A Rate is looked up by CLD through prefix search and the area_name attribute if the resulting rate is expected to be listed and valid
  2. All the Rates with the same area_name are fetched from the Tariff and the CLI is checked against the Set using prefix search. If a Rate is found, then the call is considered to be local. The search is exclusively to check for Local Calling so prices and intervals from the Rate that is found are not used
  3. If the call is local then, local_price_1, local_price_N, local_interval_1 and local_interval_N are used for the billing and loss protection check


  • The CLI Validation Rule configured on the Tariff/Destination Set is applied to the CLI (LRN CLI for the 5.2 case above) that is checked, if it does NOT match:

  1. A Rate is looked up by CLD through prefix search and the area_name attribute if the resulting rate is expected to be listed and valid
  2. local_price_1, local_price_N, local_interval_1 and local_interval_N are used for the billing and loss protection check


This procedure is exactly the same for the Destination Sets.


Call Example:


1. You receive a call with CLD (38044555111) and CLI (380442111222)


2. The System tries to find an appropriate prefix for the CLD number and gathers all possible prefixes from Tariff


3. Tariff is checked for a Local Calling Enabled flag to be set. If the flag is set, then the Local Calling check will follow


4. For 5.2 or higher versions LRN Enabled is checked for the Routing Group. If it's enabled, then:

4.1 The prefixes retrieved are checked for area_name configuration, if at least one prefix has a valid configuration, LRN lookup for CLI is carried out. If an Ignore LRN checkbox for the corresponding Connection is not set then a Local Calling check would be done for every Routing Entry based on the incoming LRN CLI 


5. For example: prefix 38044 has been found in the Tariff for the CLD number and area_name = "KV" for that prefix


6. Then the system tries to gather all possible prefixes with the same area_name = "KV" in that Tariff


7. When prefixes with the same area_name are found, the system tries to find an appropriate prefix for CLI (380442) between them


(Rate for the CLI will not be used in further charges and the check is only for the identification of "Local Calling")


8. If an appropriate prefix for CLI (380442) is detected, the system tries to bill the call using the configuration "Local Calling" (of prefix 38044) instead of the configuration "Basic Parameters" and the call is considered local


9. The same scenario occurs for each Destination Set from the Routing Group Members that was matched at 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.


See example:


1. There are 3 prefixes in Tariff. Two of them (38044, 380442) use the area_name = 'KV' and one (38046) uses area_name = 'CN'




Call is defined as intrastate:



Call is defined as interstate (originated from outside Local Area):