Difference between revisions of "M4 Local Number Portability"
Line 1: | Line 1: | ||
Documentation WIP | Documentation WIP | ||
M4 Local Number Portability allows to connect to Local Number Portability (LNP) database and retrieve information about destination number local portability status (routing number). | |||
LNP DB should be MySQL compatible, required DB fields are described in [[M2-M4_Settings#Local_Number_Portability|M4 settings page]] | |||
= Intra/Inter/Indeter = | = Intra/Inter/Indeter = | ||
Line 8: | Line 12: | ||
Jurisdictional routing is | Jurisdictional routing is activated once LNP Database is configured in [[M2-M4_Settings#Local_Number_Portability|M4 settings page]] | ||
Once | Once LNP DB is configured, Jurisdictional routing can be enabled in the Origination Point settings. | ||
<br><br> | <br><br> |
Revision as of 15:28, 29 October 2021
Documentation WIP
M4 Local Number Portability allows to connect to Local Number Portability (LNP) database and retrieve information about destination number local portability status (routing number).
LNP DB should be MySQL compatible, required DB fields are described in M4 settings page
Intra/Inter/Indeter
Jurisdictional routing is telephone call routing logic based upon the locations of the calling and called number and regulatory considerations. Jurisdictional routing can be divided into three main parts:
- Intrastate routing (Intra) - calls within the same state.
- Interstate routing (Inter) - calls from one state to the other.
- Indeterminate routing (Indeter) - calls where origination information cannot be determined (for example, calling number is not a valid number).
Jurisdictional routing is activated once LNP Database is configured in M4 settings page
Once LNP DB is configured, Jurisdictional routing can be enabled in the Origination Point settings.
Here you can select the appropriate Tariff and Routing Group for Intra/Inter/Indeter routes.