siputils

The following modules must be loaded before this module:

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

Timeout value in seconds, define how long the call-id is stored in the internal list kept for replacing 183 messages with 180. A reasonable value is “30”.

Default value is “0”. This means functionality is disabled.

...
modparam("siputils", "ring_timeout", 30)
...

This parameter is the content of the Accept header field. Note: it is not clearly written in RFC3261 if a proxy should accept any content (the default “*/*”) because it does not care about content. Or if it does not accept any content, which is “”.

Default value is “*/*”.

...
modparam("siputils", "options_accept", "application/*")
...

This parameter is the content of the Accept-Encoding header field. Please do not change the default value because Kamailio does not support any encodings yet.

Default value is “”.

...
modparam("siputils", "options_accept_encoding", "gzip")
...

First char of this parameter is used as separator for encoding/decoding Contact header.

Default value is “*”.

...
modparam("siputils", "contact_flds_separator", "-")
...

then an encoded uri might look sip:user-password-ip-port-protocol@PublicIP

This parameter is the content of the Accept-Language header field. You can set any language code which you prefer for error descriptions from other devices, but presumably there are not much devices around which support other languages then the default English.

Default value is “en”.

...
modparam("siputils", "options_accept_language", "de")
...

This parameter is the content of the Support header field. Please do not change the default value, because Kamailio currently does not support any of the SIP extensions registered at the IANA.

Default value is “”.

...
modparam("siputils", "options_support", "100rel")
...

Prefix to be added to Remote-Party-ID header field just before the URI returned from either radius or database.

Default value is “”.

modparam("auth", "rpid_prefix", "Whatever <")

Suffix to be added to Remote-Party-ID header field after the URI returned from either radius or database.

Default value is “;party=calling;id-type=subscriber;screen=yes”.

modparam("auth", "rpid_suffix", "@1.2.3.4>")

Full AVP specification for the AVP which stores the RPID value. It used to transport the RPID value from authentication backend modules (auth_db or auth_radius) or from script to the auth function append_rpid_hf and is_rpid_user_e164.

If defined to NULL string, all RPID functions will fail at runtime.

Default value is “$avp(s:rpid)”.

modparam("auth", "rpid_avp", "$avp(myrpid)")

Inserting the call-id in the internal list, which is checked when further replies arrive. Any 183 reply that is received during the timeout value will be converted to a 180 message. Please note that you need to set a positive timeout value in order to use this function.

The function returns TRUE on success, and FALSE during processing failures.

This function can be used from REQUEST_ROUTE and FAILURE_ROUTE.

...
ring_insert_callid();
...

This function checks if the request method is OPTIONS and if the request URI does not contain an username. If both is true the request will be answered stateless with “200 OK” and the capabilities from the modules parameters.

It sends “500 Server Internal Error” for some errors and returns false if it is called for a wrong request.

The check for the request method and the missing username is optional because it is also done by the function itself. But you should not call this function outside the myself check because in this case the function could answer OPTIONS requests which are sent to you as outbound proxy but with an other destination then your proxy (this check is currently missing in the function).

This function can be used from REQUEST_ROUTE.

...
if (uri==myself) {
	if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) {
		options_reply();
	}
}
...

Check if the username in credentials matches the given username.

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE.

...
if (is_user("john")) {
	...
};
...

Check if To header field uri contains tag parameter.

This function can be used from REQUEST_ROUTE.

...
if (has_totag()) {
	...
};
...

Find if Request URI has a given parameter with no value

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE.

...
if (uri_param("param1")) {
	...
};
...

Find if Request URI has a given parameter with matching value

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE.

...
if (uri_param("param1","value1")) {
	...
};
...

Add to RURI a parameter (name=value);

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE.

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

Converts RURI, if it is tel URI, to SIP URI. Returns true only if conversion succeeded or if no conversion was needed (like RURI was not tel URI).

The conversion follows the rules in RFC 3261 section 19.1.6:

The SIP URI host is formed using the From URI host.

This function can be used from REQUEST_ROUTE.

...
# RURI:  tel:+(34)-999-888-777
tel2sip();
# RURI:  sip:+34999888777@foo.com;user=phone

# RURI:  tel:+12-(34)-56-78;Ext=200;ISUB=+123-456
tel2sip();
# RURI:  sip:+12345678;ext=200;isub=+123-456@foo.com;user=phone
...

Checks if string value of pseudo variable argument is an E164 number.

This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, and LOCAL_ROUTE.

...
if (is_164("$fU")) {  # Check From header URI user part
   ...
}
if (is_e164("$avp(i:705)") {
   # Check stgring value stored in avp i:705
   ...
};
...

Checks if userpart of URI stored in pseudo variable is E164 number.

This function can be used from REQUEST_ROUTE and FAILURE_ROUTE.

...
if (is_uri_user_e164("$fu")) {  # Check From header URI user part
   ...
}
if (is_uri_user_e164("$avp(i:705)") {
   # Check user part of URI stored in avp i:705
   ...
};
...

This function will encode uri-s inside Contact header in the following manner sip:username:password@ip:port;transport=protocol goes sip:encoding_prefix*username*ip*port*protocol@hostpart.

* is the default separator and can be changed by setting the contact_flds_separator module parameter.

Note: This function discards all of the URI parameters. Thus, none of the paramters (except the transport parameter which is encoded into the userpart) can be restored.

The function returns negative on error, 1 on success.

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE.

...
if (src_ip == 10.0.0.0/8) encode_contact("natted_client","1.2.3.4"); 
...

This function will decode the request URI. If the RURI is in the format sip:encoding_prefix*username*ip*port*protocol@hostpart it will be decoded to sip:username:password@ip:port;transport=protocol It uses the default set parameter for contact encoding separator.

The function returns negative on error, 1 on success.

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE.

...
if (uri =~ "^sip:natted_client") { decode_contact(); }
...

This function will decode URIs inside Contact header. If the URI in the format sip:encoding_prefix*username*ip*port*protocol@hostpart it will be decoded to sip:username:password@ip:port;transport=protocol. It uses the default set parameter for contact encoding separator.

The function returns negative on error, 1 on success.

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE.

...
reply_route[2] {
	...
	decode_contact_header();
	...
}
...

The function returns true if the two parameters matches as SIP URI.

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, FAILURE_ROUTE and BRANCH_ROUTE.

...
if(cmp_uri("$ru", "sip:kamailio@kamailio.org"))
{
    # do interesting stuff here
}
...

The function returns true if the two parameters matches as AoR. The parameters have to be SIP URIs.

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, FAILURE_ROUTE and BRANCH_ROUTE.

...
if(cmp_aor("$rU@KaMaIlIo.org", "sip:kamailio@$fd"))
{
    # do interesting stuff here
}
...

The function checks if the SIP URI received from the database or radius server and will potentially be used in Remote-Party-ID header field contains an E164 number (+followed by up to 15 decimal digits) in its user part. Check fails, if no such SIP URI exists (i.e. radius server or database didn't provide this information).

This function can be used from REQUEST_ROUTE.

...
if (is_rpid_user_e164()) {
    # do something here
};
...

Appends to the message a Remote-Party-ID header that contains header 'Remote-Party-ID: ' followed by the saved value of the SIP URI received from the database or radius server followed by the value of module parameter radius_rpid_suffix. The function does nothing if no saved SIP URI exists.

This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE.

...
append_rpid_hf();  # Append Remote-Party-ID header field
...

This function is the same as Section 4.17, “ append_rpid_hf()”. The only difference is that it accepts two parameters--prefix and suffix to be added to Remote-Party-ID header field. This function ignores rpid_prefix and rpid_suffix parameters, instead of that allows to set them in every call.

Meaning of the parameters is as follows:

This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE.

...
# Append Remote-Party-ID header field
append_rpid_hf("", ";party=calling;id-type=subscriber;screen=yes");
...