[Kamailio-Users] carrier route vs LCR

[Jinsong Hu]

by handling price, we mean that if there are 2 routes that match the same 
scan_prefix, we choose the lower priced route.

in carrierroute table:
mysql> desc carrierroute;
+----------------+------------------+------+-----+---------+----------------+
| Field          | Type             | Null | Key | Default | Extra 
|
+----------------+------------------+------+-----+---------+----------------+
| id             | int(10) unsigned | NO   | PRI | NULL    | auto_increment 
|
| carrier        | int(10) unsigned | NO   |     | 0       | 
|
| domain         | int(10) unsigned | NO   |     | 0       | 
|
| scan_prefix    | varchar(64)      | NO   |     |         | 
|
| flags          | int(11) unsigned | NO   |     | 0       | 
|
| mask           | int(11) unsigned | NO   |     | 0       | 
|
| prob           | float            | NO   |     | 0       | 
|
| strip          | int(11) unsigned | NO   |     | 0       | 
|
| rewrite_host   | varchar(128)     | NO   |     |         | 
|
| rewrite_prefix | varchar(64)      | NO   |     |         | 
|
| rewrite_suffix | varchar(64)      | NO   |     |         | 
|
| description    | varchar(255)     | YES  |     | NULL    | 
|
+----------------+------------------+------+-----+---------+----------------+

we only have prob to control which route to pick up.  there is no place to 
store the price,
so how can we handle route based on price ?

the only way I can think of is to create another temp table, store the route 
and price there,
and then select the lower priced ones and insert into carrierroute table. as 
price changes,
we have to repeat this process again.

is there any other better way ?

Jimmy.



----- Original Message ----- 
From: "Ovidiu Sas" <osas at voipembedded.com>
To: "Jinsong Hu" <jinsong_hu at hotmail.com>
Cc: <gomespereira at startel.pt>; <users at lists.kamailio.org>
Sent: Thursday, April 09, 2009 4:26 PM
Subject: Re: [Kamailio-Users] carrier route vs LCR


> Both lcr and carrierroute can hadle routing based on price.  It's just
> a matter of properly defining the routed.
> lcr is easier to approach then carrierroute.  In 1.5 both of them are
> able to cope with large number of routes.
>
> Regards,
> Ovidiu Sas
>
> On Thu, Apr 9, 2009 at 6:15 PM, Jinsong Hu <jinsong_hu at hotmail.com> wrote:
>> I have been looking at the carrier route and LCR. it appears to me that 
>> LCR
>> can be used to handle tariff , i.e,
>> selecting lowest cost route. while carrier route doesn't have this
>> capability at all. but carrier route , according to LCR, scales better 
>> than
>> LCR.
>>
>> for a typical telco, the rate sheet is around 5K to 20K records. it 
>> appears
>> both LCR and carrier route can handle it.
>>
>> is the above assessment correct ?
>>
>> Jinsong
>