That's wonderful! :-) regards, stefano
Bogdan-Andrei Iancu wrote: > > Hi guys, > > Even if the solution suggested by Inaki is a valid one, it is a terrible > hack (storing the RURI in VIA / RR just to get it at reply time) - > especially when this information is available in the internal > transaction, so it is just a matter of accessing it. > > So, I added a new Pseudo Variable in TM module to give access to the > RURI of each outgoing branch: $T_ruri > http://www.opensips.org/html/docs/modules/1.5.x/tm.html#id272609 > > This is available in onreply route too, so you can get the RURI of the > corresponding branch from there. > > Regards, > Bogdan > > stefanoIT wrote: >> Hi Iñaki, >> you suggestion was brilliant. >> I can store the uri(s) is avp $(avp(s:uri)[n]) = $ru >> then put n in via header, and get it on 200 reply. >> I'll try. >> Thanks >> >> PS I remember that in via header there is alrealy branch number (.1 .2 .3 >> and so on) >> >> >> Iñaki Baz Castillo wrote: >> >>> 2009/2/2 stefanoIT <[email protected]>: >>> >>>> So there is no a solution to my problem. At the moment. >>>> >>> You can also process each generated branch in "branch_route" and add >>> the RURI value as Via or Record-Route parameter. For example: >>> >>> branch_route[X] { >>> add_rr_param(";branch_ruri_user=$rU"); >>> add_rr_param(";branch_ruri_hostport=$rd:$rp"); >>> } >>> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- View this message in context: http://n2.nabble.com/parallel-forking-tp2257204p2263112.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
