Ladies and gentlemen, girls and boys,
the new testing pre-release of the best SIP proxy server ever, SER, is out!
This major pre-release, codenamed Ottendorf, includes fundamental improvements to the software. The improvements allow SER users to achieve significantly higher managability and reliability by better data mode, interop features, security, etc. They recollect voluminous feedback we have received from iptel customers and open source users. In particular, the new features include but are not limited to: - improved data model which eliminates any possible ambiguities. - key under-the-hood changes with impact on performance: timer subsystem overhaul (now fast, with fine resolution, high accuracy and variability), TCP processing overhaul (higher scalability) - key reliability changes: DNS cache and IP blacklisting - key interop changes: support for STUN-bis, presence server aligned to latest IETF development, sanity module for early detection of invalid messages - more management: management features are now available via XML-RPC remotely, as well as via an alternative binary protocol - more security: ratelimit module, more check types in permissions module - scripting features: select operator in combination with revised AVPs, named flags and routes, more types of routes (onsend, timer, branch) - applications: presence has been greatly updated to keep pace with development in the IETF/SIMPLE (includes asynchronous subscription authorization, extended PIDF); web interface includes many new managibility features (multidomain, templates and multilanguage to name some). New scripting flexibility allows safely for features like individual ringing timers and direct access to SIP message elements. - new tools: Nils's script execution tree tool http://lists.iptel.org/pipermail/serdev/2006-October/008124.html and refurbished ser_ctl see the following links for some additional details: - http://www.iptel.org/ser/doc/010whatsnew - http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD
Accompanying software, SEMS and SERWEB have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVR-scripting and B2BUA, adaptive playout buffer for better voice quality, and more. SERWEB features new multilevel administrative access system, multidomain support, per-domain customization, remote xml-rpc access, multilanguage support, and more. The new command-line utility, SER_CTL, provides also many great improvements over the previous tool.
Interop ------- Shortly, we have been keeping the bar high through our participation in the IETF and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, presence + XCAP, to name the most important ones) and both new features and legacy features were extensively and successfully tested middle of October in SIPit.
Next Steps ----------- Keep in mind, this is a pre-release for testing purposes. It is now call on users to test the software hard and provide feedback. In the meantime, the codebase remains frozen and we only commit patches fixing various bugs. Once we get good confidence that Ottendorf has stabilized and is being adequately documented, we will declare the final release. No date has been determined yet. Also, we consider changing CVS to SVN.
Again, and this is very important: the final release will be as good as the feedback we obtain for this pre-release. Please do spend your time sending solid feedback back to [serusers].
Roadmap ------- We keep rolling. We are still debating with our generous contributors what is the next possible good things to work on, the topics include but are not limited to as of now: - documentation. - databases are important. LDAP and BDB, DB-API revision. - interop: identity, TLS revision - advanced scripting (scripting engine, vars returns, AVPs) - uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, .....)
Trivia -------- The release name Ottendorf is coming from a place in Saxonian Switzerland, where many iptel fellows and their friends spent a weekend during this Indian summer. http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ http://www.iptel.org/~andi/2006-09-22-Ottendorf/ http://www.iptel.org/~vlada/saxon_switzerland/index.html http://www.ohlmeier.de/albums/ottendorf_2006/index.html
Acknowledgments --------------- This grand achievement is result of extremely many folks who did lot of hard work. Out of folks affiliated with iptel, Andrei and Jan spent immense effort on moving SER forward, with great support from Hallik (command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada (new STUN). In this context, I would like to thank to our company for the great support. Recently, Bogdan Pintea greatly helped to make the upcoming release better and more stable under sponsorship of his company, iptego. transnexus provided osp support.
SEMS has been greatly improved thanks to Stefan and Raphael. Credits for serweb go to Karel.
Same importantly, SER has been immensely benefitting of contributors, to name in alphabetic order at least the 'top-of-the-iceberg' fellows: Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, http://tutpro.com/Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter Nixon, Uli Abend.
Great support on the mailing list has been provided by Greger V. Teigre, Java Rockx, Klaus Darilion, Zeus Ng, and more.
Simply, this list is too short and incomplete to capture all the generous contributions that came in -- my appologies for everyone else I have missed.
Warnings and Disclaimers ------------------------ This is a TESTING version. We are encouraging people to give it intense testing and provide us with feedback, so that we can properly assess what it takes to declare it final. The volume and number of changes is big, caution is advised.
All GPL warnings and disclaimers apply.
This is SER, which is not the derivate software known as openser. We have no ideas of in what extent and timeline derivate projects follow (or not) SER.
-------------------------------------------------------------------------------
To Give it a Try ----------------- warning: this is just a 'jump-start' for black-belt users. It is not a replacement for documentation or a detailed step-by-step installation guide. It assumes knowledge of operating system, SIP, and SER.
PREPARATION - make sure mysql is running. In the default configuration, SER assumes it to be running on localhost, if this does not hold, you need to change ser.cfg. - make sure python is installed (needed for new command-line utilities) SER INSTALLATION FROM CVS - Download from CVS/HEAD using instructions at http://www.iptel.org/downloads - Compile it: make include_modules="mysql xmlrpc" all - Install it the default way of your administrative privileges allow to: make include_modules="mysql xmlrpc" install - Download command-line tool (see more documentation under http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=H...) - cvs co serctl - Initiate database: ./scripts/mysql/ser_mysql.sh create START - Start it. Call: ser - Begin provisioning users with the new serctl (the capital word are just place holders) # ser_ctl domain add DOMAINNAME # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD # If you want to have Asserted Identity header for your user # - ser_attr add uid=UID asserted_id="PID" # If you want to have gateway support # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ description="The gateway IP for the default ser.cfg" default_flags=33 # - ser_attr add global gw_ip=GATEWAY-IP - more things you may wish to do: - familiarize yourself with current ser.cfg - send us feedback.
-- Jiri Kuthan http://iptel.org/~jiri/
Thank you guys!
On 11/6/06, Jiri Kuthan jiri@iptel.org wrote:
Ladies and gentlemen, girls and boys,
the new testing pre-release of the best SIP proxy server ever, SER, is out!
This major pre-release, codenamed Ottendorf, includes fundamental improvements to the software. The improvements allow SER users to achieve significantly higher managability and reliability by better data mode, interop features, security, etc. They recollect voluminous feedback we have received from iptel customers and open source users. In particular, the new features include but are not limited to:
- improved data model which eliminates any possible ambiguities.
- key under-the-hood changes with impact on performance: timer subsystem
overhaul (now fast, with fine resolution, high accuracy and variability), TCP processing overhaul (higher scalability)
- key reliability changes: DNS cache and IP blacklisting
- key interop changes: support for STUN-bis, presence server aligned to latest
IETF development, sanity module for early detection of invalid messages
- more management: management features are now available via XML-RPC remotely,
as well as via an alternative binary protocol
- more security: ratelimit module, more check types in permissions module
- scripting features: select operator in combination with revised AVPs,
named flags and routes, more types of routes (onsend, timer, branch)
- applications: presence has been greatly updated to keep pace with
development in the IETF/SIMPLE (includes asynchronous subscription authorization, extended PIDF); web interface includes many new managibility features (multidomain, templates and multilanguage to name some). New scripting flexibility allows safely for features like individual ringing timers and direct access to SIP message elements.
- new tools: Nils's script execution tree tool
http://lists.iptel.org/pipermail/serdev/2006-October/008124.html and refurbished ser_ctl see the following links for some additional details:
- http://www.iptel.org/ser/doc/010whatsnew
- http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD
Accompanying software, SEMS and SERWEB have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVR-scripting and B2BUA, adaptive playout buffer for better voice quality, and more. SERWEB features new multilevel administrative access system, multidomain support, per-domain customization, remote xml-rpc access, multilanguage support, and more. The new command-line utility, SER_CTL, provides also many great improvements over the previous tool.
Interop
Shortly, we have been keeping the bar high through our participation in the IETF and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, presence
- XCAP, to name the most important ones) and both new features and legacy features
were extensively and successfully tested middle of October in SIPit.
Next Steps
Keep in mind, this is a pre-release for testing purposes. It is now call on users to test the software hard and provide feedback. In the meantime, the codebase remains frozen and we only commit patches fixing various bugs. Once we get good confidence that Ottendorf has stabilized and is being adequately documented, we will declare the final release. No date has been determined yet. Also, we consider changing CVS to SVN.
Again, and this is very important: the final release will be as good as the feedback we obtain for this pre-release. Please do spend your time sending solid feedback back to [serusers].
Roadmap
We keep rolling. We are still debating with our generous contributors what is the next possible good things to work on, the topics include but are not limited to as of now:
- documentation.
- databases are important. LDAP and BDB, DB-API revision.
- interop: identity, TLS revision
- advanced scripting (scripting engine, vars returns, AVPs)
- uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, .....)
Trivia
The release name Ottendorf is coming from a place in Saxonian Switzerland, where many iptel fellows and their friends spent a weekend during this Indian summer. http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ http://www.iptel.org/~andi/2006-09-22-Ottendorf/ http://www.iptel.org/~vlada/saxon_switzerland/index.html http://www.ohlmeier.de/albums/ottendorf_2006/index.html
Acknowledgments
This grand achievement is result of extremely many folks who did lot of hard work. Out of folks affiliated with iptel, Andrei and Jan spent immense effort on moving SER forward, with great support from Hallik (command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada (new STUN). In this context, I would like to thank to our company for the great support. Recently, Bogdan Pintea greatly helped to make the upcoming release better and more stable under sponsorship of his company, iptego. transnexus provided osp support.
SEMS has been greatly improved thanks to Stefan and Raphael. Credits for serweb go to Karel.
Same importantly, SER has been immensely benefitting of contributors, to name in alphabetic order at least the 'top-of-the-iceberg' fellows: Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, http://tutpro.com/Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter Nixon, Uli Abend.
Great support on the mailing list has been provided by Greger V. Teigre, Java Rockx, Klaus Darilion, Zeus Ng, and more.
Simply, this list is too short and incomplete to capture all the generous contributions that came in -- my appologies for everyone else I have missed.
Warnings and Disclaimers
This is a TESTING version. We are encouraging people to give it intense testing and provide us with feedback, so that we can properly assess what it takes to declare it final. The volume and number of changes is big, caution is advised.
All GPL warnings and disclaimers apply.
This is SER, which is not the derivate software known as openser. We have no ideas of in what extent and timeline derivate projects follow (or not) SER.
To Give it a Try
warning: this is just a 'jump-start' for black-belt users. It is not a replacement for documentation or a detailed step-by-step installation guide. It assumes knowledge of operating system, SIP, and SER.
PREPARATION
- make sure mysql is running. In the default configuration, SER assumes it
to be running on localhost, if this does not hold, you need to change ser.cfg.
- make sure python is installed (needed for new command-line utilities)
SER INSTALLATION FROM CVS
- Download from CVS/HEAD using instructions at http://www.iptel.org/downloads
- Compile it: make include_modules="mysql xmlrpc" all
- Install it the default way of your administrative privileges allow to:
make include_modules="mysql xmlrpc" install
- Download command-line tool (see more documentation under
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=H...)
- cvs co serctl
- Initiate database:
./scripts/mysql/ser_mysql.sh create START
- Start it. Call: ser
- Begin provisioning users with the new serctl (the capital word are just place holders)
# ser_ctl domain add DOMAINNAME # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD # If you want to have Asserted Identity header for your user # - ser_attr add uid=UID asserted_id="PID" # If you want to have gateway support # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ description="The gateway IP for the default ser.cfg" default_flags=33 # - ser_attr add global gw_ip=GATEWAY-IP
- more things you may wish to do:
- familiarize yourself with current ser.cfg
- send us feedback.
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
On Monday 06 November 2006 04:02, Jiri Kuthan wrote: <snip>
PREPARATION
- make sure mysql is running.
<snip>
- Compile it: make include_modules="mysql xmlrpc" all
<snip>
make include_modules="mysql xmlrpc" install
Is a mysql rdbms simply suggested, or is it required? I thought postgresql was now fully supported with the latest ser.
At 18:09 06/11/2006, Corey wrote:
On Monday 06 November 2006 04:02, Jiri Kuthan wrote:
<snip> > PREPARATION > - make sure mysql is running. <snip> > - Compile it: make include_modules="mysql xmlrpc" all <snip> > make include_modules="mysql xmlrpc" install >
Is a mysql rdbms simply suggested, or is it required? I thought postgresql was now fully supported with the latest ser.
thanks for clarification. mysql is a default most-tested suggestion but actually refurbished postgress belongs to nice features of this release and is supported as well. I would appreciate feedback on this if you have some.
Thanks!
-jiri
-- Jiri Kuthan http://iptel.org/~jiri/
On Monday 06 November 2006 10:22, Jiri Kuthan wrote:
At 18:09 06/11/2006, Corey wrote:
On Monday 06 November 2006 04:02, Jiri Kuthan wrote:
PREPARATION
- make sure mysql is running.
<snip>
Is a mysql rdbms simply suggested, or is it required? I thought postgresql was now fully supported with the latest ser.
thanks for clarification. mysql is a default most-tested suggestion but actually refurbished postgress belongs to nice features of this release and is supported as well.
Excellent!
I would appreciate feedback on this if you have some.
We definitely will; looking forward to testing SER's latest, and we just happen to be using postgresql.
Cheers,
Corey
Hi, just note for SerWeb users. Please use cvs branch 'rel_0_10_0' for testing. Not the cvs head. Use this command for cvs checkout:
cvs -d:pserver:anonymous@cvs.berlios.de:/cvsroot/serweb co -P -r rel_0_10_0 serweb
and follow instructions in INSTALL file. If you found a bug, please report it at http://bugs.sip-router.org.
thanks, Karel
Jiri Kuthan napsal(a):
Ladies and gentlemen, girls and boys,
the new testing pre-release of the best SIP proxy server ever, SER, is out!
This major pre-release, codenamed Ottendorf, includes fundamental improvements to the software. The improvements allow SER users to achieve significantly higher managability and reliability by better data mode, interop features, security, etc. They recollect voluminous feedback we have received from iptel customers and open source users. In particular, the new features include but are not limited to:
- improved data model which eliminates any possible ambiguities.
- key under-the-hood changes with impact on performance: timer subsystem overhaul (now fast, with fine resolution, high accuracy and variability), TCP processing overhaul (higher scalability)
- key reliability changes: DNS cache and IP blacklisting
- key interop changes: support for STUN-bis, presence server aligned to latest IETF development, sanity module for early detection of invalid messages
- more management: management features are now available via XML-RPC remotely, as well as via an alternative binary protocol
- more security: ratelimit module, more check types in permissions module
- scripting features: select operator in combination with revised AVPs, named flags and routes, more types of routes (onsend, timer, branch)
- applications: presence has been greatly updated to keep pace with development in the IETF/SIMPLE (includes asynchronous subscription authorization, extended PIDF); web interface includes many new managibility features (multidomain, templates and multilanguage to name some). New scripting flexibility allows safely for features like individual ringing timers and direct access to SIP message elements.
- new tools: Nils's script execution tree tool http://lists.iptel.org/pipermail/serdev/2006-October/008124.html and refurbished ser_ctl
see the following links for some additional details:
- http://www.iptel.org/ser/doc/010whatsnew
- http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD
Accompanying software, SEMS and SERWEB have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVR-scripting and B2BUA, adaptive playout buffer for better voice quality, and more. SERWEB features new multilevel administrative access system, multidomain support, per-domain customization, remote xml-rpc access, multilanguage support, and more. The new command-line utility, SER_CTL, provides also many great improvements over the previous tool.
Interop
Shortly, we have been keeping the bar high through our participation in the IETF and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, presence
- XCAP, to name the most important ones) and both new features and legacy features
were extensively and successfully tested middle of October in SIPit.
Next Steps
Keep in mind, this is a pre-release for testing purposes. It is now call on users to test the software hard and provide feedback. In the meantime, the codebase remains frozen and we only commit patches fixing various bugs. Once we get good confidence that Ottendorf has stabilized and is being adequately documented, we will declare the final release. No date has been determined yet. Also, we consider changing CVS to SVN.
Again, and this is very important: the final release will be as good as the feedback we obtain for this pre-release. Please do spend your time sending solid feedback back to [serusers].
Roadmap
We keep rolling. We are still debating with our generous contributors what is the next possible good things to work on, the topics include but are not limited to as of now:
- documentation.
- databases are important. LDAP and BDB, DB-API revision.
- interop: identity, TLS revision
- advanced scripting (scripting engine, vars returns, AVPs)
- uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, .....)
Trivia
The release name Ottendorf is coming from a place in Saxonian Switzerland, where many iptel fellows and their friends spent a weekend during this Indian summer. http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ http://www.iptel.org/~andi/2006-09-22-Ottendorf/ http://www.iptel.org/~vlada/saxon_switzerland/index.html http://www.ohlmeier.de/albums/ottendorf_2006/index.html
Acknowledgments
This grand achievement is result of extremely many folks who did lot of hard work. Out of folks affiliated with iptel, Andrei and Jan spent immense effort on moving SER forward, with great support from Hallik (command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada (new STUN). In this context, I would like to thank to our company for the great support. Recently, Bogdan Pintea greatly helped to make the upcoming release better and more stable under sponsorship of his company, iptego. transnexus provided osp support.
SEMS has been greatly improved thanks to Stefan and Raphael. Credits for serweb go to Karel.
Same importantly, SER has been immensely benefitting of contributors, to name in alphabetic order at least the 'top-of-the-iceberg' fellows: Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, http://tutpro.com/Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter Nixon, Uli Abend.
Great support on the mailing list has been provided by Greger V. Teigre, Java Rockx, Klaus Darilion, Zeus Ng, and more.
Simply, this list is too short and incomplete to capture all the generous contributions that came in -- my appologies for everyone else I have missed.
Warnings and Disclaimers
This is a TESTING version. We are encouraging people to give it intense testing and provide us with feedback, so that we can properly assess what it takes to declare it final. The volume and number of changes is big, caution is advised.
All GPL warnings and disclaimers apply.
This is SER, which is not the derivate software known as openser. We have no ideas of in what extent and timeline derivate projects follow (or not) SER.
To Give it a Try
warning: this is just a 'jump-start' for black-belt users. It is not a replacement for documentation or a detailed step-by-step installation guide. It assumes knowledge of operating system, SIP, and SER.
PREPARATION
- make sure mysql is running. In the default configuration, SER assumes it to be running on localhost, if this does not hold, you need to change ser.cfg.
- make sure python is installed (needed for new command-line utilities)
SER INSTALLATION FROM CVS
- Download from CVS/HEAD using instructions at http://www.iptel.org/downloads
- Compile it: make include_modules="mysql xmlrpc" all
- Install it the default way of your administrative privileges allow to: make include_modules="mysql xmlrpc" install
- Download command-line tool (see more documentation under http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=H...)
- cvs co serctl
- Initiate database: ./scripts/mysql/ser_mysql.sh create
START
- Start it. Call: ser
- Begin provisioning users with the new serctl (the capital word are just place holders) # ser_ctl domain add DOMAINNAME # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD # If you want to have Asserted Identity header for your user # - ser_attr add uid=UID asserted_id="PID" # If you want to have gateway support # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ description="The gateway IP for the default ser.cfg" default_flags=33 # - ser_attr add global gw_ip=GATEWAY-IP
- more things you may wish to do:
- familiarize yourself with current ser.cfg
- send us feedback.
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Just a bit more info on this pre-release adding to Jiri's long post (if you can take it ;-):
* The mentioned http://www.iptel.org/ser/doc/010whatsnew will be updated as we go with new documentation. Any registered user on iptel.org can add to or modify documentation and all help is welcome. If you are uncertain about how to proceed, send me an email
* As Jiri mentioned, any input and help is appreciated. If you want to contribute, but don't know what to do, have a look at the to-dos page: http://www.iptel.org/todos
* This pre-release is, without basic documentation, a bit for the die-hard. This is an overview of what we are working (and need help) on to make it easier accessible: - A tar source package ready for simple update from CVS (similar to the ONsip.org source package) - Better "kickstart" instructions, including more details in What's new 0.10 (above link) - Updated SER - Getting Started configuration files and updated SER - Getting Started document - Database migration script (contact me if you want to try out an existing python migration script and test/improve)
* Also, in addition to the ser.cfg and Nils recently commited ser-basic.cfg in CVS, take a look at an example config file: http://www.iptel.org/basic_changes_in_configuration_file_0
*An optimized NAT-handled config file can be found here: http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy
Happy testing! g-)
Jiri Kuthan wrote:
Ladies and gentlemen, girls and boys,
the new testing pre-release of the best SIP proxy server ever, SER, is out!
This major pre-release, codenamed Ottendorf, includes fundamental improvements to the software. The improvements allow SER users to achieve significantly higher managability and reliability by better data mode, interop features, security, etc. They recollect voluminous feedback we have received from iptel customers and open source users. In particular, the new features include but are not limited to:
- improved data model which eliminates any possible ambiguities.
- key under-the-hood changes with impact on performance: timer subsystem overhaul (now fast, with fine resolution, high accuracy and variability), TCP processing overhaul (higher scalability)
- key reliability changes: DNS cache and IP blacklisting
- key interop changes: support for STUN-bis, presence server aligned to latest IETF development, sanity module for early detection of invalid messages
- more management: management features are now available via XML-RPC remotely, as well as via an alternative binary protocol
- more security: ratelimit module, more check types in permissions module
- scripting features: select operator in combination with revised AVPs, named flags and routes, more types of routes (onsend, timer, branch)
- applications: presence has been greatly updated to keep pace with development in the IETF/SIMPLE (includes asynchronous subscription authorization, extended PIDF); web interface includes many new managibility features (multidomain, templates and multilanguage to name some). New scripting flexibility allows safely for features like individual ringing timers and direct access to SIP message elements.
- new tools: Nils's script execution tree tool http://lists.iptel.org/pipermail/serdev/2006-October/008124.html and refurbished ser_ctl
see the following links for some additional details:
- http://www.iptel.org/ser/doc/010whatsnew
- http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD
Accompanying software, SEMS and SERWEB have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVR-scripting and B2BUA, adaptive playout buffer for better voice quality, and more. SERWEB features new multilevel administrative access system, multidomain support, per-domain customization, remote xml-rpc access, multilanguage support, and more. The new command-line utility, SER_CTL, provides also many great improvements over the previous tool.
Interop
Shortly, we have been keeping the bar high through our participation in the IETF and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, presence
- XCAP, to name the most important ones) and both new features and legacy features
were extensively and successfully tested middle of October in SIPit.
Next Steps
Keep in mind, this is a pre-release for testing purposes. It is now call on users to test the software hard and provide feedback. In the meantime, the codebase remains frozen and we only commit patches fixing various bugs. Once we get good confidence that Ottendorf has stabilized and is being adequately documented, we will declare the final release. No date has been determined yet. Also, we consider changing CVS to SVN.
Again, and this is very important: the final release will be as good as the feedback we obtain for this pre-release. Please do spend your time sending solid feedback back to [serusers].
Roadmap
We keep rolling. We are still debating with our generous contributors what is the next possible good things to work on, the topics include but are not limited to as of now:
- documentation.
- databases are important. LDAP and BDB, DB-API revision.
- interop: identity, TLS revision
- advanced scripting (scripting engine, vars returns, AVPs)
- uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, .....)
Trivia
The release name Ottendorf is coming from a place in Saxonian Switzerland, where many iptel fellows and their friends spent a weekend during this Indian summer. http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ http://www.iptel.org/~andi/2006-09-22-Ottendorf/ http://www.iptel.org/~vlada/saxon_switzerland/index.html http://www.ohlmeier.de/albums/ottendorf_2006/index.html
Acknowledgments
This grand achievement is result of extremely many folks who did lot of hard work. Out of folks affiliated with iptel, Andrei and Jan spent immense effort on moving SER forward, with great support from Hallik (command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada (new STUN). In this context, I would like to thank to our company for the great support. Recently, Bogdan Pintea greatly helped to make the upcoming release better and more stable under sponsorship of his company, iptego. transnexus provided osp support.
SEMS has been greatly improved thanks to Stefan and Raphael. Credits for serweb go to Karel.
Same importantly, SER has been immensely benefitting of contributors, to name in alphabetic order at least the 'top-of-the-iceberg' fellows: Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, http://tutpro.com/Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter Nixon, Uli Abend.
Great support on the mailing list has been provided by Greger V. Teigre, Java Rockx, Klaus Darilion, Zeus Ng, and more.
Simply, this list is too short and incomplete to capture all the generous contributions that came in -- my appologies for everyone else I have missed.
Warnings and Disclaimers
This is a TESTING version. We are encouraging people to give it intense testing and provide us with feedback, so that we can properly assess what it takes to declare it final. The volume and number of changes is big, caution is advised.
All GPL warnings and disclaimers apply.
This is SER, which is not the derivate software known as openser. We have no ideas of in what extent and timeline derivate projects follow (or not) SER.
To Give it a Try
warning: this is just a 'jump-start' for black-belt users. It is not a replacement for documentation or a detailed step-by-step installation guide. It assumes knowledge of operating system, SIP, and SER.
PREPARATION
- make sure mysql is running. In the default configuration, SER assumes it to be running on localhost, if this does not hold, you need to change ser.cfg.
- make sure python is installed (needed for new command-line utilities)
SER INSTALLATION FROM CVS
- Download from CVS/HEAD using instructions at http://www.iptel.org/downloads
- Compile it: make include_modules="mysql xmlrpc" all
- Install it the default way of your administrative privileges allow to: make include_modules="mysql xmlrpc" install
- Download command-line tool (see more documentation under http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=H...)
- cvs co serctl
- Initiate database: ./scripts/mysql/ser_mysql.sh create
START
- Start it. Call: ser
- Begin provisioning users with the new serctl (the capital word are just place holders) # ser_ctl domain add DOMAINNAME # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD # If you want to have Asserted Identity header for your user # - ser_attr add uid=UID asserted_id="PID" # If you want to have gateway support # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ description="The gateway IP for the default ser.cfg" default_flags=33 # - ser_attr add global gw_ip=GATEWAY-IP
- more things you may wish to do:
- familiarize yourself with current ser.cfg
- send us feedback.
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi,
I've just installed new ser on my FC6 desktop. I must say you guys have done unbelievable job down there. Configuration file now looks fantastic!!! Plz, accept my sincere "thank you" to all of you.
Everything's quite understandable, except one: what is $t variable, where does it come from and what is $t.did? I've searched in NEWS, README, README.cfg, but still cant properly get what it means.
Will be eagorously waiting for some more docs.
Regards,
Andrey.
You can find (at least partial) answer here: http://www.iptel.org/attribute_value_pairs_and_selects
You can have attributes (AVPs) with the same name for both caller and callee (like voicemail preference). To distinguish which track you want to check, load etc. you can put track prefix to the name.
$t. or $t?. means TO track (? is one letter CLASS) $f. or $f?. means FROM track
Then there are classes with priority serach, when class is not specified: uRi User Domain Global. The letter in uppercase is the one you use as class prefix. If you want to specify class, you have to specify the track too.
Domain attrs are loaded upon lookup_domain if allowed by modparam. Global attrs are loaded upon ser start if allowed by modparam.
So if ($tu.avp) {...} searches for AVP in TO track USER class only. If you ommit the class, all classes are searched starting with the uri, then user, domain and finally global. So you can have widespread default value (in global class) which is then overriden with avps in user class.
To explain some statements from the ser.cfg: lookup_user("$tu", "@to.uri") stores avp with name uid in the TO track, USER class; you cannot change the name of the attribute here
load_attrs("$tu","$t.uid") will search for avp with uid name in the TO track in all classes (uri, user, domain, global) until first one is found. Then the value is used to load all attributes from user_attrs db table into to TO track USER class.
if ($t.voicemail=="YES") {...} again searches in all classes of TO track.
Note1: the global class is shared between TO and FROM tracks. Note2: from the script you are allowed to change only uri and user classes attributes.
Michal
On Thu, 2006-11-09 at 20:18 +0700, Andrey Kuprianov wrote:
Hi,
I've just installed new ser on my FC6 desktop. I must say you guys have done unbelievable job down there. Configuration file now looks fantastic!!! Plz, accept my sincere "thank you" to all of you.
Everything's quite understandable, except one: what is $t variable, where does it come from and what is $t.did? I've searched in NEWS, README, README.cfg, but still cant properly get what it means.
Will be eagorously waiting for some more docs.
Regards,
Andrey.
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Thanx Michal :-)
On 11/9/06, Michal Matyska michal@iptel.org wrote:
You can find (at least partial) answer here: http://www.iptel.org/attribute_value_pairs_and_selects
You can have attributes (AVPs) with the same name for both caller and callee (like voicemail preference). To distinguish which track you want to check, load etc. you can put track prefix to the name.
$t. or $t?. means TO track (? is one letter CLASS) $f. or $f?. means FROM track
Then there are classes with priority serach, when class is not specified: uRi User Domain Global. The letter in uppercase is the one you use as class prefix. If you want to specify class, you have to specify the track too.
Domain attrs are loaded upon lookup_domain if allowed by modparam. Global attrs are loaded upon ser start if allowed by modparam.
So if ($tu.avp) {...} searches for AVP in TO track USER class only. If you ommit the class, all classes are searched starting with the uri, then user, domain and finally global. So you can have widespread default value (in global class) which is then overriden with avps in user class.
To explain some statements from the ser.cfg: lookup_user("$tu", "@to.uri") stores avp with name uid in the TO track, USER class; you cannot change the name of the attribute here
load_attrs("$tu","$t.uid") will search for avp with uid name in the TO track in all classes (uri, user, domain, global) until first one is found. Then the value is used to load all attributes from user_attrs db table into to TO track USER class.
if ($t.voicemail=="YES") {...} again searches in all classes of TO track.
Note1: the global class is shared between TO and FROM tracks. Note2: from the script you are allowed to change only uri and user classes attributes.
Michal
On Thu, 2006-11-09 at 20:18 +0700, Andrey Kuprianov wrote:
Hi,
I've just installed new ser on my FC6 desktop. I must say you guys have done unbelievable job down there. Configuration file now looks fantastic!!! Plz, accept my sincere "thank you" to all of you.
Everything's quite understandable, except one: what is $t variable, where does it come from and what is $t.did? I've searched in NEWS, README, README.cfg, but still cant properly get what it means.
Will be eagorously waiting for some more docs.
Regards,
Andrey.
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Andrey Kuprianov -
Corey -
Greger V. Teigre -
Jiri Kuthan -
Karel Kozlik -
Michal Matyska