exec_dst(command)exec_msg(command)exec_dst usageexec_msg usageExec 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 additionaly lot of information about request in environment variables:
SIP_HF_<hf_name> contains value of each header field in request. If a header field occured multiple times, values are concatenated and comma-separated. <hf_name> is in capital letters. Ff a header-field name occured 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.
Specifies the longest time a program is allowed to execute. If the time is exceeded, the program is killed.
Default value is 0.
exec_dst(command)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.
exec_msg(command)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_router/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.
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).
The module does not provide any sort of API to use in other SER modules.
Take a look at http://iptel.org/ser.
First at all check if your question was already answered on one of our mailing lists:
E-mails regarding any stable version should be sent to <serusers@iptel.org> and e-mail
regarding development versions or CVS snapshots should be send to <serdev@iptel.org>.
If you want to keep the mail private, send it to <serhelp@iptel.org>.
Please follow the guidelines provided at: http://iptel.org/ser/bugs