topology_hiding Module

The following modules must be loaded before this module:

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

The string password that will be used for encoding/decoding the callid in case of topology_hiding with callid mangling.

Default value is “"OpenSIPS"”

...
modparam("topology_hiding", "th_callid_passwd", "my_topo_hiding_secret")
...

The prefix that will be used for detecting callids which have been encoded by the dialog topology hiding. Make sure to change this value in case your SIP path contains multiple OpenSIPS boxes with topology hiding.

Default value is “"DLGCH_"”

...
modparam("topology_hiding", "th_callid_prefix", "MYCALLIDPREFIX_")
...

List of semicolon-separated Contact URI parameters that will be passed from one side to the other for topology hiding calls. To be used when end-to-end functionality uses such Contact URI parameters.

Default value is “empty” - do not pass any parameters

...
modparam("topology_hiding", "th_passed_contact_uri_params", "paramname1;myparam;custom_param")
...

List of semicolon-separated Contact header parameters that will be passed from one side to the other for topology hiding calls. To be used when end-to-end functionality uses such Contact header parameters.

Default value is “empty” - do not pass any parameters

...
modparam("topology_hiding", "th_passed_contact_params", "paramname1;myparam;custom_param")
...

If set to 1, the module will internally create the dialog ( if not already created ). This will only work for INVITE based dialogs, and the dialog module must be loaded.

Default value is “0”

...
modparam("topology_hiding", "force_dialog", 1)
...

When not relying on the dialog module ( due to script writer preference or simply when doing topo hiding for non INVITE dialogs ), the module will store the needed information in a Contact URI param. The parameter configures the string password that will be used for encoding/decoding that specific param .

Default value is “"ToPoCtPaSS"”

...
modparam("topology_hiding", "th_contact_encode_passwd", "my_topoh_passwd")
...

When not relying on the dialog module ( due to script writer preference or simply when doing topo hiding for non INVITE dialogs ), the module will store the needed information in a Contact URI param. The parameter configures the respective parameter name.

Default value is “"thinfo"”

...
modparam("topology_hiding", "th_contact_encode_param", "customparam")
...

When not relying on the dialog module ( due to script writer preference or simply when doing topo hiding for non INVITE dialogs ), the module will store the needed information in a Contact URI param. This parameter configures the encoding scheme to be used for the data stored in the Contact URI param. Possible values are:

Default value is “"base64"”

...
modparam("topology_hiding", "th_contact_encode_scheme", "base32")
...

By calling this function on an initial request, the modules will hide the topology, meaning that it will strip and restore all the Via, Record-Route and Route headers and it will replace the contact with the IP address of the interface where the request was received.

You must note however, that the detection of the future in-dialog requests(BYE, reInvite, etc.) for these dialogs on which topology hiding is applied, is not done automatically. Without topology hiding and only normal dialog, the detection was done when loose_route was called. But now, for this dialogs where topology hiding is applied, the in dialog requests reaching OpenSIPS won't have any Route headers and the RURI will point to OpenSIPS machine. So, to be able to match the in-dialog requests to the corresponding dialog, a script function must be called. It's name is topology_hiding_match and you can read it's description above. The in-dialog topology requests are requests with a to tag, RURI pointing to opensips and with a method specific to a Invite dialog. For this kind of requests you should call topology_hiding_match() function. If the request is successfully matched and fixed as according to the topology hiding logic,the function returns success.

Optionally,the function also receives a string parameter, which holds string flags. Current options for the string flags are :

...
if(!has_totag() && is_method("INVITE")) {
	topology_hiding();
}
...
...
if(!has_totag() && is_method("INVITE")) {
	topology_hiding("U");
}
...

...
if (has_totag())
        if(topology_hiding_match())
        {
                xlog("Found a request $rm belonging to an existing topology hiding dialog\n");
                route(relay);
                exit;
        }
}
...

This function is to be used to match and fix a sequential request belong to an existing topology hiding dialog.

With regards to dialog matching (including the optional parameter), this function behaves identically to match_dialog(). Please see the dialog module documentation for further details regarding dialog matching options.

The function returns true if a topology hiding dialog exists for the request and the request has been successfully fixed.

This function can be used from REQUEST_ROUTE.

...
    if (has_totag()) {
        if (!topology_hiding_match() ) {
            xlog(" cannot match request to a dialog \n");
	    send_reply(404,"Not found");
        } else
		route(RELAY);
    }
...

Read only variable that will contain the callid as it is propagated towards the callee side, in case topology_hiding("C") is called.

NULL will be returned if there is no topology hiding dialog for the request or if topology_hiding with callid encoding was not used for the current dialog.