Kamailio (OpenSER) Core CookBook for version 1.5.x

Main author:
   Daniel-Constantin Mierla <miconda (at) asipto.com>

This page is dedicated to Kamailio (OpenSER) core interaction with the configuration script (openser.cfg). These parameters, keywords, and functions are exported by Kamailio (OpenSER)'s core for use in configuration file.

This list is not complete yet. It will eventually, and with your help, that will happen sooner.

Please contribute only to the items you are sure you know what they mean.

Thank you!

IMPORTANT: This document is only valid for Kamailio (OpenSER) version 1.5.x.

IMPORTANT: To learn what variables can be used directly in configuration file see Pseudo variables list.

Keywords specific to SIP messages which can be used mainly in 'if' expressions.

The address family of the received SIP message. It is INET if the message was received over IPv4 or INET6 if the message was received over IPv6.

Exampe of usage:

  if(af==INET6) {
      log("Message received over IPv6 link\n");
  };

The IP of the local interface where the SIP message was received. When the proxy listens on many network interfaces, makes possible to detect which was the one that received the packet.

Example of usage:

 if(dst_ip==127.0.0.1) {
    log("message received on loopback interface\n");
 };

The local port where the SIP packet was received. When OpenSER is listening on many ports, it is useful to learn which was the one that received the SIP packet.

Example of usage:

   if(dst_port==5061)
   {
       log("message was received on port 5061\n");
   };

This script variable is a reference to the URI of 'From' header. It can be used to test 'From'- header URI value.

Example of usage:

  if(is_method("INVITE") && from_uri=~".*@kamailio.net")
  {
      log("the caller is from kamailio.net\n");
  };

The variable is a reference to the SIP method of the message.

Example of usage:

  if(method=="REGISTER")
  {
     log("this SIP request is a REGISTER message\n");
  };

The variable is a reference to the size of the message. It can be used in 'if' constructs to test message's size.

Example of usage:

  if(msg:len>2048)
  {
      sl_send_reply("413", "message too large");
      exit;
  };

It represents the value returned by last function executed (similar to $? from bash – if you wish, you can use also $? in OpenSER config, both names '$retcode' and '$?' are supported). If tested after a call of a route, it is the value retuned by that route.

Example of usage:

 route {
     route(1);
     if($retcode==1)
     {
         log("The request is an INVITE\n");
     };
 }

 
 route[1] {
     if(is_method("INVITE"))
         return(1);
     return(2);
 }

This variable can be used to test the transport protocol of the SIP message.

Example of usage:

  if(proto==UDP)
  {
      log("SIP message received over UDP\n");
  };

If used in onreply_route, this variable is a referece to the status code of the reply. If it used in a standard route block, the variable is a reference to the status of the last reply sent out for the current request.

Example of usage:

  if(status=="200")
  {
      log("this is a 200 OK reply\n");
  };

Reference to source IP address of the SIP message.

Example of usage:

  if(src_ip==127.0.0.1)
  {
      log("the message was sent from localhost!\n");
  };

Reference to source port of the SIP message (from which port the message was sent by previous hop).

Example of usage:

  if(src_port==5061)
  {
      log("message sent from port 5061\n");
  }

This variable can be used to test the value of URI from To header.

Example of usage:

if(to_uri=~"sip:.+@kamailio.net")
{
    log("this is a request for kamailio.net users\n");
};

This variable can be used to test the value of the request URI.

Example of usage:

  if(uri=~"sip:.+@kamailio.net")
  {
      log("this is a request for kamailio.net users\n");
  };

Values that can be used in 'if' expressions to check against Core Keywords

This keyword can be used to test whether the SIP packet was received over an IPv4 connection.

Example of usage:

  if(af==INET)
  {
      log("the SIP message was received over IPv4\n");
  };

This keyword can be used to test whether the SIP packet was received over an IPv6 connection.

Example of usage:

if(af==INET6)
{
    log("the SIP message was received over IPv6\n");
};

This keyword can be used to test the value of 'proto' and check whether the SIP packet was received over TCP or not.

Example of usage:

if(proto==TCP)
{
    log("the SIP message was received over TCP\n");
};

This keyword can be used to test the value of 'proto' and check whether the SIP packet was received over UDP or not.

Example of usage:

if(proto==UDP)
{
    log("the SIP message was received over UDP\n");
};

This keyword is set to the maximum size of an UDP packet. It can be used to test message's size.

Example of usage:

  if(msg:len>max_len)
  {
      sl_send_reply("413", "message too large to be forwarded over UDP without fragmentation");
      exit;
  }

It is a reference to the list of local IP addresses, hostnames and aliases that has been set in OpenSER configuration file. This lists contain the domains served by OpenSER.

The variable can be used to test if the host part of an URI is in the list. The usefulness of this test is to select the messages that has to be processed locally or has to be forwarded to another server.

See “alias” to add hostnames,IP addresses and aliases to the list.

Example of usage:

  if(uri==myself) {
      log("the request is for local processing\n");
  };

Can be used in assignment to reset the value of a per-script variable or to delete an avp.

Example of usage:

  $avp(i:12) = null;
  $var(x) = null;

Global parameters that can be set in configuration file. Accepted values are, depending on the actual parameters strings, numbers and yes/ no. If you need to specify either “yes” or “no” as part of a string, wrap this in double quotes.

It can be an IP address or string and represents the address advertised in Via header and other destination lumps (e.g RR header). If empty or not set (default value) the socket address from where the request will be sent is used.

WARNING: 
- don't set it unless you know what you are doing (e.g. nat traversal)
- you can set anything here, no check is made (e.g. foo.bar will be
accepted even if foo.bar doesn't exist)

Example of usage:

  advertised_address="kamailio.net"

The port advertised in Via header and other destination lumps (e.g. RR). If empty or not set (default value) the port from where the message will be sent is used. Same warnings as for 'advertised_address'.

Example of usage:

  advertised_port=5080

Parameter to set alias hostnames for the server. It can be set many times, each value being added in a list to match the hostname when 'myself' is checked.

It is necessary to include the port (the port value used in the “port=” or “listen=” defintions) in the alias definition otherwise the loose_route() function will not work as expected for local forwards

Example of usage:

    alias=other.domain.com:5060
    alias=another.domain.com:5060

Contains a multiple definition of aliases for AVP names.

Example of usage:

    avp_aliases="uuid=I:660;email=s:email_addr;fwd=i:753"

This parameter controls if aliases should be automatically discovered and added during fixing listening sockets. The auto discovered aliases are result of the DNS lookup (if listen is a name and not IP) or of a reverse DNS lookup on the listen IP.

Far backward compatibility reasons, the default value is “on”.

Example of usage:

  auto_aliases=no
  auto_aliases=0

Check if the address in top most via of replies is local. Default value is 0 (check disabled).

Example of usage:

  check_via=1 

Number of children to fork for the UDP interfaces (one set for each interface - ip:port). Default value is 8.

Example of usage:

  children=16

The value must be a valid path in the system. If set, OpenSER will chroot (change root directory) to its value.

Example of usage:

  chroot=/other/fakeroot

Set the debug level. Higher values make sip-router to print more debug messages. Log messages are usually sent to syslog, except logging to stderr was activated (see 'log_stderror' parameter).

The following log levels are defined:

 L_ALERT     -4
 L_BUG       -3
 L_CRIT2     -2
 L_CRIT      -1
 L_ERR        0
 L_WARN       1 
 L_NOTICE     2 
 L_INFO       3 
 L_DBG        4 

A log message will be logged if its log-level is lower than the defined debug level. Log messages are either produced by the the code, or manually in configuration script using log() or xlog() functions. For a production server you usually use a log value between -1 and 2.

Examples of usage:

• debug=3: print all log messages. This is only useful for debugging of problems. Note: this produces a lot of data and therefore should not be used on production servers (on a busy server this can easily fill up your hard disk with log messages)
• debug=0: This will only log warning, errors and more critical messages.
• debug=-6: This will disable all log messages.

Value of 'debug' parameter can also be get and set dynamically using 'debug' Core MI function, e.g.:

kamctl fifo debug

Further information can also be bound at: http://www.kamailio.org/dokuwiki/doku.php/tutorials:debug-syslog-messages

Can be 'yes' or 'no'. By default core dump limits are set to unlimited or a high enough value. Set this config variable to 'yes' to disable core dump-ing (will set core limits to 0).

Default value is 'no'.

Example of usage:

  disable_core_dump=yes

The DNS resolver, when configured with failover, can automatically store in a temporary blacklist the failed destinations. This will prevent (for a limited period of time) openser to send requests to destination known as failed. So, the blacklist can be used as a memory for the DNS resolver.

The temporary blacklist created by DNS resolver is named “dns” and it is by default selected for usage (no need use the use_blacklist()) function. The rules from this list have a life time of 4 minutes - you can change it at compile time, from blacklists.h .

Can be 'yes' or 'no'. By default the blacklist is disabled (Default value is 'yes').

Example of usage:

  disable_dns_blacklist=no

Can be 'yes' or 'no'. By default DNS-based failover is enabled. Set this config variable to 'yes' to disable the DNS-based failover. This is a global option, affecting the core and the modules also.

Default value is 'no'.

Example of usage:

  disable_dns_failover=yes

Global parameter to disable TCP support in the SIP server. Default value is 'no'.

Example of usage:

  disable_tcp=yes

See http://www.kamailio.net/docs/tls.html

This parameter controls if the SIP server should attempt to lookup its own domain name in DNS. If this parameter is set to yes and the domain name is not in DNS a warning is printed on syslog and a “received=” field is added to the via header.

Default is no.

Time in seconds before retrying a dns request. Default value is system specific, depends also on the '/etc/resolv.conf' content (usually 5s).

Example of usage:

  dns_retr_time=3

Number of dns retransmissions before giving up. Default value is system specific, depends also on the '/etc/resolv.conf' content (usually 4).

Example of usage:

  dns_retr_no=3

How many dns servers from the ones defined in '/etc/resolv.conf' will be used. Default value is to use all of them.

Example of usage:

  dns_servers_no=2

Can be 'yes' or 'no'. If it is set to 'yes' and a DNS lookup fails, it will retry it for ipv6 (AAAA record). Default value is 'no'.

Example of usage:

  dns_try_ipv6=yes

Can be 'yes' or 'no'. If set to 'no', the search list in '/etc/resolv.conf' will be ignored (⇒ fewer lookups ⇒ gives up faster). Default value is 'yes'.

HINT: even if you don't have a search list defined, setting this option to 'no' will still be “faster”, because an empty search list is in fact search “” (so even if the search list is empty/missing there will still be 2 dns queries, eg. foo+'.' and foo+“”+'.')

Example of usage:

  dns_use_search_list=no

Definition of a static (read-only) IP/destination blacklist. These lists can be selected from script (at runtime) to filter the outgoing requests, based on IP, protocol, port, etc.

Its primary purposes will be to prevent sending requests to critical IPs (like GWs) due DNS or to avoid sending to destinations that are known to be unavailable (temporary or permanent).

Example of usage:

   # filter out requests going to ips of my gws
   dst_blacklist = gw:{( tcp , 192.168.2.100 , 5060 , "" ),( any , 192.168.2.101 , 0 , "" )}
   # block requests going to "evil" networks
   dst_blacklist = net_filter:{ ( any , 192.168.1.100/255.255.255.0 , 0 , "" )}
   # block message requests with nasty words
   dst_blacklist = msg_filter:{ ( any , 192.168.20.0/255.255.255.0 , 0 , "MESSAGE*ugly_word" )}
   # block requests not going to a specific subnet
   dst_blacklist = net_filter2:{ !( any , 192.168.30.0/255.255.255.0 , 0 , "" )}

Each rule is defined by:

1. protocol : TCP, UDP, TLS or “any” for anything
2. port : number or 0 for any
3. ip/mask
4. test patter - is a filename like matching (see “man 3 fnmatch”) applied on the outgoing request buffer (first_line+hdrs+body)

If set to 'yes' the proxy will fork and run in daemon mode - one process will be created for each network interface the proxy listens to and for each protocol (TCP/UDP), multiplied with the value of 'children' parameter.

When set to 'no', the proxy will stay bound to the terminal and runs as single process. First interface is used for listening to. This is equivalent to setting the server option “-F”.

Default value is 'yes'.

Example of usage:

  fork=no

The group id to run OpenSER.

Example of usage:

group="openser"

Set the network addresses the SIP server should listen to. It can be an IP address, hostname or network iterface id or combination of protocol:address:port (e.g., udp:10.10.10.10:5060). This parameter can be set multiple times in same configuration file, the server listening on all addresses specified.

Example of usage:

  listen=10.10.10.10
  listen=eth1:5062
  listen=udp:10.10.10.10:5064

If you omit this directive then the SIP server will listen on all interfaces. On start the SIP server reports all the interfaces that it is listening on. Even if you specify only UDP interfaces here, the server will start the TCP engine too. If you don't want this, you need to disable the TCP support completly with the core parameter disable_tcp.

If OpenSER logs to syslog, you can control the facility for logging. Very useful when you want to divert all OpenSER logs to a different log file. See the man page syslog(3) for more details.

For more see: http://www.kamailio.org/dokuwiki/doku.php/tutorials:debug-syslog-messages

Default value is LOG_DAEMON.

Example of usage:

  log_facility=LOG_LOCAL0

Set the id to be printed in syslog. The value must be a string and has effect only when OpenSER runs in daemon mode (fork=yes), after daemonize. Default value is argv[0].

Example of usage:

  log_name="openser-5070"

With this parameter you can make OpenSER to write log and debug messages to standard error. Possible values are:

- “yes” - write the messages to standard error

- “no” - write the messages to syslog

Default value is “no”.

For more see: http://www.kamailio.org/dokuwiki/doku.php/tutorials:debug-syslog-messages

Example of usage:

  log_stderror=yes

The parameters set the value of maximum loops that can be done within a “while”. Comes as a protection to avoid infinite loops in config file execution. Default is 100.

Example of usage:

  max_while_loops=200

The size in bytes not to be exceeded during the auto-probing procedure of descovering the maximum buffer size for receiving UDP messages. Default value is 262144.

Example of usage:

  maxbuffer=65536

Log level to print memory debug info. It has be less than the value of 'debug' parameter if you want memory info to be logged. Default: memlog=L_DBG (4)

Example of usage:

  memlog=2

It can be 'yes' or 'no'. If set to 'yes', multicast datagram are sent over loopback. Default value is 'no'.

Example of usage:

  mcast_loopback=yes

Set the value for multicast ttl. Default value is OS specific (usually 1).

Example of usage:

  mcast_ttl=32

Set the server to try to locate outbound interface on multihomed host. This parameter affects the selection of the outgoing socket for forwarding requests. By default is off (0) - it is rather time consuming. (The implementation in kamailio version 1.5.4 has been considerably improved). When decativated, the incoming socket will be used or the first one for a different protocol, disregarding the destination location. When activated, Kamailio will select a socket that can reach the destination (to be able to connect to the remote address).

Example of usage:

  mhomed=1

Set the module search path. This can be used to simplify the loadmodule parameter

Example of usage:

  mpath="/usr/local/lib/openser/modules"
  loadmodule "mysql.so"
  loadmodule "uri.so"
  loadmodule "uri_db.so"
  loadmodule "sl.so"
  loadmodule "tm.so"
  ...

If set and bigger than the current open file limit, OpenSER will try to increase its open file limit to this number. Note: OpenSER must be started as root to be able to increase a limit past the hard limit (which, for open files, is 1024 on most systems).

Example of usage:

  open_files_limit=2048

The port the SIP server listens to. The default value for it is 5060.

Example of usage:

  port=5080

If it is set to 1, any local reply is sent to the address advertised in top most Via of the request. Default value is 0 (off).

Example of usage:

  reply_to_via=0

This parameter controls if the SIP server shold attempt to lookup its own IP address in DNS. If this parameter is set to yes and the IP address is not in DNS a warning is printed on syslog and a “received=” field is added to the via header.

Default is no.

The body of Server header field generated by OpenSER when it sends a request as UAS. It defaults to “OpenSer (<version> (<arch>/<os>))”.

Example of usage:

server_header="Server: My Company SIP Proxy"

Please note that you have to add the header name “Server:”, otherwise OpenSER will just write a header like:

My Company SIP Proxy

This parameter controls the “Server” header in any locally generated message.

Example of usage:

   server_signature=no

If it is enabled (default=yes) a header is generated as in the following example:

   Server: OpenSer (0.9.5 (i386/linux))

Can be 0 (default value) or 1. If set to 1 a 'Warning' header is added to each rely generated by OpenSER. The header contains several details that help troubleshooting using the network traffic dumps.

Example of usage:

  sip_warning=0

Number of children processes to be created for reading from TCP connections. If no value is explicitly set, the same number of TCP children as UDP children (see “children” parameter) will be used.

Example of usage:

  tcp_children=4

Time in seconds after a TCP connection will be closed if it is not available for writing in this interval (and OpenSER wants to send something on it). The default value is 10s.

Example of usage:

  tcp_send_timeout=3

Time in seconds before an ongoing attempt to connect will be aborted. The default value is 10s.

Example of usage:

  tcp_connect_timeout=5

Lifetime in seconds for TCP sessions. TCP sessions which are inactive for >tcp_connection_lifetime will be closed by openser. Default value is defined in tcp_conn.h: #define DEFAULT_TCP_CONNECTION_LIFETIME 120. Setting this value to 0 will close the TCP connection pretty quick . You can also set the TCP lifetime to the expire value of the REGISTER by using the tcp_persistent_flag parameter of the registrar module.

Example of usage:

  tcp_connection_lifetime=3600

maximum number of tcp connections (if the number is exceeded no new tcp connections will be accepted). Default is defined in tcp_conn.h: #define DEFAULT_TCP_MAX_CONNECTIONS 2048

Example of usage:

  tcp_max_connections=4096

poll method used (by default the best one for the current OS is selected). For available types see io_wait.c and poll_types.h: none, poll, epoll_lt, epoll_et, sigio_rt, select, kqueue, /dev/poll

Example of usage:

  tcp_poll_method=select

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

See http://kamailio.net/docs/tls.html

The TOS (Type Of Service) to be used for the sent IP packages (both TCP and UDP).

Example of usage:

  tos=IPTOS_LOWDELAY
  tos=0x10
  tos=IPTOS_RELIABILITY

The user id to run OpenSER (OpenSER will suid to it).

Example of usage:

  user="openser"

The body of User-Agent header field generated by OpenSER when it sends a request as UAC. It defaults to “OpenSer (<version> (<arch>/<os>))”.

Example of usage:

user_agent_header="User-Agent: My Company SIP Proxy"

Please note that you have to include the header name “User-Agent:” as OpenSER does not add it and you will get an erroneous header like:

My Company SIP Proxy

The working directory used by OpenSER at runtime. You might find it usefull when come to generating core files :)

Example of usage:

   wdir="/usr/local/openser"
   or
   wdir=/usr/openser_wd

Functions exported by core that can be used in route blocks.

Add 'rport' parameter to the Via header generated by server (see RFC3581 for its meaning). It affects only the current processed request.

Example of usage:

  add_local_rport()

Similarly to t_fork_to, it extends destination set by a new entry. The difference is that current URI is taken as new entry.

Without parameter, the function copies the current URI into a new branch. Thus, leaving the main branch (the URI) for further manipulation.

With a parameter, the function copies the URI in the parameter into a new branch. Thus, the current URI is not manipulated.

Note that it's not possible to append a new branch in “on_failure_route” block if a 6XX response has been previously received (it would be against RFC 3261).

Example of usage:

    # if someone calls B, the call should be forwarded to C too.
    #
    if (method=="INVITE" && uri=~"sip:B@xx.xxx.xx ")
    {
        # copy the current branch (branches[0]) into
        # a new branch (branches[1])
        append_branch();
        # all URI manipulation functions work on branches[0]
        # thus, URI manipulation does not touch the 
        # appended branch (branches[1])
        seturi("sip:C@domain");
        
        # now: branch 0 = C@domain
        #      branch 1 = B@xx.xx.xx.xx
        
        # and if you need a third destination ...
        
        # copy the current branch (branches[0]) into
        # a new branch (branches[2])
        append_branch();
        
        # all URI manipulation functions work on branches[0]
        # thus, URI manipulation does not touch the 
        # appended branch (branches[1-2])
        seturi("sip:D@domain");
        
        # now: branch 0 = D@domain
        #      branch 1 = B@xx.xx.xx.xx
        #      branch 2 = C@domain
        
        t_relay();
        exit;
    };

    # You could also use append_branch("sip:C@domain") which adds a branch with the new URI:
    
    
    if(method=="INVITE" && uri=~"sip:B@xx.xxx.xx ") {
        # append a new branch with the second destionation
        append_branch("sip:user@domain");
        # now: branch 0 = B@xx.xx.xx.xx
        # now: branch 1 = C@domain

        t_relay();
        exit;
}

Since v0.10.0-dev3, 'break' can no longer be used to stop the execution of a route. The only place to use is to end a 'case' block in a 'switch' statement. 'return' must be now used instead of old 'break'.

'return' and 'break' have now a similar meaning as in c/shell.

Stop the execution of the configuration script and alter the implicit action which is done afterwards.

If the function is called in a 'branch_route' then the branch is discarded (implicit action for 'branch_route' is to forward the request).

If the function is called in a 'onreply_route' then any provisional reply is discarded (implicit action for 'onreply_route' is to send the reply upstream according to Via header).

Example of usage:

  onreply_route {
      if(status=="183") {
          drop();
      }
  }

Stop the execution of the configuration script – it has the same behaviour as return(0). It does not affect the implicit action to be taken after script execution.

route {
  if (route(2)) {
    xlog("L_NOTICE","method $rm is INVITE\n");
  } else {
    xlog("L_NOTICE","method is $rm\n");
  };
}

route[2] {
  if (is_method("INVITE")) {
    return(1);
  } else if (is_method("REGISTER")) {
    return(-1);
  } else if (is_method("MESSAGE")) {
    sl_send_reply("403","IM not allowed");
    exit;
  };
}

Force_rport() adds the rport parameter to the first Via header. Thus, openser will add the received IP port to the top most via header in the SIP message, even if the client does not indicate support for rport. This enables subsequent SIP messages to return to the proper port later on in a SIP transaction.

The rport parameter is defined in RFC 3581.

Example of usage:

  force_rport();

Force OpenSER to send the message from the specified socket (it _must_ be one of the sockets OpenSER listens on). If the protocol doesn't match (e.g. UDP message “forced” to a TCP socket) the closest socket of the same protocol is used.

Example of usage:

  force_send_socket(10.10.10.10:5060);

force_tcp_alias(port)

adds a tcp port alias for the current connection (if tcp). Usefull if you want to send all the trafic to port_alias through the same connection this request came from [it could help for firewall or nat traversal]. With no parameters adds the port from the message via as the alias. When the “aliased” connection is closed (e.g. it's idle for too much time), all the port aliases are removed.

Forward the SIP request to the given destination in stateless mode. This has the format of [proto:]host[:port]. Host can be an IP or hostname; supported protocols are UDP, TCP and TLS. (For TLS, you need to compile the TLS support into core). If proto or port are not specified, NAPTR and SRV lookups will be used to determine them (if possible). Its important to keep in mind that this information is cached, so any changes in the DNS setup for this name during the runtime of the server are not recognized. If you want to avoid this, set the destination URI or request URI and call forward without parameters instead.

If the destination parameter is missing and no destination URI is set as well then the forwarding will be done based on the request URI.

Example of usage:

  forward("10.0.0.10:5060");
  #or
  forward();

Test if the dst_uri field (next hop address) is set.

Example of usage:

  if(isdsturiset()) {
      log("dst_uri is set\n");
  };

Test if a flag is set for current processed message (if the flag value is 1). The value of the parameter can be in range of 0..31.

For more see http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations or flags.

Example of usage:

  if(isflagset(3)) {
      log("flag 3 is set\n");
  };

Test if a flag is set for a specific branch (if the flag value is 1). The value of the “flag_idx” parameter can be in range of 0..31. “branch_idx” identify the branch for which the flags are tested - it must be a positive number. Branch index 0 refers to the RURI branch. If this parameter is missing, 0 branch index is used as default.

For more about script flags, see flags.

Example of usage:

  if(isbflagset(1,3)) {
      log("flag 3 is set in branch 1\n");
  };

Test if a script flag is set (if the flag value is 1). The value of the “flag_idx” parameter can be in range of 0..31.

For more about script flags, see flags.

Example of usage:

  if(issflagset(2)) {
      log("script flag 2 is set\n");
  };

Write text message to standard error terminal or syslog. You can specify the log level as first parameter.

For more see: http://www.kamailio.org/dokuwiki/doku.php/tutorials:debug-syslog-messages

Example of usage:

  log("just some text message\n");

Add the string parameter in front of username in R-URI.

Example of usage:

  prefix("00");

Prints the formatted 'string' in the AVP 'pv'. The 'string' parameter can include any pseudo-variable defined in OpenSER. The 'pv' can be any writable pseudo-variable – e.g.,: AVPs, VARs, $ru, $rU, $rd, $du, $br, $fs.

It was extended from the avp_printf(…) function exported in previous versions by the avpops module. Starting with 1.3.0, avp_printf(…) is just an alias to pv_printf(…).

Example of usage:

  pv_printf("$var(x)", "r-uri: $ru");
  pv_printf("$avp(i:3)", "from uri: $fu");

The return() function allows you to return any integer value from a called route() block. You can test the value returned by a route using $retcode variable.

return(0) is same as exit();

In bool expressions:

• Negative and ZERO is FALSE
• Positive is TRUE

Example usage:

route {
  if (route(2)) {
    xlog("L_NOTICE","method $rm is INVITE\n");
  } else {
    xlog("L_NOTICE","method $rm is REGISTER\n");
  };
}

route[2] {
  if (is_method("INVITE")) {
    return(1);
  } else if (is_method("REGISTER")) {
    return(-1);
  } else {
    return(0);
  };
}

Set the value of dst_uri filed to NULL. dst_uri field is usually set after loose_route() or lookup(“location”) if the contact address is behind a NAT.

Example of usage:

  resetdsturi();

Reset a flag for current processed message (set the value to 0). The value of the parameter can be in range of 0..31.

For more see http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations or flags.

Example of usage:

  resetflag(3);

Reset a flag for a specific branch (set flag to value 0). The value of the “flag_idx” parameter can be in range of 0..31. “branch_idx” identify the branch for which the flag is reset - it must be a positiv number. Branch index 0 refers to the RURI branch. If this parameter is missing, 0 branch index is used as default.

For more about script flags, see flags.

Example of usage:

  resetbflag(1,3);
  # or
  resetbflag(3); # same with resetbflag(0,3)

Reset a script flag (set flag to value 0). The value of the “flag_idx” parameter can be in range of 0..31.

For more about script flags, see flags.

Example of usage:

  resetsflag(2);

Set the R-URI to the value of the R-URI as it was when the request was received by server (undo all changes of R-URI).

Example of usage:

  revert_uri();

Rewrite the domain part of the R-URI with the value of function's parameter. Other parts of the R-URI like username, port and URI parameters remain unchanged.

Example of usage:

  rewritehost("1.2.3.4");

Rewrite the domain part and port of the R-URI with the value of function's parameter. Other parts of the R-URI like username and URI parameters remain unchanged.

Example of usage:

  rewritehostport("1.2.3.4:5080");

Rewrite the user part of the R-URI with the value of function's parameter.

Example of usage:

  rewriteuser("newuser");

Rewrite the password part of the R-URI with the value of function's parameter.

Example of usage:

  rewriteuserpass("my_secret_passwd");

Rewrites/sets the port part of the R-URI with the value of function's parameter.

Example of usage:

  rewriteport("5070");

Rewrite the request URI.

Example of usage:

  rewriteuri("sip:test@openser.org");

Send the original SIP message to a specific destination in stateless mode. This is definied as [proto:]host[:port]. No changes are applied to received message, no Via header is added. Host can be an IP or hostname; supported protocols are UDP, TCP and TLS. (For TLS, you need to compile the TLS support into core). If proto or port are not specified, NAPTR and SRV lookups will be used to determine them (if possible).

Parameter is mandatory and has string format.

Example of usage:

 send("udp:10.10.10.10:5070");

Same as 'advertised_address' but it affects only the current message. It has priority if 'advertised_address' is also set.

Example of usage:

  set_advertised_address("openser.org");

Same as 'advertised_port' but it affects only the current message. It has priority over 'advertised_port'.

Example of usage:

  set_advertised_port(5080);

Changes the debug level of the current process from script. If called without the parameter then the debug level of the current process will be reset to the global level. If the debug level of the current process is changed then changing the global debug level (using MI function) does not affect it, so be careful and make sure to reset the process debug level when you are done. This function is very helpful if you are tracing and debugging only a specific piece of code.

Example of usage:

  debug= -1 # errors only
  .....
  {
    ......
    setdebug(4); # set the debug level of the current process to DBG
    uac_replace_from(....);
    setdebug(); # reset the debug level of the current process to the global level
    .......
  }

Explicitely set the dst_uri field to the value of the paramater. The parameter has to be a valid SIP URI.

Example of usage:

  setdsturi("sip:10.10.10.10:5090");

Set a flag for current processed message. The value of the parameter can be in range of 0..31. The flags are used to mark the message for special processing (e.g., accounting) or to keep some state (e.g., message authenticated).

For more see http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations .

Example of usage:

  setflag(3);

Set a flag for a specific branch (set flag to value 1). The value of the “flag_idx” parameter can be in range of 0..31. “branch_idx” identify the branch for which the flag is set - it must be a positiv number. Branch index 0 refers to the RURI branch. If this parameter is missing, 0 branch index is used as default.

For more about script flags, see flags.

Example of usage:

  setbflag(1,3);
  # or
  setbflag(3); # same with setbflag(0,3)

Set a script flag (set flag to value 0). The value of the “flag_idx” parameter can be in range of 0..31.

For more about script flags, see flags.

Example of usage:

  setsflag(2);

Strip the first N-th characters from username of R-URI (N is the value of the parameter).

Example of usage:

  strip(3);

Strip the last N-th characters from username of R-URI (N is the value of the parameter).

Example of usage:

strip_tail(3);

Gets or sets value of debug core variable.

Examples of usage:

  kamctl fifo debug
  kamctl fifo debug 1

Request routing block. It contains a set of actions to be taken for SIP requests.

The main 'route' block identified by 'route{…}' or 'route[0]{…}' is executed for each SIP request.

The implicit action after execution of the main route block is to drop the SIP request. To send a reply or forward the request, explicit actions must be called inside the route block.

Example of usage:

  route {
       if(is_method("OPTIONS")) {
          # send reply for each options request
          sl_send_reply("200", "ok");
          exit();
       }
       route(1);
  }
  route[1] {
       # forward according to uri
       forward();
  }

Note that if a 'route(X)' is called from a 'branch_route[Y]' then in 'route[X]' is just processed each separate branch instead of all branches together as occurs in main route.

Request's branch routing block. It contains a set of actions to be taken for each branch of a SIP request. It is executed only by TM module after it was armed via t_on_branch(“branch_route_index”).

Example of usage:

  route {
      lookup("location");
      t_on_branch("1");
      if(!t_relay()) {
          sl_send_reply("500", "relaying failed");
      }
  }
  branch_route[1] {
      if(uri=~"10\.10\.10].10") {
          # discard branches that go to 10.10.10.10
          drop();
      }
  }

Failed transaction routing block. It contains a set of actions to be taken each transaction that received only negative replies (>=300) for all branches. The 'failure_route' is executed only by TM module after it was armed via t_on_failure(“failure_route_index”).

Note that in 'failure_route' is processed the request that initiated the transaction, not the reply .

Example of usage:

  route {
      lookup("location");
      t_on_failure("1");
      if(!t_relay()) {
          sl_send_reply("500", "relaying failed");
      }
  }
  failure_route[1] {
      if(is_method("INVITE")) {
           # call failed - relay to voice mail
           t_relay_to_udp("voicemail.server.com","5060");
      }
  }

Reply routing block. It contains a set of actions to be taken for SIP replies.

The main 'onreply_route' identified by 'onreply_route {…}' or 'onreply_route[0] {…}' is executed for all replies received.

Certain 'onreply_route' blocks can be executed by TM module for special replies. For this, the 'onreply_route' must be armed for the SIP requests whose replies should be processed within it, via t_on_reply(“onreply_route_index”).

Main 'onreply_route' block is executed before a possible tm 'onreply_route' block.

route {
    lookup("location");
    t_on_reply("1");
    if(!t_relay()) {
        sl_send_reply("500", "relaying failed");
    }
}

onreply_route {
    if(!t_check_trans()) {
        drop;
    }
}

onreply_route[1] {
    if(status=~"1[0-9][0-9]") {
         log("provisional response\n");
    }
}

The error route is executed automatically when a parsing error occurred during SIP request processing. This allow the administrator to decide what to do in case of error.

In error_route, the following pseudo-variables are available to get access to error details: * $(err.class) - the class of error (now is '1' for parsing errors) * $(err.level) - severity level for the error * $(err.info) - text describing the error * $(err.rcode) - recommended reply code * $(err.rreason) - recommended reply reason phrase

  error_route {
     xlog("--- error route class=$(err.class) level=$(err.level)
            info=$(err.info) rcode=$(err.rcode) rreason=$(err.rreason) ---\n");
     xlog("--- error from [$si:$sp]\n+++++\n$mb\n++++\n");
     sl_send_reply("$err.rcode", "$err.rreason");
     exit;
  }

Different constructs that help to select specific actions to be executed.

IF-ELSE statement

Prototype:

    if(expr) {
       actions;
    } else {
       actions;
    }

The 'expr' should be a valid logical expression.

The logical operators that can be used in 'expr':

* == - equal * != - not equal * =~ - regular expression matching * !~ - regular expression not-matching * > - greater * >= - greater or equal * < - less * ⇐ - less or equal * && - logical AND * || - logical OR * ! - logical NOT * [ … ] - test operator - inside can be any arithmetic expression

Example of usage:

  if(is_method("INVITE"))
  {
      log("this sip message is an invite\n");
  } else {
      log("this sip message is not an invite\n");
  }

SWITCH statement - it can be used to test the value of a pseudo-variable.

IMPORTANT NOTE: 'break' can be used only to mark the end of a 'case' branch (as it is in shell scripts). If you are trying to use 'break' outside a 'case' block the script will return error – you must use 'return' there.

Example of usage:

    route {
        route(1);
        switch($retcode)
        {
            case -1:
                log("process INVITE requests here\n");
            break;
            case 1:
                log("process REGISTER requests here\n");
            break;
            case 2:
            case 3:
                log("process SUBSCRIBE and NOTIFY requests here\n");
            break;
            default:
                log("process other requests here\n");
       }

        # switch of R-URI username
        switch($rU)
        {
            case "101":
                log("destination number is 101\n");
            break;
            case "102":
                log("destination number is 102\n");
            break;
            case "103":
            case "104":
                log("destination number is 103 or 104\n");
            break;
            default:
                log("unknown destination number\n");
       }
    }

    route[1]{
        if(is_method("INVITE"))
        {
            return(-1);
        };
        if(is_method("REGISTER"))
            return(1);
        }
        if(is_method("SUBSCRIBE"))
            return(2);
        }
        if(is_method("NOTIFY"))
            return(3);
        }
        return(-2);
    }

NOTE: take care while using 'return' - 'return(0)' stops the execution of the script.

while statement

Example of usage:

  
  $var(i) = 0;
  while($var(i) < 10)
  {
      xlog("counter: $var(i)\n");
      $var(i) = $var(i) + 1;
  }

Starting with 1.2.0, assignments together with string and arithmetic operations can be done directly in configuration file.

Assignments can be done like in C, via '=' (equal). The following pseudo-variables can be used in left side of an assignment: * AVPs - to set the value of an AVP * script variables ($var(…)) - to set the value of a script variable * shared variables ($shv(…)) * $ru - to set R-URI * $rd - to set domain part of R-URI * $rU - to set user part of R-URI * $rp - to set the port of R-URI * $du - to set dst URI * $fs - to set send socket * $br - to set branch * $mf - to set message flags value * $sf - to set script flags value * $bf - to set branch flags value

$var(a) = 123;

There is a special assign operator ':=' (colon equal) that can be used with AVPs. If the right value is 'null', all AVPs with that name are deleted. If different, the new value will overwrite any existing values for the AVPs with than name (on other words, delete existing AVPs with same name, add a new one with the right side value).

$avp(i:3) := 123;

For strings, '+' is available to concatenate.

$var(a) = "test";
$var(b) = "sip:" + $var(a) + "@" + $fd;

For numbers, one can use:

* + : plus * - : minus * / : divide * * : multiply * % : modulo * | : bitwise OR * & : bitwise AND * ^ : bitwise XOR * ~ : bitwise NOT * « : bitwise left shift * » : bitwise right shift

Example:

$var(a) = 4 + ( 7 & ( ~2 ) );

NOTE: to ensure the priority of operands in expression evaluations do use parenthesis.

Arithmetic expressions can be used in condition expressions via test operator ' [ … ] '.

if( [ $var(a) & 4 ] )
    log("var a has third bit set\n");