Routing

Routing - is a process of building of routing table in response to parameters of incoming call.
Routing table - is a sorted list of dial peers and call parameters for generation a call to each route.
Then system performs Hunting over found routes.

Routing is performed internally by next application:

To check routing table you can use tool Check hunting, which is present on configuration page for each peer.

See also:

Building routing table

Supported technologies of building routing table:

When building routing table following parameters are accounted:

  • Route class, which is configured on originator
  • parameters of Number replacement on all peers
  • technologies, configured on the peers
  • peer balances. Peers calls to which will be blocked by balance, are not put to routing table.
    More in detail this is described in section Balance maintanance.

After building of routing table, the system excludes several rules according to:

  • traffic portions to perform Percentage routing.
  • parameter huntstop.
    If it's set up, the system will erase all routes from table which appeared to be after this route as a result of sorting.

Number replacemenet for inbound call

Automatic number replacement for inbound call uses following algorithm.

In case if inbound peer has been configured to perform Number replacement, system tried to substitute numbers (caller ID or callee ID) according to rules.
After number replacement system uses replaced numbers to perform routing by destination code and Billing.
Usually number replacement is used to trim technical prefixes in order to bring numbers to E.164 format to perform correct billing.

In case if rules are configured in a way, that system can't perform substitution, then routing is stopped.
This feature could be used to pass only some specific sets of callee or caller IDs.
In case if you want to replace specfic numbers, and others topass without changes, you need to add wldcard substitution .* -> & at the end.
More in detail this substitution is explained in section Regex patterns.

In case if there is no rules for number replacement, it's assumed that routing would be done without number replacement.

Number replacement for outbound call

Automatic number replacement for outbound call uses following algorithm.

In case if outbound peer has been configured to perform Number replacement, system tried to substitute numbers (caller ID or callee ID) according to rules.
After number replacement system uses replaced numbers to generate outbound call.
Usually number replacement is used to add technical prefixes in order to E.164 numbers.

In case if rules are configured in a way, that system can't perform substitution, then route to this peer is not included to routing table.
You can use this feature to pass only some specific sets of callee or caller IDs to terminating peer.
In case if you want to replace specfic numbers, and others topass without changes, you need to add wldcard substitution .* -> & at the end.
More in detail this substitution is explained in section Regex patterns.

In case if there is no rules for number replacement, it's assumed that generation of outbound call will be done without number replacement.

See also:

Русский перевод

Also available in: PDF HTML TXT