About SIPfoundry

Website : http://www.sipfoundry.org/

WiKi : http://sipx-wiki.calivia.com/

SIPfoundry, a non-profit organisation, exists to promote and advance SIP-related Open Source projects. Through SIPfoundry users, developers, and distributors of SIP based products can utilise open-source materials to accelerate the growth and adoption of SIP.

Founded in February 2004, SIPfoundry established close ties with the SIP Forum as well as the IETF.

The SIPfoundry developer and user communities have rapidly expanded to include participants from 63 countries and counting. SIP is hot, so whether you are a user or developer, get involved and consider SIPfoundry as the place where you find or develop your SIP capabilities.

SIPfoundry Projects

1. The sipX Project

The sipX project aim is to develop a feature rich and standards compliant SIP communications infrastructure for Enterprise use in a community organized open source effort.

sipX consists of a modular architecture based around the following building blocks:

• sipX Communications Server
• sipX Media Server
• sipX Configuration Server
• While sipX packages these components to function as a SIP PBX, each server can also be used standalone.

2. The sipXphone, sipXezPhone, and sipXtapi UA SDK project

SIPfoundry provides a very comprehensive set of technologies for the development of SIP user agents supporting SIP voice communications, presence and instant messaging.

sipXphone, formerly known as Pingtel's instant xpressa soft phone, is a fully functional SIP soft phone that runs on Microsoft Windows and Linux. The Pingtel's xpressa phone (no longer a Pingtel product) is based on this same source base.

The SIP soft phone leverages a well tested RFC 3261 compliant SIP stack
(sipXportLib), and boasts rich configuration abilities, a java-based application framework / development kit, and a wide range of features (Message Waiting Indication to on-phone bridged conferences). The sipXphone project includes the Java Application Layer, C++ embedded web server, and a C/C++ JNI API. The rest of the code is separated into reusable component libraries.

3. The reSIProcate Project

The reciprocate project is developing an object oriented SIP stack written in C++ and intended to serve as the SIP reference implementation. Developed by many of the same people who participate in the IETF’s standardization effort of SIP, the reSIProcate stack is fully standards compliant, feature complete, and often serves as a test environment for new initiatives such as the most recent IETF draft proposals for SIP security.

The reSIProcate stack is used in an increasing number of commercial products by companies such as TelTel, Jasomi and Xten. Its design objective is to create a well documented and easy to use SIP stack for use in phones, gateways, SIP proxies, back-to-back user agents as well as instant messaging and presence applications.

4. The SIP Forum Test Framework (SFTF) Project

Interoperability of SIP products and SIP-based technologies is key to achieving SIPfoundry's objectives. The scope of SIPfoundry's initiatives to encourage and promote interoperability of SIP products and SIP-based technologies include the following:

• Establishment of a test framework (SFTF)
• Active participation in SIP based IETF standards development
• Involvement in forums (SIP Forum)
• Promotion of SIP testing interoperability events (SIPIT and SIMPLEt).

5. The Open Settlement Protocol (OSP) Client Toolkit Project

The OSP client Toolkit is a complete development kit for software developers who want to implement the client side of the European Telecommunication Standards Institute's Open Settlement Protocol (ETSI TS 101321). The OSP client Toolkit includes source code written in ANSI C, test tools and extensive documentation on how to implement OSP. A hosted OSP test server is freely available on the Internet for all developers to test their OSP implementation.

OSP is an Operational Support System (OSS) protocol well suited for managing inter-domain routing, access control and accounting of SIP transactions. OSP uses the communications protocols below to convey messages. The content of an OSP transaction is an HTTP message formatted according to the standard for MIME. Individual components in the message are XML documents and the message may be signed with an S/MIME digital signature.

5. The Message Session Relay Protocol (MSRP) Project

This project is still in an early phase of development and aims to create a reference implementation of an MSRP stack. We are currently targeting the most recent drafts of the base specification and the relay extensions. The current plan is to create a beta-quality stack suitable for use in a client, and then add relay functionality (for both clients and relays) after the basic functionality is in place. Work is done in close cooperation with the IETF and the MSRP implementation will serve as a first reference implementation.

Goals of this project include:

• Validation of the implementability of the existing IETF specifications for MSRP.
• Creation of a freely available stack against which others can test their implementation.
• Creation of a stack that can be integrated into both opensource and proprietary products to add MSRP functionality.