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