Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: New pseudo variable for route_params

Initial Comment:
To my big surprise, OpenSIPS is not transparent in regards with route parameters. In route scripts, there is no easy way to copy all the route params from the incoming message into the outgoing ones.

I extended the RR modules in order to give access to rr params in a pseudo variable named $rr_params

So copying route params becomes easy

if (loose_route() )
{
record_route( $rr_params );
...
t_relay();
}

Examining and modifying route params beforehand in script variables or AVPs is also vastly simplified.

Message:
Ok Klaus, I agree with the comment.
ROute set should not be modified once established.

Nevertheless, I use route param to make dialog wide routing decision in my
conf scripts and as far as I know, there is no easy way to retreive RR
parameter value. There is only a function to check whether a param has a
predefined value.

The new pseudo variable associated with transformation enable easy access
to such information. Would the maintainter kindly consider the addition of
this PV ?

Message:
not sure what you mean: during the first INVITE, if you call
record_route(), openser will add the Record-route header with some
parameters. If there are already Route headers present, openser will remove
the ones pointing to itself and the other will be untouched.

Further, in-dialog requests will contain the Route added by openser. The
Route headers which point to openser will be remove during loose_routing,
other route headers will be untouched.

If you see a different behavior please post an ngrep trace (ngrep -W
byline -t -q -P "" -d any port 5060)

Message:
FYI: Adding Record-Route header to in-dialog requests is useless, as the
route set is built from the initial request and MUST NOT be changed during
the dialog. If a client interprets Record-route headers of in-dialog
requests than the client is buggy.