Call routing per destination basis

From Kolmisoft Wiki

Jump to: navigation, search

SETTINGS > Billing > LCR and then click on icon in "By destinations" column.

Some destinations need fine tuning to better tell which providers should be used to reach that destination and in which order.

Each user has an assigned LCR. For some destinations, it is possible to set a different LCR.

File:Routing_by_destination_new.png

Different LCR can be set on Prefix, Destination Name or Destination Group.

Destination Names support wildcard characters:

  •  % matches any number of characters, even zero characters.
  • _ matches exactly one character.

In cases when active destinations selected by Prefix, Destination Name or Destination Group overlap, it works as intuitively expected. For example if you add LCR by Prefix 370, its activate destination list will include all prefixes starting with 370. Now, let's say there is a destination group named Lithuania - Mobile Tele2, which have destinations with prefixes 3706, 370645 add 370646. If we add LCR by Destination Group Lithuania - Mobile Tele2, then this LCR active destination list will have prefixes 3706, 370645 add 370646 and these prefixes will be removed from LCR by Prefix 370 active destination list.

Here is the list of rules which can be handy if you need to determinate how MOR chooses active destination list is more complicated scenarios. The following rules apply:

  • Exact Prefix in LCR by Prefix have highest priority. If there are no other rules and we add LCR by Prefix 370, this LCR will include 370 and all other destinations starting with 370. As we add other LCRs by Prefix, Destination Name or Destination Group, these can claim all prefixes starting with 370, except Exact Prefix 370, which will always stick to this LCR.
  • LCR by Destination Group is second in priority and always include all prefixes available in that destination group, except exact prefix in LCR by Prefix, which will always have exact prefix as it has highest priority.
  • LCR by Destination Name have third priority, which means that LCR by Destination Name will have all destinations which matches the name, excluding destinations which exist in LCRs by Destination Group and exact prefixes in LCR by Prefix.
  • All other prefixes except exact prefix in LCR by Prefix destinations list have lowest priority.

[edit] Example

We take Paraguay as example, because this country has a small number of destinations.

Image:crpdb1.png

Let's say we have three providers (in LCR: Primary), and we use them all together for all our destinations. The route is picked by the least cost route, that is, the LCR order is by Price:

Image:crpdb2.png

Then we have the situation that calls to Paraguay (except those to Mobiles) do not go through the provider Eutelia.

To handle this situation we create a new LCR: Secondary, in which the order is Priority. It excludes Eutalia and has only two providers:

Image:crpdb3.png

Now we need to configure Routing per destination.

Click on the By destinations icon for Primary LCR (because Primary LCR is used by the user who dials):

Image:crpdb4.png

We create the following configuration:

Image:crpdb5.png

[edit] Explanation

Now when the user dials any Paraguay FIX number, the call will be routed using LCR: Secondary with order: priority:

Image:crpdb6.png

We can click on Active destinations and will see for which prefixes such an LCR applies:

Image:crpdb7.png

As we know that Eutalia can route calls to Mobile networks of Paraguay, so MOB destinations will be handled by old LCR:

Image:crpdb8.png

We can click on Active destinations and will see for which prefixes such an LCR applies:

Image:crpdb9.png

[edit] See also

Personal tools

Try MOR

Try M2