On 9/26/12 4:44 PM, Juha Heinanen wrote:

Juha Heinanen writes:

...

I tried to call record_route_preset() in branch route in order to add contact specific RR headers when request is forked to more than one contact. What happened was that I got error message:

Sep 26 17:03:47 wheezy2 /usr/sbin/sip-proxy[2436]: ERROR: rr [rr_mod.c:256]: Duble attempt to record-route

Is it really so that record routing is not a branch specific thing? Is there a way to solve this problem? i "solved" it by not using record_route_preset() at all. instead i used append_hf, which seemed to do the same thing on per branch basis. i wonder if there is any point in having record_route_preset() function? I think it integrates better with the rest of the rr functions, like adding rr params set by dedicated config function.

The error comes from a safety check based on internal flag to avoid calling many times record routing in request_route, but probably it can be relaxed for branch_route. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu

Alex Balashov writes:

I wonder what happens if you add a Record-Route header manually in the branch_route, with append_hf(), e.g.

append_hf("Record-Route: <sip:ip.of.proxy:5060>\r\n");

that would work, but is not that simple due to all kinds of r-r params and socket that depend on many things. but it looks like the contents of resulting r-r header are branch specific, i.e., it is possible to call record_route() once in route block and set r-r params and socket in branch route block. -- juha