The Siproxd Project - a VoIP SIP Proxy

Time 2021-11-23 11:24:44

Web Name: The Siproxd Project - a VoIP SIP Proxy

WebSite: http://siproxd.sourceforge.net

ID:245951

Keywords:

Project,Siproxd,The,Proxy,SIP,VoIP,

Description:

keywords:
description:Siproxd is a VoIP SIP Proxy that eliminates many of the problems that NAT introduces to VoIP. It provides various features as well as a plugin framework that allows custom extensions.
Site Navigation: OverviewNewsRelease NotesFAQOnline DocuChangeLogGitHub RepoDownload ReleaseDownload SnapshotSF Project PageMailing ListForumsBug TrackerContributionsCommercial SupportContact Current Release: 0.8.3

Siproxd - a masquerading SIP Proxy Server

OVERVIEWSiproxd is a proxy/masquerading daemon for the SIP protocol.It handles registrations of SIP clients on a private IP networkand performs rewriting of the SIP message bodies to make SIPconnections work via an masquerading firewall (NAT).It allows SIP software clients (like kphone, linphone) or SIPhardware clients (Voice over IP phones which are SIP-compatible,such as those from Cisco, Grandstream or Snom) to work behindan IP masquerading firewall or NAT router.

SIP (Session Initiation Protocol, RFC3261) is the protocol ofchoice for most VoIP (Voice over IP) phones to initiatecommunication. By itself, SIP does not work via masqueradingfirewalls as the transfered data contains IP addresses andport numbers. There do exist other solutions to traverse NAT existing(like STUN, or SIP aware NAT routers), but such a solutions has itsdisadvantages or may not be applicable to a given situation.Siproxd does not aim to be a replacement for these solutions,however in some situations siproxd may bring advantages.
PREREQUISITESSiproxd runs on a variety of Unix derivates. Currently known to work are:LinuxFreeBSDOpenBSDSunOSMac OS XpfSenseSiproxd requires the libosip2 package available at www.gnu.org.
HOW TO GET STARTEDEither download a ready made package for your favorite distribution (there arequite some around) or do it from scratch:make sure libosip2 is installed
If your libposip2 libraries are installed in /usr/local/lib, be sure to include this library path to /etc/ld.so.conf$ ./configure$ make$ make installedit /usr/etc/siproxd.conf according to your situation.
At least configure 'if_inbound' and 'if_outbound'. They must represent the interface names (e.g. on Linux: ppp0, eth1) for the inbound and outbound interface.edit /usr/etc/siproxd_passwd.cfg if you enable client authentication in siproxd.confstart siproxd (siproxd does not require root privileges)
$ siproxdAnd of course: Please read the documentation and the FAQ!
SENDING A PATCHIf you send a patch, please make the diff using "diff -Naur" andinclude the version of siproxd you used to patch. This makes it a loteasier for me to merge it.
PROBLEM REPORTINGIf you encounter problems/crashes and ask for support, please includeas much information as possible. Very helpful is a debug log thathas been recorded at the time of the misbehavior. Also include the exactversions of the siproxd package and libosip2 that you are using.You should also include your siproxd.conf.

The easiest way to generate a debug log is:make sure siproxd is not started as daemon.
-> 'daemonize = 0' in the config file.start siproxd:
$ ./siproxd -d -1 2debug.logreproduce the errorinclude the file debug.log in your error report.Since Version 0.5.10 there also exists the possibility to obtainthe debug log remote via TCP (useful if running siproxd on an embeddedsystem). To enable this feature, edit the configuration file andset 'debug_port' to a free TCP port number (e.g. 5050). Then (afterstarting siproxd) you can connect from any remote client to thisTCP port (e.g. using netcat) and all the debug output will be sentvia network:edit configuration file:
-> 'daemonize = 1' have siproxd started as daemon
-> 'silence_log' should be set to 1
-> 'debug_level = -1'
-> 'debug_port = 5050' (or any other TCP port you like)have siproxd started the usual wayconnect from a remote machine and write into a file:
$ netcat IP_of_siproxd port debug.logreproduce the errorinclude the file debug.log in your error report.If siproxd crashes, a stack backtrace usually is helpful to me:start siproxd in the debugger (daemonize set to 0):
$ gdb ./src/siproxd
(gdb) set args -c /path/to/siproxd.conf
(gdb) runreproduce the crashuse gdb to print the stack backtrace:
(gdb) info thread
...
(gdb) bt
#0 0x400ec9ee in __select ()
#1 0xbffff6f8 in ?? ()
#2 0x804a5c2 in main (argc=3, argv=0xbffffc54) at siproxd.c:186
#3 0x4005bcb3 in __libc_start_main (main=0x804a30c main, argc=3,
argv=0xbffffc54, init=0x8049a08 <_init>, fini=0x804edac <_fini>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffc4c)
at ../sysdeps/generic/libc-start.c:78
(gdb)copy-paste all the output and include it in your error report.
LOOKING FOR COMMERCIAL SUPPORT?Please click here Copyright 2007-2019 - Thomas Ries. All rights reserved.
This page was last modified at: Saturday, 12-May-2018 07:29:28 UTC

TAGS:Project Siproxd The Proxy SIP VoIP 

<<< Thank you for your visit >>>

Siproxd is a VoIP SIP Proxy that eliminates many of the problems that NAT introduces to VoIP. It provides various features as well as a plugin framework that allows custom extensions.

Hot Websites