Provided by: ser_2.0.0-4ubuntu4_i386
ser - very fast and configurable sip proxy
ser [ -hcrRvdDEVT ] [ -f config-file ] [ -l address ] [ -n processes-no
] [ -N tcp processes-no ] [ -b max_rcv_buf_size ] [ -m shared_mem_size
] [ -w working-dir ] [ -t chroot-dir ] [ -u uid ] [ -g gid ] [ -P
ser or Sip Express Router is a very fast and configurable SIP proxy.
-h Displays a short usage description, including all available
-c Checks the config file and displays the aliases and listen
-r Uses dns to check if it is necessary to add a "received="
field to a via.
-R Same as -r but uses reverse dns.
-v Turns on via host checking when forwarding replies.
-d Turns on debugging, multiple -d increase the debug level.
-D Runs ser in the foreground (it doesn't fork into daemon
-E Sends all the log messages to stderr.
-T Disables TCP support.
-V Displays the version number.
Reads the configuration from config-file (default
-l address Listens on the specified address/interface. Multiple -l
mean listening on multiple addresses. The address format is
[proto:]address[:port], where proto = udp|tcp and address =
host|ip_address|interface_name. Example: -l localhost, -l
udp:127.0.0.1:5080, -l eth0:5062. The default behaviour is
to listen on all the ipv4 interfaces.
Specifies the number of children processes forked per
interface (default 8).
-N tcp processes-no
Specifies the number of children processes forked to handle
tcp incoming connections (by default is equal to -n ).
Maximum receive buffer size which will not be exceeded by
the auto-probing procedure even if the OS allows.
Size of the shared memory which will be allocated (in
Specifies the working directory. In the very improbable
event that ser will crash, the core file will be generated
Forces ser to chroot after reading the config file.
-u uid Changes the user id under which ser runs.
-g gid Changes the group id under which ser runs.
-P pid-file Creates a file containing the pid of the main ser process.
Full documentation on ser, including configuration guidelines, FAQs and
licensing conditions, is available at http://www.iptel.org/ser/.
For reporting bugs see http://www.iptel.org/ser/bugs/.
firstname.lastname@example.org - ser user community
email@example.com - ser development, new features and unstable version