Difference between revisions of "LCR"
m (→Example 2) |
m |
||
Line 11: | Line 11: | ||
Supported routing modes: | Supported routing modes: | ||
* By Price - cheapest first (Least Cost Routing). | * [[Call Routing by price|By Price]] - cheapest first (Least Cost Routing). | ||
* [[Call Routing by priority (Manual LCR) | By priority]]. | * [[Call Routing by priority (Manual LCR) | By priority]]. | ||
* [[Routing by Percent| By percent]] or Weight-based routing. | * [[Routing by Percent| By percent]] or Weight-based routing. | ||
Line 18: | Line 18: | ||
It is possible to route different destinations for a User using [[Call routing per destination basis]]. | It is possible to route different destinations for a User using [[Call routing per destination basis]]. | ||
<br><br> | <br><br> | ||
Revision as of 10:04, 11 August 2011
About
LCR (Least Cost Routing) is a set of Providers that should be used to send a call when trying to dial any destination - for example, by the cheapest rate.
The correct name for such a function is a Routing Table, because the function supports other ways of routing, not just finding the cheapest route.
LCR supports fail-over. That is, if one provider fails, the next one is dialed. This is completely invisible for the caller and lets you increase the chances of the user reaching his destination. If one Provider is not capable of delivering a call, the system will try to use the remaining Providers.
The LCR window can by found in SETTINGS – Billing – LCR.
Supported routing modes:
- By Price - cheapest first (Least Cost Routing).
- By priority.
- By percent or Weight-based routing.
The user has one base LCR, so that all his calls are routed by some preset rule.
It is possible to route different destinations for a User using Call routing per destination basis.