We are having an odd issue with our LCR. This started after we upgraded from kamailio 4.1.0 to 4.1.6.

Here is the situation:

We populate our gw_uri_avp (stored in: $avp(i:709)) as follows: 16|1||||[gateway ip address]||5060||1|1.

The $ru before running next gateway shows: sip:[destination number]@[our domain that the call came into]. This is how it should look before lcr occurs.

Then we run next_gw(). We get these message in the logs during the running of next_gw

DEBUG: lcr [lcr_mod.c:2156]: generate_uris(): r_uri <1[destination number]@[gateway ip address]:50601>, dst_uri <>

DEBUG: lcr [lcr_mod.c:2437]: next_gw(): added ruri_user_avp <[destination number]>

DEBUG: lcr [lcr_mod.c:2473]: next_gw(): added flags_avp <1>

DEBUG: lcr [lcr_mod.c:2480]: next_gw(): added tag_avp <>

DEBUG: lcr [lcr_mod.c:2488]: next_gw(): added defunct_gw_avp <1253613379>

The main thing to notice there is that there is now a 1 at the start and end of the r_uri shown in generate_uris. I am fairly certain those are new, and maybe related to what happens next.

Immediately following the next_gw function running the $ru becomes: <null>, so of course the call doesn't go through.

I have looked at the code for the lcr module and it looks like it wasn't changed in version 4.1.6. I found alot of other notes in the change log that had to do with the way uris are handled so it is possible one of those changes caused the problem.

I am stumped currently. Any help any one can offer me would be very appreciated.

All the best.

Will Ferrer

Swithsoft Inc