sipproxy64
9 years agoImprovement to init-script (assign /128 instead of /64 addresses) master
Rick van Rein [Fri, 22 Jul 2011 11:50:26 +0000 (11:50 +0000)]
Improvement to init-script (assign /128 instead of /64 addresses)

10 years agoCanonical Refer-To:
Rick van Rein [Tue, 11 Jan 2011 15:38:30 +0000 (15:38 +0000)]
Canonical Refer-To:

10 years agoHandling REFER messages properly
Rick van Rein [Tue, 11 Jan 2011 14:50:00 +0000 (14:50 +0000)]
Handling REFER messages properly

10 years agoCorrection for IPv4 calls behind one SIPproxy64, connected through an IPv6 proxy
Rick van Rein [Thu, 30 Dec 2010 21:40:23 +0000 (21:40 +0000)]
Correction for IPv4 calls behind one SIPproxy64, connected through an IPv6 proxy

10 years agoMinor updates in printf()
root [Mon, 27 Dec 2010 07:51:11 +0000 (08:51 +0100)]
Minor updates in printf()

10 years agoExtended manual page to reflect SIGHUP as a gentle "please go away"
Rick van Rein [Tue, 21 Dec 2010 21:16:11 +0000 (21:16 +0000)]
Extended manual page to reflect SIGHUP as a gentle "please go away"

10 years agoStartup as a daemon, stop SIP processing upon SIGHUP, but still logging to stdout...
Rick van Rein [Tue, 21 Dec 2010 20:52:17 +0000 (20:52 +0000)]
Startup as a daemon, stop SIP processing upon SIGHUP, but still logging to stdout/stderr.

10 years agoExample IPs moved to 19.0.2.x (RFC 5735) and 2001:db8::/32 (RFC 3849)
root [Fri, 17 Dec 2010 09:00:33 +0000 (10:00 +0100)]
Example IPs moved to 19.0.2.x (RFC 5735) and 2001:db8::/32 (RFC 3849)

10 years agoFixed SIP PING. Heritage of an silly past...
Rick van Rein [Sun, 5 Dec 2010 17:31:36 +0000 (17:31 +0000)]
Fixed SIP PING.  Heritage of an silly past...

10 years agoIgnoring GrandStream boot: REGISTER without proper Contact (why?!?)
Rick van Rein [Sun, 5 Dec 2010 17:21:08 +0000 (17:21 +0000)]
Ignoring GrandStream boot: REGISTER without proper Contact (why?!?)

10 years agoVersion 0.2 -- Solving problems with Record-Route and
Rick van Rein [Sun, 5 Dec 2010 13:25:20 +0000 (13:25 +0000)]
Version 0.2 -- Solving problems with Record-Route and
crashes due to NOTIFY without From-tag.

10 years agoCalls pass through OK, setup/breakdown/media. Registration does not always work...
Rick van Rein [Fri, 3 Dec 2010 20:52:39 +0000 (20:52 +0000)]
Calls pass through OK, setup/breakdown/media.  Registration does not always work though?!?

10 years agoReworked most of the code, got it working from unknown phones to specified ones.
Rick van Rein [Fri, 3 Dec 2010 07:59:44 +0000 (07:59 +0000)]
Reworked most of the code, got it working from unknown phones to specified ones.
Registration does not work yet, no cleanup of handle_sip() yet.

10 years agoRemoved Debian example files
Rick van Rein [Tue, 30 Nov 2010 20:09:08 +0000 (21:09 +0100)]
Removed Debian example files

10 years agoIntroducing (very simple) configure file
Rick van Rein [Tue, 30 Nov 2010 18:41:30 +0000 (18:41 +0000)]
Introducing (very simple) configure file

10 years agoWorking version, with Via: and Record-Route: headers
Rick van Rein [Tue, 30 Nov 2010 18:39:39 +0000 (18:39 +0000)]
Working version, with Via: and Record-Route: headers

10 years agoRemoved dependency on RTPproxy from rtpproxy.org. The reasons for this are: drop-rtpproxy
Rick van Rein [Thu, 25 Nov 2010 08:55:23 +0000 (08:55 +0000)]
Removed dependency on RTPproxy from rtpproxy.org.  The reasons for this are:
 * RTPproxy is more complex than needed for simple 6/4 translation
 * RTPproxy is hardly documentated, making it an unreliable basis for SIPproxy64
 * RTPproxy is intended for very large setups; our scaling to 12500 conversations is enough?

There is a lot of work left to be done, most notably cleanup of the code now that it
works and closing sockets.  But that can be done as part of a major restructuring
operation in the master branch.

10 years agoInitial version. Effectively proxies SIP, but does not interface with
Rick van Rein [Wed, 24 Nov 2010 16:42:33 +0000 (16:42 +0000)]
Initial version.  Effectively proxies SIP, but does not interface with
RTPproxy well enough, largely because that software lacks *any* form of
documentation on how to address it from your own software.