On 01/12/14 02:23, Juha Heinanen wrote: > Juha Heinanen writes: > >> it might be possible to store in branch route request uris to an avp and >> then select the correct one based on the last field of top via branch, >> but that is a far too complicated solution for such a simple task as >> finding out the request uri of replied request. therefore, i must be >> missing something. > another one would be to store $ru in branch route to htable using > transaction and branch index as key and then get it from there in onreply > route. still too complicated. I think indeed that would be an option. Looks like nobody needed this value so far ... > > would it be possible to define $T(request_uri)? I think the best way is to extend $T_branch(...) class of pvs to have $T_branch(ruri), or maybe even $T_branch($pv) and have $T_branch($ru) for what you need.
Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda _______________________________________________ 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
