As a rule, I have managed to work my way through any issues however, I would really appreciate and help in getting the LCR module working (with postgres), what I really need is working examples of working config and database tables,
Many thanks,
Jeff
The quality of responses to your request would be increased by a brief statement of your objective. Despite its tantalising name, the 'lcr' module may not be the most appropriate solution to your problem, depending on what exactly your problem is.
-- This message was painstakingly thumbed out on my mobile, so apologies for brevity and errors.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Atlanta, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com
On Mar 19, 2012, at 2:48 PM, Jeff Russell jrussell@advanis.net wrote:
As a rule, I have managed to work my way through any issues however, I would really appreciate and help in getting the LCR module working (with postgres), what I really need is working examples of working config and database tables,
Many thanks,
Jeff
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
Details...
We have a table with about 145,000 NPA/NXX's with differing rates and carriers, I would like to use the LCR module to load this table and rewrite the URI based on the best rate for dialled number and or a default route. The new 'in memory" LCR module should be efficient enough (we are planning about 35k calls per hour.
Any help or direction much appreciated.
Jeff
On 2012-03-20, at 1:19 AM, Alex Balashov wrote:
The quality of responses to your request would be increased by a brief statement of your objective. Despite its tantalising name, the 'lcr' module may not be the most appropriate solution to your problem, depending on what exactly your problem is.
-- This message was painstakingly thumbed out on my mobile, so apologies for brevity and errors.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Atlanta, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com
On Mar 19, 2012, at 2:48 PM, Jeff Russell jrussell@advanis.net wrote:
As a rule, I have managed to work my way through any issues however, I would really appreciate and help in getting the LCR module working (with postgres), what I really need is working examples of working config and database tables,
Many thanks,
Jeff
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
Jeff Russell writes:
We have a table with about 145,000 NPA/NXX's with differing rates and carriers, I would like to use the LCR module to load this table and rewrite the URI based on the best rate for dialled number and or a default route.
lcr module selects the gateways first based on longest matching prefix of called number and second based on priority of the gateways defined for the matched prefix. perhaps you can map your rates to these priorities.
-- juha
I am still struggling a little with this, I have everything working, postgres & lcr modules loading what I am looking for for is a difinative working example of the information in the db tables.
my db tables: lcr_rule (lcr_id, prefix, from_uri, stopper, enabled, id)
lcr_rule_target (rule_id, gw_id, priority, weight, id, lcr_id)
lcr_gw gw_name, ip_addr, port, uri_scheme, transport, params, hostname, strip, prefix, tag, flags, defunct, id, lcr_id)
a couple simple examples that will update the following would be VERY helpful
original uri sip:1103@10.1.1.58 updated uri sip:1103@10.1.1.60
original uri 7802291103@10.1.1.58 updated uri 17802291103@10.1.1.61
at present I get the following errors 'error while parsing R-URI' & the load_gw fails.
Anything you can provide that will prevent my head from exploding would be very much appreciated.
Jeff
On 2012-03-20, at 11:26 PM, Juha Heinanen wrote:
Jeff Russell writes:
We have a table with about 145,000 NPA/NXX's with differing rates and carriers, I would like to use the LCR module to load this table and rewrite the URI based on the best rate for dialled number and or a default route.
lcr module selects the gateways first based on longest matching prefix of called number and second based on priority of the gateways defined for the matched prefix. perhaps you can map your rates to these priorities.
-- juha
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
Jeff Russell writes:
I am still struggling a little with this, I have everything working, postgres & lcr modules loading what I am looking for for is a difinative working example of the information in the db tables.
your problem:
at present I get the following errors 'error while parsing R-URI' & the load_gw fails.
has nothing to do with lcr tables. the error message comes if load_gws() fails to parse request uri.
add xlog("L_INFO", "request uri is <$ru>\n")
before load_gws() call and then check what is wrong with your request uri.
-- juha
I wish that were the case, I am already logging this and there is nothing wrong with the URI , it there seems to be no issues if I use another non-lcr route :(
also, I would really like and example of what the contents of the db should be.
Again, many thanks,
Jeff
xlog( "L_NOTICE", "here");
xlog("L_NOTICE","route[IVR]: Original URI <$tu>\n"); if(!load_gws()){ sl_send_reply("500", "Internal server error, unable to load gateways"); xlog("L_NOTICE","Internal server error, unable to load gateways"); break; } if(!next_gw()){ sl_send_reply("503", "Service not available, no gateways found"); break; }
xlog("L_NOTICE","route[IVR]: AFTER Original URI <$tu> Updated URI <$ru> \n"); return; }
Apr 3 13:35:33 p-siprouter-003 /usr/local/sbin/kamailio[5193]: NOTICE: <script>: here Apr 3 13:35:33 p-siprouter-003 /usr/local/sbin/kamailio[5193]: NOTICE: <script>: route[TEST]: Original URI sip:1103@10.1.1.58 Apr 3 13:35:33 p-siprouter-003 /usr/local/sbin/kamailio[5193]: ERROR: lcr [lcr_mod.c:1721]: error while parsing R-URI
On 2012-04-04, at 2:05 AM, Juha Heinanen wrote:
Jeff Russell writes:
I am still struggling a little with this, I have everything working, postgres & lcr modules loading what I am looking for for is a difinative working example of the information in the db tables.
your problem:
at present I get the following errors 'error while parsing R-URI' & the load_gw fails.
has nothing to do with lcr tables. the error message comes if load_gws() fails to parse request uri.
add xlog("L_INFO", "request uri is <$ru>\n")
before load_gws() call and then check what is wrong with your request uri.
-- juha
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
Jeff Russell writes:
I wish that were the case, I am already logging this and there is nothing wrong with the URI , it there seems to be no issues if I use another non-lcr route :(
xlog("L_NOTICE","route[IVR]: Original URI <$tu>\n");
you are logging $tu, which has nothing to do with lcr module. i asked you to log $ru.
-- juha
Grrr..
My apologies, your right! (whoda thunk it), the error was because this was for a register, not a route, that has now been taken care of and I'll work a little more on getting the right info into the LCR db tables.
May thanks, sorry about my ineptitude.
Jeff
On 2012-04-04, at 2:05 AM, Juha Heinanen wrote:
Jeff Russell writes:
I am still struggling a little with this, I have everything working, postgres & lcr modules loading what I am looking for for is a difinative working example of the information in the db tables.
your problem:
at present I get the following errors 'error while parsing R-URI' & the load_gw fails.
has nothing to do with lcr tables. the error message comes if load_gws() fails to parse request uri.
add xlog("L_INFO", "request uri is <$ru>\n")
before load_gws() call and then check what is wrong with your request uri.
-- juha
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
-
Alex Balashov -
Jeff Russell -
Juha Heinanen