9 Aug
2011
9 Aug
'11
6:45 p.m.
No, but if you are manually creating them via append_branch(), you can set the RURI
beforehand in, say, a failure route. It will apply to the current (failed, let's say)
branch, but will be copied into the one as well, because that's how append_branch()
works.
I would use that as a manual hack around needing a different RURI for every usrloc contact
for an AOR.
--
This message was painstakingly thumbed out on my mobile, so apologies for brevity, errors,
and general sloppiness.
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
On Aug 9, 2011, at 10:41 AM, Alex Hermann <alex(a)speakup.nl> wrote:
On Tuesday 09 August 2011, Iñaki Baz Castillo wrote:
The behaviour is unexpected. Imagine you do
lookup (which fetchs 2
contacts) and after that, still in route block, do setflag(1). Such
flag is set in branch_route for both generated branches. Why setting
the $rU in same circumstances should behave different?
Flags are related to the whole transaction, so being able to see them on all
branches is expected. Use branch_flags if you want to set them per branch.
$rU is related to the 'main' branch in request_route. There is no way to set
the request uri for all branches in a transaction.
--
Greetings,
Alex Hermann
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users