preparation for 0.4.0 release

This commit is contained in:
Thomas Ries 2003-10-11 09:32:53 +00:00
parent f33e23775a
commit 49b237db3f
5 changed files with 32 additions and 20 deletions

View File

@ -1,8 +1,9 @@
0.3.7
0.4.0
=====
11-Oct-2003: - released 0.4.0
08-Oct-2003: - rtpproxy_masq: fixed an issue in port allocation
which lead to syslog entries from IPCHAINS complaining
about 'already used connection'
about 'already used connection' in the syslog.
- added INFO() for incomming SIP Calls
04-Oct-2003: - Siproxd now also works as outbound proxy 'only',
means that local UAs may register themselfes to a
@ -11,7 +12,7 @@
- fixed some errors with callid handling (NULL pointers)
24-Sep-2003: - corrected the calling arguments of rtp_masq dummy
routines (non IPCHAINS capable kernels)
22-Sep-2003: - \0 termination of read() SIP telegram from line
22-Sep-2003: - '\0' termination of read() SIP telegram from line
0.3.6
=====

View File

@ -1,6 +1,8 @@
Release Notes for siproxd-0.3.6b
Release Notes for siproxd-0.4.0
================================
- May be used as an pure Outbound proxy (registration of local UAs
to a 3rd party registrar)
- Fli4l OPT_SIP (still experimental) available, check
http://home.arcor.de/jsffm/fli4l/
- supports Linux and FreeBSD (other BSD derivates not yet tested)
@ -9,6 +11,7 @@ Release Notes for siproxd-0.3.6b
- Includes an RTP data stream proxy for *incoming* audio data
(outgoing RTP data should be handled by IP masquerading by the firewall)
- Includes Linux/IPCHAINS support for UDP masquerading tunnels as RTP proxy
(Kernels 2,2,x so far - 2.4.x with IPTABLES is not yet supported)
- Port range to be used for incoming RTP traffic is configurable
(-> easy to set up apropriate firewall rules for incoming traffic)
- RTP proxy can handle multiple RTP streams (eg. audio + video)
@ -44,14 +47,13 @@ Reported to build on:
- OpenBSD 2.9
Reported interoperability (tested with softphones):
- Grandstream BudgeTone-100 series (they only work with IPCHAINS RTP proxy)
- Grandstream BudgeTone-100 series (only works with IPCHAINS RTP proxy)
- Linphone (local and remote UA) (http://www.linphone.org)
- Kphone (local and remote UA) (http://www.wirlab.net/kphone/)
- MSN messenger 4.6 (remote and local UA)
Known bugs:
- does not yet work with Grandstream BudgeTone phones,
but I'm working on this.
There will be...
If you port siproxd to a new platform or do other kinds of changes
or bugfixes that might be of general interest, please drop me a
@ -60,16 +62,9 @@ Known bugs:
-----
md5sum for siproxd-0.3.6b.tar.gz: 5ded692aa606aac714f9c9278b4adee7
md5sum for siproxd-0.4.0.tar.gz:
GnuPG signature for siproxd-0.3.6a.tar.gz archive:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA/cztqCfzBioe83JQRAs8OAJ9DZn4qJceNYkkhuF3EqMiV+w+kKQCcDFPL
h7SwZyAdz+7Qzri/xFcdrjE=
=SEXX
-----END PGP SIGNATURE-----
GnuPG signature for siproxd-0.4.0.tar.gz archive:
GnuPG: pub 1024D/87BCDC94 2000-03-19 Thomas Ries <tries@gmx.net>

View File

@ -29,8 +29,8 @@ dnl
dnl Release Version
dnl
SPD_MAJOR_VERSION=0
SPD_MINOR_VERSION=3
SPD_MICRO_VERSION=7
SPD_MINOR_VERSION=4
SPD_MICRO_VERSION=0
SPD_VERSION=$SPD_MAJOR_VERSION.$SPD_MINOR_VERSION.$SPD_MICRO_VERSION

18
doc/FAQ
View File

@ -11,9 +11,10 @@ A: The goal is that every softphone (that is SIP compliant) should be
- linphone (0.9.0)
- kphone (1.0.2)
- MSN Messenger
- Grandstream BudgeTone series (only with IPCHAINS based RTP proxy)
---------------------------------------------------------------------------
Q: Siproxd's RTP proxying does only work for incoming RTP audio data.
Shouldn't italso proxy outgoing RTP data?
Shouldn't it also proxy outgoing RTP data?
A: This is the correct behaviour. Incoming RTP traffic
is handled by siproxd's RTP proxy. However, outgoing RTP traffic has
@ -147,6 +148,13 @@ A: The RTP proxy actually is quite simple. It does not use any RTP
Outgoing traffic must be handled (masqueraded) by the firewall itself
(using ipchains or iptables rules).
Since version 0.3.6, siproxd also includes an IPCHAINs based RTP proxy/
forwarding. The principle is similar to above, but instead of receiving
and forwarding the UDP packets itself, siproxd just opens up an UDP
masquerading tunnel for the incomming traffic and then the kernel will
do the rest of the work.
---------------------------------------------------------------------------
Q: Does siproxd need to be installed on the same host as the
firewall (ipchains/iptables) is running?
@ -170,6 +178,14 @@ A: Simple. In the config file set the configuration option
Note: The UDP port range for incomming RTP data still uses the same
range as configured in the config file.
---------------------------------------------------------------------------
Q: How do I use siproxd as a pure outbound proxy, so I can register with my
SIP phone at a thired party registrar?
A: Also Simple. Just configure your SIP phone to use siproxd as outbound
proxy and your 3rd party registrar as registrar. Siproxd will then
transparently handle (and if needed rewrite) the SIP traffic.
---------------------------------------------------------------------------
yet unstructured:

View File

@ -183,4 +183,4 @@ struct siproxd_config {
This issue is fixed in linphone-0.9.1pre1
*/
#define MOREDEBUG
//#define MOREDEBUG