iptel.org - Site, General, Development

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.

iptel.org technical board elected

Wed, 13 Jun 2007 21:11:45 +0200

iptel.org has now an elected technical board. The election was held on the serusers, serdev, and semsdev mailing lists. The term is from now until May 31, 2009. The board will govern on issues where consensus cannot be reached or where consensus is unsuitable.

Nominations and Voting - Technical Board 2007

Tue, 22 May 2007 07:59:05 +0200

Technical Board 2007-2009

The members of the technical board for the term starting June 15, 2007 and ending May 31, 2009 are: Jan Janak, Andrei Pelinescu-Onciul, Greger Viken Teigre, Stefan Sayer, and Martin Hoffmann.

These were the nominations for the mid-2007 technical board election (in the order of received nominations). Nominees who accepted the nomination are listed with "accepted".

The number of votes received is listed in paranthesis.

Raphael Coeffic (SEMSi), accepted, (7 votes)
Stefan Sayer (SEMS), accepted, (8 votes)
Jan Janak, accepted, (13 votes)
Andrei Pelinescu-Onciul, accepted, (13 votes)
N.

SIP Looking Glass

Mon, 14 May 2007 13:07:33 +0200

Thanks to a sponsor, iptel.org SIP services have been enhanced by a "SIP Looking Glass" feature. Looking glass, like in the IP world, allows observers to watch characteristics of traffic in a particular domain. The equipment provided courtesy of iptego features, among others, comprehensible statistics of SIP user agents using the iptel.org site. Warning: the equipment is still in BETA stage.

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. '

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.

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

New artwork

Mon, 27 Nov 2006 02:51:12 +0100

Update version of all logos (SERi, SEMSi, SERWebi) is available at http://www.iptel.org/artwork. The new graphics includes http://iptel.org as the URL for the software (instead of the old http://sip-router.org) and also the text in the images looks better now.

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.

Bug tracker update

Tue, 21 Nov 2006 12:44:52 +0100

The bug tracker at iptel.org projects was updated yesterday. We are now running Jira 3.6.5 which will be hopefully more stable than the previous version. We are using the bug tracker to track bugs in SERi, SERWebi, serctli, and SEMSi projects. You can find the bug tracker at http://tracker.iptel.org

Overview of iptel.org Drupal System

Fri, 01 Sep 2006 00:45:03 +0200

Have you wondered how does the iptel.org site powered by Drupal work ? What is behind the scenes and how are pages stored in the system and rendered to the user ? Don't panic ! Rather check this new page which describes it all.

Certificate Authority

Thu, 31 Aug 2006 14:28:09 +0200

There is a new page describing how to apply for a certificate from iptel.org certificate authority. Our certificate authority is used to secure the pages on the web server and in the future it will be also used to secure the SIP service we are running. Anyone can apply for a client certificate which can be later imported into the SIP user agent. You can also download the certificate of the CA from that page.

New iptel.org site!

Wed, 16 Aug 2006 09:21:59 +0200

The new http://iptel.org/, home of SERi, SEMSi, and SERWebi is now up. If you have an account from ONsip.org, you can log in using your old ONsip.org username/password. However, all content is available without registration.

The new site is supported by the joint efforts of the iptel.org and ONsip.org teams. Our aim is to dramatically improve the project communication, documentation, and development process. The start is already up there, and we have many plans. The best thing of all: The new http://iptel.org site is a great basis for contributions from anyone.

We are working on migrating and organizing the remaining content from the old site, but meanwhile you can access everything from the old site from http://dog.iptel.org/

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.)