$Revision: 1274 $ $Date: 2006-11-27 19:57:15 +0200 (Mon, 27 Nov 2006) $

The module contains record routing logic

&ser; is basically only a transaction statefull proxy, without any dialog support build in. There are many features/services which actually requires a dialog awareness, like storing the information in the dialog creation stage, information which will be used during the whole dialog existence. The most urging example is NAT traversal, in dealing with the within the dialog INVITEs (re-INVITEs). When processing the initial INVITE, the proxy detects if the caller or callee is behind some NAT and fixes the signalling and media parts - since not all the detection mechanism are available for within the dialog requests (like usrloc), to be able to fix correspondingly the sequential requests, the proxy must remember that the original request was NAT processed. There are many other cases where dialog awareness fixes or helps. The solution is to store additional dialog-related information in the routing set (Record-Route/Route headers), headers which show up in all sequential requests. So any information added to the Record-Route header will be found (with no direction dependencies) in Route header (corresponding to the proxy address). As storage container, the parameters of the Record-Route / Route header will be used - Record-Route parameters mirroring are reinforced by RFC 3261 (see 12.1.1 UAS behavior). For this purpose, the modules offers the following functions: add_rr_param() - see check_route_param() - see UAC OpenSER PROXY UAS ---- INVITE ------> record_route() ----- INVITE ----> add_rr_param(";foo=true") --- reINVITE -----> loose_route() ---- reINVITE ---> check_route_param(";foo=true") <-- reINVITE ------ loose_route() <--- reINVITE ---- check_route_param(";foo=true") <------ BYE ------- loose_route() <----- BYE ------- check_route_param(";foo=true")

The following modules must be loaded before this module: No dependencies on other &ser; modules.

The following libraries or applications must be installed before running &ser; with this module loaded: None.

If set to 1 then ;lr=on instead of just ;lr will be used. This is to overcome problems with broken &ua;s 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) ...

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) ...

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) ...

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) ...

The function performs routing of SIP requests which contain a route set. The name is a little bit confusing, as this function also routes requests which are in the strict router format. This function is usually used to route in-dialog requests (like ACK, BYE, reINVITE). Nevertheless also out-of-dialog requests can have a pre-loaded route set and my be routed with loose_route. It also takes care of translating between strict-routers and loose-router. The loose_route function analyzes the Route: headers in the requests. If there is no Route: header, the function returns FALSE and routing should be done with normal lookup functions. If a Route: header is found, the function returns 1 and behaves as described in section 16.12 of RFC 3261. There is only one exception: If the request is out-of-dialog (no to-tag) and there is only one Route: header indicating the local proxy, then the Route: header is removed and the function returns FALSE. Make sure your loose_routing function can't be used by attackers to bypass proxy authorization. The loose_routing topic is very complex. See the RFC3261 for more details (grep for route set is a good starting point in this comprehensive RFC). This function can be used from REQUEST_ROUTE. ... loose_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. If any string is passed as parameter, it will be appended as URI parameter to the Record-Route header. The string must follow the ;name=value scheme and it may contain pseudo-variables. This function can be used from REQUEST_ROUTE, BRANCH_ROUTE and FAILURE_ROUTE. ... record_route(); ...

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; it may contain pseudo-variables. This function can be used from REQUEST_ROUTE, BRANCH_ROUTE and FAILURE_ROUTE. ... record_route_preset("1.2.3.4:5090"); ...

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 (see ). Meaning of the parameters is as follows: param - String containing the URI parameter to be added. It must follow the ;name=value scheme; it may contain pseudo-variables. This function can be used from REQUEST_ROUTE, BRANCH_ROUTE and FAILURE_ROUTE. ... add_rr_param(";nat=yes"); ...

The function checks if the URI parameters of the local Route header (corresponding to the local server) matches the given regular expression. It must be call after loose_route() (see ). Meaning of the parameters is as follows: re - regular expression to check against the Route URI parameters. This function can be used from REQUEST_ROUTE. ... if (check_route_param("nat=yes")) { setflag(6); } ...

The function checks the flow direction of the request. As for checking it's used the ftag Route header parameter, the append_fromtag (see module parameter must be enables. Also this must be call only after loose_route() (see ). The function returns true if the dir is the same with the request's flow direction. The downstream (UAC to UAS) direction is relative to the initial request that created the dialog. Meaning of the parameters is as follows: dir - string containing the direction to be checked. It may be upstream (from UAS to UAC) or downstream (UAC to UAS). This function can be used from REQUEST_ROUTE. ... if (is_direction("upstream")) { xdbg("upstream request ($rm)\n"); } ...