Hello;
i commented your last commit. Sorry , i think i couldn't explain
situation.
Here is log for more understand.
- Here is first load_gws and next_gws() functions are
called-
6(10299) DEBUG: lcr [
ycaner writes:
> in load_gws function
> there is a delete_avp for gw_uri_avp as you mentioned . but in my
> view it needs a delete_avp for ruri_user_avp.
> Because it is reloading gws for different route.
I added deletion of possible old ruri_user_avp value when next_gw()
in load_gws function
there is a delete_avp for gw_uri_avp as you mentioned . but in my
view it needs a delete_avp for ruri_user_avp.
Because it is reloading gws for different route.
Thanks.
04.12.2015 11:44 tarihinde Juha
Heinanen [via SI
ycaner writes:
> Thanks for reply. before load_gws , setting ruri_user_avp to null solves
> request uri problems.
load_gws() tries to delete possibly existing avp values by this
statement:
delete_avp(gw_uri_avp_type|AVP_VAL_STR, gw_uri_avp);
obviously there is something wrong with if the av
Hey;
Thanks for reply. before load_gws , setting ruri_user_avp to null solves
request uri problems.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/LCR-module-re-load-gws-uri-errors-tp143602p143648.html
Sent from the Users mailing list archive at Nabble.com.
___
ycaner writes:
> when first usage of load_gws() and next_gw() functions , next_gw() fills all
> uri avps to ru_AVPs from gws tables. if it goes to failure route or route
> again , it can re use ru_AVPs in next_gw(). so if recall the load_gws()
> again for choose new route , it uses old uri avps i
Hello;
i found the problem i hope i can explain the problem to get solution.
when first usage of load_gws() and next_gw() functions , next_gw() fills all
uri avps to ru_AVPs from gws tables. if it goes to failure route or route
again , it can re use ru_AVPs in next_gw(). so if recall the load_gws
Hello;
After change $rU in failure route , calling load_gws function.
so lcr module changes request uri and fromuser and it is wrong.
here is example for more explain;
calls flows
1- 850xxx to 1021850yyy
2- 486 busy
3- going to t_on_failure rout
