Call routing per destination basis

From Kolmisoft Wiki
Revision as of 07:31, 29 January 2016 by Ricardass (talk | contribs)
Jump to navigationJump to search

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.

Routing by destination new.png

Different LCR can bet 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.

Example

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

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:

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:

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):

Crpdb4.png

We create the following configuration:

Crpdb5.png

Explanation

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

Crpdb6.png

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

Crpdb7.png

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

Crpdb8.png

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

Crpdb9.png

See also