Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sipw(8) [debian man page]

sipw(8) 							   GNU Telephony							   sipw(8)

NAME

       sipw - sipwitch service daemon

SYNOPSIS

       sipw [options]

DESCRIPTION

       This  is a service daemon for the SIP protocol.	This daemon enables sip devices and softphone applications to register as well as to route
       messages for the SIP protocol between arbitrary endpoints, both locally and remote over the  Internet  using  DNS  to  resolve  destination
       uri's.	As a telephone system, sipw offers call redirection, speed dials, call forwarding, sms style instant messaging, and the ability to
       ring multiple user agents tied together under a common user id.

       The sipw daemon is also being used as a mediator for desktop telephony.	For this purpose, sip  users  become  the  same  as  normal  login
       accounts  which	happen to be in a specific group of sipusers, and sipw will assume a role for VoIP services similar to what gstreamer does
       for media.

OPTIONS

       Normally the sipw daemon is started from an init script or upstart rather than manually, and  hence  only  those  options  setable  in  the
       /etc/default/sipwitch config file can be set.  However, the sipw daemon can be manually started, both in the foreground for testing, and in
       the background.	If this is done, a number of options may be passed to it directly as documented.

       --background
	      Execute the sipw daemon detached in the background (default).

       --concurrency=level
	      Set the pthread concurrency level for the sipw process.

       --debug=level
	      Specify debug logging level (0-9).  When run in foreground debug messages are shown on the console.  When  in  background  they  are
	      saved in the sipwitch log file.

       --foreground
	      Execute the sipw daemon in the foreground, with output shown on stdout or stderr.

       --gdb  Execute the sipw daemon under control of gdb for full debugging.

       --group=id
	      Specify the group id that the sipw daemon will execute as for receiving control messages or access to daemon managed shared memory.

       --memcheck
	      Execute the sipw daemon under valgrind to validate basic memory management.

       --memleak
	      Execute the sipw daemon under valgrind for full memory leak detection.

       --no-localusers
	      Disable use of local (system) user accounts entirely.

       --plugins=names
	      Load only these specified plugins from /var/lib/sipwitch.

       --priority=level
	      Execute the sipw daemon under the realtime (fifo) schedule, and specify a realtime process priority level (1-9).

       --restarable
	      The  sipw  daemon will automatically restart if it exits or crashes other than from a manually specified reason.	This is often used
	      on BSD systems when sipw is started from an rc file.

       --trace
	      Logs sip messages the sipw daemon sends and receives.

       --version
	      Print the currently installed version of sipwitch to standard output.

AUTHOR

       sipw was written by David Sugar <dyfet@gnutelephony.org>.

REPORTING BUGS

       Report bugs to sipwitch-devel@gnu.org.

COPYRIGHT

       Copyright (C) 2009 David Sugar, Tycho Softworks.
       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

GNU SIP Witch							   December 2009							   sipw(8)

Check Out this Related Man Page

HALD(8) 						      System Manager's Manual							   HALD(8)

NAME

       hald - HAL daemon

SYNOPSIS

       hald [options]

DESCRIPTION

       hald  is  a  daemon  that maintains a database of the devices connected to the system system in real-time. The daemon connects to the D-Bus
       system message bus to provide an API that applications can use to discover, monitor and invoke operations on devices. For more  information
       about  both  the  big  picture  and  specific  API  details, refer to the HAL spec which can be found in /usr/local/share/doc/hal/spec/hal-
       spec.html depending on the distribution.

OPTIONS

       The following options are supported:

       --daemon=yes|no
	      Specify whether to run in the foreground or the background.

       --verbose=yes|no
	      Enable verbose debug output.

       --use-syslog
	      Enable logging of debug output to the syslog instead of stderr. Use this option only together with --verbose.

       --help Print out usage.

       --version
	      Print the version of the daemon and exit.

BUGS AND DEBUGGING

       Please send bug reports to either the distribution or the HAL mailing list, see http://lists.freedesktop.org/mailman/listinfo/hal on how to
       subscribe.

       First,  to  obtain  useful debug traces you will need to have debuginfo packages installed. On a Fedora system this is in the hal-debuginfo
       package and can be installed via the yum update program.

       Second, shut down the existing hald daemon instance; on a Fedora system this is achieved by

       /usr/local/etc/init.d/haldaemon stop

       After having shut down the daemon, you might want to run

       pkill hald

       to ensure that all the helper processe of hald are killed too. To start the HAL daemon, use

       /usr/local/sbin/hald --daemon=no --verbose=yes

       If the daemon crashes, you can start it under a debugger via

       gdb /usr/local/sbin/hald

       and then typing

       run --daemon=no --verbose=yes

       at the (gdb) prompt. To capture a back trace, use the bt command and attach this to the bug report.

       Please also attach the output of lshal(1) in the bug report if possible (it's not possible if the hald daemon crashed). If  the	nature	of
       the bug has to do with hotplugging, attach two outputs of lshal(1) - one before the device hotplug event and one after.

SEE ALSO

       udev(7),  dbus-daemon(1),  lshal(1),  hal-set-property(1), hal-get-property(1), hal-find-by-property(1), hal-find-by-capability(1), hal-is-
       caller-locked-out(1)

AUTHOR

       Written by David Zeuthen <david@fubar.dk> with a lot of help from many others.

																	   HALD(8)
Man Page