iptel.org - SER

Standard ser.cfg

Wed, 17 Oct 2007 08:44:53 +0200

#
# $Id: seri.cfg,v 1.42 2007/05/30 12:28:17 tirpi Exp $
#

# First start SERi sample config script with:
#   database, accounting, authentication, multi-domain support
#   PSTNi GW section, named flags, named routes, global-,
#   domain- and user-preferences with AVPs
# Several of these features are only here for demonstration purpose
# what can be achieved with the SER config script language.
#
# If you look for a simpler version with a lot less dependencies
# please refer to the ser-basic.cfg file in your SER distribution.

SER 2.0.0 Release Candidate 1

Sat, 12 May 2007 12:54:28 +0200

Release candidate 1 has been thoroughly tested and also used in several commercial production environments. It has thus proven stable.

SERi 2.0 Release Candidate 1 was made available May 12, 2007. A detailed ChangeLog is available, while an overview of news can be found in the NEWS file.

Installation Instructions

You can either compile SER from the sources or install a binary package. Standard SER is fairly easy to compile, so compiling it from sources should be fine. You should have a SER 2.0 up and running in 15-30 minutes by following the procedures below!

Technical Board - Election rules

Sat, 28 Apr 2007 15:13:37 +0200

These election rules were established by consensus on the following mailing lists: serusers@iptel.org,serdev@iptel.org,sems@iptel.org,semsdev@iptel.org.
The basic principles were discussed on the developers' meeting in Prague, April 12.
The principles were put forward on the lists, discussed, and modified with a summary posted to the lists for approval on April 28 by Greger V. Teigre.
This page documents the agreed rules and was edited by Greger V. Teigre on May 17, adding semsdev@iptel.org as a voting list.
Any modifications to these rules agreed by the community should be documented here with a history.
May 18, 2007, GVT, updated #6, made explicit nomination/voting procedure by adding "(by posting to at least one of the lists)."
May 29, 2007, GVT, reversed May 18 addition, and added items 9 to 13 suggested in GVT post on May 25 to make explicit nomination and voting procedures, including an option for secret voting (no comments were received on the suggesting, thus accepted by the community)

Finally making SER accessible to newcomers, while keeping the strength of its configuration language!

Tue, 24 Apr 2007 18:26:31 +0200

One big problem with SERi has been the complexity of the SER configuration language. Only apache (httpd) can (almost) compare in the flexibility and number of ways a piece of software can be configured. This has resulted in a pretty steep learning curve for beginners. SIP can be used for an increasing number of applications and each deployment has its own, specific needs. Thus, SER's configuration language must be powerful.

The professional SER user has other issues, like maintaining multiple configurations across server farms and setups, sharing some code, but still needing individual tailoring to each server. '

Documentation search

Wed, 18 Apr 2007 11:26:27 +0200

PLEASE wait until the data loads, then change the header fields to update the table's content.

F: R: P: S: ?

Insufficient documentation ?


{dsRecords::module}	{dsRecords::version}	{dsRecords::type_name}	{dsRecords::name}	Report

Materials from SER/SEMS meeting in Prague available online.

Sun, 25 Mar 2007 19:05:01 +0200

Slides, audio streams, and pictures from the SERi/SEMSi meeting in Prague are now available online on our FTP server.

SER Prague User Group Meeting Notes

Thu, 22 Mar 2007 08:20:43 +0100

SERi USER GROUP MINUTES AND PRESENTATIONS, March 19th 2007, Prague

These are tentative meeting notes. If you participated, feel free to edit and add things you think should be covered.

(PDF) Jiri Kuthan opened up with his view of SER status. The status update concentrated on the newly coined SLAMP ecosystem (SIP/SER/SEMSi+LAMP) and the motivation for the recent major Ottendorf release. The SLAMP system has been defined as environment for rapid innovation of open communication services using LAMP (Linux+Apache+Mysql+Python/perl) enhanced by SIP-based real communication.

SER User Group Meeting

Wed, 31 Jan 2007 13:21:18 +0100

On March 19th, the first SERi User Group Meeting took place, colocated with the IETF meeting. The purpose of this meeting was facilitation of most direct contact among SER users and developers, and discussion of SER roadmap.

A SysOp's Perspective on SER's flexibility

Wed, 31 Jan 2007 09:43:56 +0100

This snippet was cut from the developer's mailing list during a discussion on seri.cfg, SERi's pride and most beginners' challenge... It will give you an insight into what SER is and isn't, and whether it might be for you :-)

Consider a more simple SIP proxy like repro. All you can do there is start the damn thing and give it the user data (what would be
subscribers, aliases, and parts of the usr_preferences in SER 0.9). Sounds all nice and simple.

Now, as an VoIPi operator, my world will be a little bit more complicated. I may have different services that run on separate proxy farms. I may

Daily snapshots of software

Wed, 13 Dec 2006 23:24:30 +0100

Daily generated snapshots of SERi, SERwebi, SERctli, and RTPproxyi are now available on the FTP server. New tarballs are generated every day, but only if there were changes since the last tarball (because generating tarballs that would be same is waste of space).

Daily snapshots of SER are in http://ftp.iptel.org/pub/ser/daily-snapshots
Daily snapshots of SERctl are in http://ftp.iptel.org/pub/serctl/daily-snapshots
Daily snapshots of SERweb are in http://ftp.iptel.org/pub/serweb/daily-snapshots
Daily snapshots of RTPproxy are in http://ftp.iptel.org/pub/rtpproxy/daily-snapshots

Full module documentation for SER Ottendorf in commentable format!!

Sun, 26 Nov 2006 11:48:09 +0100

SERi Ottendorf module documentation is now available at iptel.org. The auto-generated module documentation (nightly from latest SER Ottendorf documentation sources) is commentable. We encourage everybody to add comments and experiences to the module documentation!

SER Ottendorf module documenation is not complete yet. There may miss documentation of functions and parameters and some modules are yet to be made available online. We are working on this, but again, we encourage you to comment in order to complete and improve the documentation.

SER Database Migration Tool

Fri, 17 Nov 2006 01:09:38 +0100

New migration tool for SER database is available. The tool can convert the database schema from SERi version 0.9.x into the new schema used in release 0.10.x and further.

New major SER pre-release, Ottendorf, is out for testing

Tue, 07 Nov 2006 15:17:00 +0100

Ladies and gentlemen, girls and boys,

the new testing pre-release of the best SIP proxy server ever, SERi, is out!

About the release

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 IETFi 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, branchi)
applications: presence has been greatly updated to keep pace with development in the IETF/SIMPLEi (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 seri_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, SEMSi and SERWEBi have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVRi-scripting and B2BUAi, 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.

Documentation effort for SER 0.10.x started!!!

Thu, 07 Sep 2006 22:02:51 +0200

We have started documenting 0.10.x and need your help!! http://www.iptel.org/ser/doc/010whatsnew will be home for documentation of changes from 0.9.x to 0.10.x. The format is a set of pages that form a book. Together, the book will become the Migration guide for 0.10.x.

If you have started using SERi 0.10.x from CVSi or the presence snapshot, we need your help! Document the changes and how to use new features, so that other users can "stand on your shoulders"... ;-)

Either edit an existing book page or go to Create content, choose 'book' and make sure that the parent page is either 'SER 0.10.x What's new?' or 'Changes in modules', depending on whether you are documenting some basic/core functionality or modules. When creating the book page, select 0.10.x as the SER version (from the list of versions), and from the list of SER components, select the relevant components for what you document.

Get Started With SER

Sun, 13 Aug 2006 10:38:08 +0200

Is SERi for me?!

This is a difficult question. People come to iptel.org with many different goals. Basically, SER is a highly scalable SIP server (redirect, proxy, and registrar). It is not a telephony PBXi, and it is not a simple "run SIP proxy" applications. You need to understand SIP, tailor SER to your needs using the seri.cfg configuration file, and tweak to your network, your user devices, gateways etc. That being said, the flexibiilty of how much you can tweak is quite unique. (Btw, SER does come with example config files that gives you a basic working setup in very short time.)