Parameters
<varname>enable_full_lr</varname> (integer)
If set to 1 then ;lr=on instead of just ;lr will be used. This is
to overcome problems with broken UAs which strip ;lr parameter
when generating Route header fields from Record-Route (;lr=on seems
to help).
Default value is 0 (no).
Set <varname>enable_full_lr</varname> parameter
...
modparam("rr", "enable_full_lr", 1)
...
<varname>append_fromtag</varname> (integer)
if turned on, request's from-tag is appended to record-route;
that's useful for understanding whether subsequent requests (such
as BYE) come from caller (route's from-tag==BYE's from-tag) or
callee (route's from-tag==BYE's to-tag)
Default value is 1 (yes).
Set <varname>append_fromtag</varname> parameter
...
modparam("rr", "append_fromtag", 0)
...
<varname>enable_double_rr</varname> (integer)
There are some situations when the server needs to insert two
Record-Route header fields instead of one. For example when using
two disconnected networks or doing cross-protocol forwarding from
UDP->TCP. This parameter enables inserting of 2 Record-Routes. The
server will later remove both of them.
Default value is 1 (yes).
Set <varname>enable_double_rr</varname> parameter
...
modparam("rr", "enable_double_rr", 0)
...
<varname>user_part_avp</varname> (string)
If this parameter is set, the loose_route call stores the user
part of the route URI in the AVP, which is identified by the
parameter value. It can be utilized later in the routing script.
Default value is NULL (do not insert user part into avps).
Set <varname>user_part_avp</varname> parameter, later use
...
modparam("rr", "user_part_avp", "route_user")
...
route{
...
if (loose_route()) {
t_relay();
}
if ($route_user == "my_user") {
...
}
...
}
<varname>next_route_avp</varname> (string)
If this parameter is set, the loose_route call stores the URI
of the next hop in the AVP, which is identified by the
parameter value. It can be then utilized in the routing script.
Default value is NULL (do not insert next route into avps).
Set <varname>next_route_avp</varname> parameter, later use
...
modparam("rr", "next_route_avp", "route_next")
...
route{
...
loose_route();
if ($route_next=~"101.102.103.1[0-9][0-9]") {
t_relay();
}
<varname>cookie_secret</varname> (string)
Secret to distinguish cookies from different servers.
Default value is empty string.
Set <varname>cookie_secret</varname> parameter, later use
...
modparam("rr", "cookie_secret", "bflmpsvz")
...
<varname>force_send_socket</varname> (integer)
If set to 1 and two Record-Route headers have been inserted
by the proxy before then the outgoing socket is forced by
loose_route() to be the address of the second Route header
in the in-dialog requests. Useful on multihomed hosts.
Default value is 1 (yes).
Set <varname>force_send_socket</varname> parameter
...
modparam("rr", "force_send_socket", 1)
...