Routing Type in RouteGroup: COST v/s LCR

[Jaime]

Hi All,

Currently I'm testing the new v3.0 ASTPP version, It's work as expected.

but I want to understand what is the diference in RouteGroup the

option "Routing Type" that is COST or LCR.

I undertand well the LCR option, but can you explain the logic when I select

the "COST" option int RoutingType?

Thanks for your help

Jaime

[Lucky Santiago]

Anyone has a clear explanation on the "COST" routing type?

[Samir Doshi]

Cose based routing will focus on destination number matched prefix with less amount from each possible trunk and dial the nunber. It will never consider lenght of the prefix like lcr. 

--
=====================================================================
Documentation : https://astppdoc.atlassian.net/
Please contact at sa...@inextrix.com for commercial support.
---
You received this message because you are subscribed to the Google Groups "ASTPP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to astpp+unsubscribe@googlegroups.com.
To post to this group, send email to as...@googlegroups.com.
Visit this group at https://groups.google.com/group/astpp.
To view this discussion on the web visit https://groups.google.com/d/msgid/astpp/81b3e676-5e0a-4988-9dce-ec8ab99ccd08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Sent from my iPhone

[Lucky Santiago]

Hi Samir,

Having this kind of scenario as an example:

Dialed number: 99887766

Rate 1 

prefix: 9988

rate: 0.123

Rate 2

prefix: 9988776
rate: 0.234

both rates is on the same trunk

if set to LCR will pick rate 1

if set to COST will pick rate 2

Is it right?

[Samir Doshi]

Nope thats not correct. It must be reverse. 

if set to LCR should pick rate 2

if set to COST should pick rate 1

Please reconfirm it and if you think its doing wrong then report it as bug. We will review it and do needful. 

https://github.com/iNextrix/ASTPP/issues

Best Regards
--
Samir Doshi
iNextrix Technologies Pvt. Ltd.
http://www.inextrix.com

Disclaimer:
The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorised to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful.

To view this discussion on the web visit https://groups.google.com/d/msgid/astpp/ae1ccdde-5c82-4abe-8b41-7d1c238441c2%40googlegroups.com.

[Lucky Santiago]

I had an impression that when set to LCR will always pick the least cost rate from previous systems that i used, thanks for clarifying this Samir.  

To unsubscribe from this group and stop receiving emails from it, send an email to astpp+un...@googlegroups.com.

To post to this group, send email to as...@googlegroups.com.
Visit this group at https://groups.google.com/group/astpp.

[BFS]

Hello,

We originally funded this feature as we found the existing LCR did not function similar to other systems. We have not tested this feature yet, however, it is our understanding that the longest prefix match in each providers rate desks would be chosen and then sorted by least to most expensive. Only the longest and closest matched route prefix should be used when looking up rates for each dialed number.

It is supposed to work like following example:

Example:

Dialed Number: 573173289568

Provider ABC Longest Prefix Match: 57317

Provider ABC Rate for Prefix: 0.0123

Provider DEF Longest Prefix Match: 5731

Provider DEF Rate for Prefix: 0.0098

As you can see from the example scenario above the first priority provider should be Provider DEF as it has the lower rate, however, it has a shorter prefix. Please look at comparison below of how suggested COST LCR could resolve issue. The ASTPP LCR default code could stay the same for your customers who are used to or want to route based on longest prefix only, however, a option could be added for COST LCR code to consider each provider's longest prefix and then sort by rate.

Current ASTPP LCR Code:

1. Look for longest prefix match for dialed number for active providers
2. Sort based on provider's rate
3. Attempt to make call to lowest cost provider
4. If call fails then make call to second lowest cost provider

Current ASTPP LCR Selection: Provider ABC

Suggested ASTPP COST Option Code:

1. Look for longest prefix match for dialed number for each active provider
2. Sort based on provider's rate
3. Attempt to make call to lowest cost provider
4. If call fails then make call to second lowest cost provider

Suggested ASTPP COST Selection: Provider DEF

To unsubscribe from this group and stop receiving emails from it, send an email to astpp+un...@googlegroups.com.

To post to this group, send email to as...@googlegroups.com.
Visit this group at https://groups.google.com/group/astpp.

[Dusty Countryman]

I agree, LCR should be lowest rate, no matter how long the prefix match.

Any update on this?

[Samir Doshi]

For that use COST based routing. That will do your job. 

Best Regards
--
Samir Doshi
iNextrix Technologies Pvt. Ltd.
http://www.inextrix.com

Disclaimer:
The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorised to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful.

On Mon, Mar 20, 2017 at 9:10 PM, Dusty Countryman <coun...@gmail.com> wrote:

I agree, LCR should be lowest rate, no matter how long the prefix match.

Any update on this?

--

=====================================================================
Documentation : https://astppdoc.atlassian.net/
Please contact at sa...@inextrix.com for commercial support.
---
You received this message because you are subscribed to the Google Groups "ASTPP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to astpp+unsubscribe@googlegroups.com.
To post to this group, send email to as...@googlegroups.com.
Visit this group at https://groups.google.com/group/astpp.

To view this discussion on the web visit https://groups.google.com/d/msgid/astpp/cd767b8c-d9e9-4310-acde-b57966c2199f%40googlegroups.com.