The following modules must be loaded before this module:

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

Type of storage, valid types are:

Default value is “db”.

...
modparam("topos", "storage", "redis")
...

Database URL.

Default value is “mysql://kamailio:kamailiorw@localhost/kamailio”.

...
modparam("topos", "db_url", "dbdriver://username:password@dbhost/dbname")
...

Whether to encode the Call-id: header. Some SIP extensions include the Call-id in the SIP message payload or header, so it is safe to not encode Call-id in such cases. Well-known extensions such as call transfer or conference join will be added to work with encoded Call-id. Topoh module should be loaded with use_mode paramerter set to 1

Default value is 0 (do not mask).

...
modparam("topos", "mask_callid", 1)
...

If set to 1, topos module will bind to sanity module in order to perform sanity checks over received SIP request. Default sanity checks are done. It is useful to check if received request is well formatted before proceeding to encoding/decoding.

Default value is 0 (do not bind to sanity module).

...
modparam("topos", "sanity_checks", 1)
...

Interval in seconds after which the branch records are deleted.

Default value is 180 (3 min).

...
modparam("topos", "branch_expire", 300)
...

Interval in seconds after which the dialog records are deleted. Keep in mind that the module does not update the dialog timestamp after the initial call setup on re-INVITEs or other in-dialog messages. So set a large enough value (according your longest call duration) to prevent problems in re-writing messages. This key is only relevant for INVITE dialog. SUBSCRIBE dialog records lifetime are based on value set in expires header. Moreover each re-SUBSCRIBEs update the dialog timestamp.

Default value is 10800 (3 hours).

...
modparam("topos", "dialog_expire", 3600)
...

Interval in seconds to run the clean up of stored records.

Default value is 60 (1 min).

...
modparam("topos", "clean_interval", 30)
...

The name of the function in the KEMI configuration file (embedded scripting language such as Lua, Python, ...) to be executed instead of event_route[...] blocks.

The function receives a string parameter with the name of the event.

Default value is 'empty' (no function is executed for events).

...
modparam("topos", "event_callback", "ksr_topos_event")
...
-- event callback function implemented in Lua
function ksr_topos_event(evname)
	KSR.info("===== topos module triggered event: " .. evname .. "\n");
	return 1;
end
...

Control what event_route blocks to be executed. It is a bitmask of: 1 - execute event_route[topos:msg-outgoing]; 2 - execute event_route[topos:msg-sending]; 4 execute event_route[topos:msg-incoming]; 8 execute event_route[topos:msg-receiving];.

Default value is 3 (execute both event_route blocks).

...
modparam("topos", "event_mode", 2)
...

You may need to control the host part of the Contact header added by topos. If the xavu_field_contact_host parameter is set, this value is ignored. For example when using TLS with TOPOS the remote UAS must be able to open a new TLS socket to the contact header. In this case, the contact header must contain a domain name with a trusted CA signed certitificate.

Default value is taken from the Record-Route URI.

...
modparam("topos", "contact_host", "proxy.domain.com")
...

Control the mode where the key to lookup the message data from the database or redis server is stored. The default is to use the Contact user (0), alternatively a Contact URI parameter can be used (1) with values from the SIP message, or from AVP variables (2). This can be useful for interoperating which gateways that need a certain user part in the Contact URI.

In mode (1) the a-side contact user is taken from the request URI and the b-side contact user from the Contact header of the processed initial SIP request.

If you use the mode (2), you need to configure the xavu_field_a_contact and xavu_field_b_contact parameter. Furthermore you need to assign values to them during the processing of the initial SIP request.

The name of the Contact URI parameter can be customized with the cparam_name parameter.

Default value is 0 - use the Contact user

...
modparam("topos", "contact_mode", 1)
...

Name of the Contact URI parameter to store the database or redis server key for message lookup.

This parameter is only used when the contact_mode parameter is set to 1 or 2.

Default value is “tps”.

...
modparam("topos", "cparam_name", "xyz")
...

Name of root XAVU to hold config-specific values to be used by module at runtime.

Note: this parameter must be set if any other parameter prefixed with `xavu_field_` is used.

Default value is “NULL” (disabled).

...
modparam("topos", "xavu_cfg", "_tps_")
modparam("topos", "xavu_field_a_contact", "a_contact")
...
    $xavu(_tps_=>a_contact) = "...";
...

Name of the field inside root XAVU specifed by `xavu_cfg` to evaluate for the A-side Contact Header user part. This parameter is only necessary in contact_mode (2).

Default value is “NULL” (disabled).

...
modparam("topos", "xavu_cfg", "_tps_")
modparam("topos", "xavu_field_a_contact", "a_contact")
...
    $xavu(_tps_=>a_contact) = "...";
...

Name of the field inside root XAVU specifed by `xavu_cfg` to evaluate for the B-side Contact Header user part. This parameter is only necessary in contact_mode (2).

Default value is “NULL” (disabled).

...
modparam("topos", "xavu_cfg", "_tps_")
modparam("topos", "xavu_field_b_contact", "b_contact")
...
    $xavu(_tps_=>b_contact) = "...";

...

Control from where to take the host part of the Contact header added by topos. This parameter allows to take the value from an XAVU during run-time, it specifies the field inside XAVU "xavu_cfg". If this parameter is set, the contact_host parameter is ignored. For example when using TLS with TOPOS the remote UAS must be able to open a new TLS socket to the contact header. In this case, the contact header must contain a domain name with a trusted CA signed certitificate.

Default value is empty, not set.

...
modparam("topos", "xavu_cfg", "_tps_")
modparam("topos", "xavu_field_contact_host", "contact_host")
...
    $xavu(_tps_=>contact_host) = "kamailio.org";
...

If set to 1, topos module will track and update record route changes on re-invite.

Default value is 0 (do not update record route changes within dialog).

...
modparam("topos", "rr_update", 1)
...

Set the global context for topos instance.

The value has to be maximum 12 characters.

Default value is “NULL” (disabled).

...
modparam("topos", "context", "srvone")
...

List of SIP methods to skip adding Contact header for.

Default value is “BYE,CANCEL,PRACK”.

...
modparam("topos", "methods_nocontact", "CANCEL,PRACK")
...

List of headers to disable multiple comma separated values inserted in compact form. Altough compact form is RFC compliant this paramter gives possibilty to disable compact form header values for UA that don't support or can't handle it. The following options are available: (1) - disable multiple comma separated values for Via header (2) - disable multiple comma separated values for Record-Route header (4) - disable multiple comma separated values for Route header

Default value is “0”.

...
modparam("topos", "header_mode", 1)
...

List of SIP methods to skip doing topos if it is an intial request (no To-tag).

Default value is “” (no method).

...
modparam("topos", "methods_noinitial", "OPTIONS,NOTIFY")
...

Update the context at runtime. If the value is emtpy string, then the runtime context is reset.

This function can be used from ANY_ROUTE.

...
request_route {
    ...
    tps_set_context("srvone");
    ...
}
...

It is executed before doing topology stripping processing for an outgoing SIP message. If 'drop' is executed inside the event route, then the module skips doing the topology hiding.

Inside the event route the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the destination. The SIP message is not the one to be sent out, but an internally generated one at startup, to avoid reparsing the outgoing SIP message for the cases when topology hiding is not wanted.

...
event_route[topos:msg-outgoing] {
  if($sndto(ip)=="10.1.1.10") {
    drop;
  }
}
...

It is executed before doing topology stripping processing for a SIP message to be sent out, being executed after event_route[topos:msg-outgoing].

Inside the event route the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the destination. The SIP message is the one to be sent out.

...
event_route[topos:msg-sending] {
  if(is_request() and $fU=="alice") {
    drop;
  }
}
...

It is executed before doing topology stripping processing for an incoming SIP message. If 'drop' is executed inside the event route, then the module skips doing the topology hiding.

Inside the event route the variables $si, $sp and $proto point to the source address. The SIP message is not the one to be sent out, but an internally generated one at startup, to avoid reparsing the outgoing SIP message for the cases when topology hiding is not wanted.

...
event_route[topos:msg-incoming] {
  if($si=="10.1.1.10") {
    drop;
  }
}
...

It is executed before doing topology stripping processing for a SIP message that was received, being executed after event_route[topos:msg-incoing].

Inside the event route the variables $si, $sp and $proto point to the source address. The SIP message is the one to be sent out.

...
event_route[topos:msg-receiving] {
  if(is_request() and $fU=="alice") {
    drop;
  }
}
...