Hi everybody,
the version 1.0.0 has been released. The branch 'rel_1_0_0' is created and must be used by anybody wanting the get v1.0.0 out from CVS (cvs co -r rel_1_0_0 sip-server).
There are a lot of new features in this release, starting from TLS, pseudo-variables in core and continuing with enhancements in avpops and other module. This release is the first open source sip server with TLS support, although there is still to work on it (e.g., multi domain support) it allow secure sip signaling communications between servers and clients.
An unified format of pseudo-variables has been adopted in core and many modules, basic functionality for future dialog support is present in RR module, avpops includes functions for string operations (concatenation, prefix, suffix, substitute), arithmetic and bitwise operations, among others. A new module, uac_redirect, has been introduced to handle redirect replies (3xx) on server, with proper accounting and filter rules.
See the full list of new features at: http://www.openser.org/release-1.0.0.php A roughly change log can be browsed online at: http://cvs.sourceforge.net/viewcvs.py/openser/sip-server/ChangeLog?view=mark...
There are two categories of released packages: - classic openser, without TLS support - the name of the package does not contain the -tls- word - TLS-ed version of openser - the name of the package contain the -tls- word
The tarball with the sources can be downloaded from: http://openser.org/pub/openser/1.0.0/src/
The basic binary packages are deployed to the download site: http://openser.org/pub/openser/1.0.0/bin/ http://openser.org/pub/openser/1.0.0/packages/
We are still collecting other packages from contributors which already volunteered, so expect new distributions to be represented there in the next days. The module documentations are up-to-date, the site and tutorials need a quick review in the next days.
Congratulation to the excellent work of OpenSER community on this milestone release!
Please excuse me that I didn't follow the changes of TLS part close enough. Originally I thought TLS support could be turn on/off on compile flag level. If so, why do we need two flavors of source tarball?
- Cheng
On Oct 29, 2005, at 6:25 AM, Daniel-Constantin Mierla wrote:
There are two categories of released packages:
- classic openser, without TLS support - the name of the package
does not contain the -tls- word
- TLS-ed version of openser - the name of the package contain the -
tls- word
Hi Cheng,
the difference is in the default configuration (if TLS flags is or or off) and about present sources (if TLS code is included or not).
it's not such a big difference, but I find is more easier to understand/use.
regards, bogdan
Cheng Zhang wrote:
Congratulation to the excellent work of OpenSER community on this milestone release!
Please excuse me that I didn't follow the changes of TLS part close enough. Originally I thought TLS support could be turn on/off on compile flag level. If so, why do we need two flavors of source tarball?
- Cheng
On Oct 29, 2005, at 6:25 AM, Daniel-Constantin Mierla wrote:
There are two categories of released packages:
- classic openser, without TLS support - the name of the package
does not contain the -tls- word
- TLS-ed version of openser - the name of the package contain the -
tls- word
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Cheng,
the difference is in the default configuration (if TLS flags is or or off) and about present sources (if TLS code is included or not).
it's not such a big difference, but I find is more easier to understand/use.
So is there any drawback to using the TLS version if I don't have any particular need for TLS support right now?
Doug
Hi Doug,
the only drawback will be the extra requirements: to compile the TLS-enable sources you need libssl-devel to run TLS-enable binaries you need libssl
Note that by default (even if compiled in) the TLS engine is disabled. Use "tls_disable=no"
regards, bogdan
Doug Meredith wrote:
Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Cheng,
the difference is in the default configuration (if TLS flags is or or off) and about present sources (if TLS code is included or not).
it's not such a big difference, but I find is more easier to understand/use.
So is there any drawback to using the TLS version if I don't have any particular need for TLS support right now?
Doug