$Revision: 1525 $ $Date: 2007-01-19 12:04:29 +0200 (Fri, 19 Jan 2007) $

Exec module allows to start an external command from a &ser; script. The commands may be any valid shell commands--the command string is passed to shell using popen command. &ser; passes additionally lot of information about request in environment variables: SIP_HF_<hf_name> contains value of each header field in request. If a header field occurred multiple times, values are concatenated and comma-separated. <hf_name> is in capital letters. Ff a header-field name occurred in compact form, <hf_name> is canonical. SIP_TID is transaction identifier. All request retransmissions or CANCELs/ACKs associated with a previous INVITE result in the same value. SIP_DID is dialog identifier, which is the same as to-tag. Initially, it is empty. SIP_SRCIP is source &ip; address from which request came. SIP_ORURI is original request &uri;. SIP_RURI is current request &uri; (if unchanged, equal to original). SIP_USER is userpart of current request &uri;. SIP_OUSER is userpart of original request &uri;.

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.

Turn off to disable setting environment variables for executed commands. Default value is 1. ... modparam("exec", "setvars", 1) ...

Specifies the longest time a program is allowed to execute. If the time is exceeded, the program is killed. Default value is 0. ... modparam("exec", "time_to_kill", 20) ...

Executes an external command. Current &uri; is passed to the command as parameter. Output of the command is considered &uri; set (separated by lines). Meaning of the parameters is as follows: command - Command to be executed. It can include pseudo- variabes; WARNING: if the var you are passing out has a bash special character in it, the var needs to be placed inside quotes, for ex: exec_msg("print-contact.sh '$ct'"); This function can be used from REQUEST_ROUTE, FAILURE_ROUTE. ... exec_dset("echo TEST > /tmp/test.txt"); exec_dset("echo TEST > /tmp/$rU.txt"); ...

Executes an external command. The whole message is passed to it in input, no command-line parameters are added, output of the command is not processed. See sip-server/modules/exec/etc/exec.cfg in the source tarball for information on usage. Meaning of the parameters is as follows: command - Command to be executed. It can include pseudo-variables. WARNING: if the var you are passing out has a bash special character in it, the var needs to be placed inside quotes, for ex: exec_msg("print-contact.sh '$ct'"); This function can be used from REQUEST_ROUTE, FAILURE_ROUTE. ... exec_dset("echo TEST > /tmp/test.txt"); exec_dset("echo TEST > /tmp/$rU.txt"); ...

Executes an external command. Each line from output of the command is saved in an AVP from 'avplist'. If 'avplist' is missing, the AVP are named 1, 2, 3, ... Meaning of the parameters is as follows: command - Command to be executed. It can include pseudo- variabes; avplist - comma separated list with AVP names to store the result in; WARNING: if the var you are passing out has a bash special character in it, the var needs to be placed inside quotes, for ex: exec_msg("print-contact.sh '$ct'"); This function can be used from REQUEST_ROUTE, FAILURE_ROUTE. ... exec_avp("echo TEST"); exec_avp("echo TEST", "$avp(s:test)"); ...

There is currently no guarantee that scripts ever return and stop blocking &sip; server. (There is kill.c but it is not used along with the current mechanisms based on popen. Besides that kill.c is ugly).