1.2.1. OpenSER Modules

The following modules must be loaded before this module:

• No dependencies on other OpenSER modules.

1.2.2. External Libraries or Applications

The following libraries or applications must be installed before running OpenSER with this module loaded:

• None.

1.3.1. enable_full_lr (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).

...
modparam("rr", "enable_full_lr", 1)
...

1.3.2. append_fromtag (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).

...
modparam("rr", "append_fromtag", 0)
...

1.3.3. enable_double_rr (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).

...
modparam("rr", "enable_double_rr", 0)
...

1.3.4. add_username (integer)

If set to a non 0 value (which means yes), the username part will be also added in the Record-Route URI.

Default value is 0 (no).

...
modparam("rr", "add_username", 1)
...

1.4.1. loose_route()

The function performs loose routing as defined in RFC3261. See the RFC3261 for more details.

...
loose_route();
...

1.4.2. strict_route() -- deprecated

If there are any Route HFs in the message, the function takes the first one, rewrites Request-URI with it's value and removes the first URI from Route HFs.

...
strict_route();
...

1.4.3. record_route()

The function adds a new Record-Route header field. The header field will be inserted in the message before any other Record-Route header fields.

...
record_route();
...

1.4.4. record_route_preset(string)

This function will put the string into Record-Route, don't use unless you know what you are doing.

Meaning of the parameters is as follows:

• string - String to be inserted into the header field.

...
record_route_preset("1.2.3.4:5090");
...

1.4.5. add_rr_param(param)

Adds a parameter to the Record-Route URI (param must be in ";name=value" format. The function may be called also before or after the record_route() call.

Meaning of the parameters is as follows:

• param - String containing the URI parameter to be added. It must follow the ";name=value" scheme.

...
add_rr_param(";nat=yes");
...

1.4.6. check_route_param(re)

The function check if the URI parameters of the local Route header (coresponding to the local server) matches the given regular expression. It must be call after loose_route().

Meaning of the parameters is as follows:

• re - regular expression to check against the Route URI parameters.

...
if (check_route_param("nat=yes")) {
    setflag(6);
}
...