First thing to remember that lcr_id field is the one to link all three tables together. Let's say that you want to create a lcr to route international call starting with 011:

1) Create a row in lcr_gw table with id = 4, lcr_id = 3 and gateway IP etc.

2) Then create a row in lcr_rule table with id =2, lcr_id = 3 and prefix = 011

3) Then create a row in lcr_rule_target table to glue the gateway and prefix together like this: lcr_id =3, gw_id=4 (Match the id value in lcr_gw table), rule_id = 2 (Match the id in lcr_rule table)  also rest of the fields like priority etc.

Hope this help.

Gary

On Fri, Jun 28, 2013 at 5:02 PM, Geoffrey Mina <geoffreymina@gmail.com> wrote:

Greetings,
I am migrating some 1.5 servers to 4.0 and I have some questions about how the LCR module works now.

I am familiar with the concept of the gw table and the lcr table.  This was pretty straight forward.  In the new version it looks like we have:

LCR Gateway List

LCR Rule List

LCR Target List

I read through the module documentation and it doesn't really speak to what the new architecture is intended to accomplish.  Anyone have a quick overview they would like to share which would help me understand the intent of the data structure?

Thanks,
Geoff

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users