<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>[Asterisk-Users] VON Update - Pingtel Creates new SIP Open Source Group</TITLE>
</HEAD>
<BODY dir=ltr>
<P><STRONG>cut-n-paste from site: </STRONG></P>
<P>(seems to me like a SIP instance of CLASS Asterisk)</P>
<P><STRONG>Mission</STRONG></P>
<P>The mission of SIPfoundry is to promote and advance SIP-related Open Source
projects. Through SIPfoundry the users, developers, and distributors of SIP
based products can collectively support each other and accelerate the growth and
adoption of SIP. </P>
<P>Open source has already proven its ability to transform the way that other
technologies are developed and the rate at which they can be adopted by end
users. The ability of open source communities to improve the quality and utility
of software surpasses anything that old fashioned business process ever acheived
or ever could. Community development is especially powerful when applied to
broad infrastructure technologies where standards and broad interoperability are
important. </P>
<P>We believe that the time for SIP to come into its own has arrived. The
foundations have been laid for fundamental change in the structure of
telecommunications. We invite you to join us as catalysts in this
transformation. </P>
<P>Organization</P>
<P>SIPfoundry is a non-profit corporation. To quote its <A
href="sipfoundry/bylaws.html" shape="rect">Bylaws</A>: </P>
<BLOCKQUOTE>
<P>It is organized under the Massachusetts Nonprofit Mutual Benefit
Corporation Law for the mutual benefit of the developers, distributors and
customers of open source software products and services. </P></BLOCKQUOTE>
<H3><A name=board shape="rect">Board Of Directors</A></H3>
<P>SIPfoundry will be governed by a Board of Directors drawn from the SIP and
Open Source communities. The role of the board is to foster support for projects
and set overall organization policies. </P>
<H4>Founding Board Nominees</H4>
<UL>
<LI>Bob Andreasen
<LI>Jason Fischl
<LI>Cullen Jennings
<LI>Daniel Petrie
<LI>Robert Sparks
<LI>Martin Steinmann
<LI class=tbd>TBD </LI></UL>
<P>Most business of SIPfoundry should be discussed on the <A
href="http://list.sipfoundry.org/mailman/listinfo/dev" shape="rect">developers
mailing list</A>; for communication just to the board, you may address email to
<board AT sipfoundry DOT org> </P>
<H3>Privacy Policy</H3>
<P>SIPfoundry, Inc. respects and will make every reasonable effort to protect
the privacy of the users of our projects, web site, and any associated services.
See <A href="privacy.html" shape="rect">the SIPfoundry Privacy Policy</A>. </P>
<H1>How you can use SIPFoundry projects</H1>
<P>The specific projects available from SIPfoundry may vary in thier license
terms; you should check the COPYING or LICENSE file in the top level directory
of the distribution for the project(s) you are interested in for the details.
</P>
<P><A href="http://www.opensource.org/docs/definition.php" shape="rect"><IMG
height=95
src="http://www.opensource.org/trademarks/opensource/web/opensource-110x95.png"
width=110 align=right border=0></IMG></A> That having been said, all the
projects available here are <A href="http://www.opensource.org/licenses"
shape="rect">OSI Certified Open Source Software</A>, which means that the
licenses meet the terms of the <A
href="http://www.opensource.org/docs/definition.php" shape="rect">Open Source
Definition</A>. Which means that you can download the source code here, compile
it, and use it. </P>
<P>We are just getting started here at SIPfoundry; there will be some important
and interesting announcements soon about new projects and services available
here. To get those annoucements, please subscribe to our <A
href="http://list.sipfoundry.org/mailman/listinfo/announce"
shape="rect">announce mailing list</A>. </P>
<H1>sipX Family of Projects</H1>
<P>The sipX family of projects were contributed to SIPfoundry by <A
href="http://www.pingtel.com/" shape="rect">Pingtel Corp.</A>. They are now open
source projects available for use by anyone. </P>
<P>All of the sipX projects are distributed under the <A
href="sipfoundry/lgpl.html" shape="rect">LGPL</A>. </P>
<DIV class=AlertBox xmlns=""
xml:base="/home/lawrence/proj/sipfoundry.org/src/html/notyet.xml">
<H2>Source code and binary downloads are coming soon!</H2>
<P>SIPfoundry is dedicated to providing the open source community with the best
initial offering of code possible. To that end, SIPfoundry is working diligently
to prepare source code and tools for distribution. </P>
<P>To be notified when code is available, or to simply learn about activities,
please subscribe to our <A
href="http://list.sipfoundry.org/mailman/listinfo/announce">announce mailing
list</A>. </P></DIV>
<DL>
<DT><A href="sipXphone/" shape="rect">sipXphone</A>
<DD>A SIP soft phone
<DT><A href="sipXproxy/" shape="rect">sipXproxy</A>
<DD>A pair of applications that together form a powerful and highly
configurable SIP router.
<DT><A href="sipXregistry/" shape="rect">sipXregistry</A>
<DD>A SIP Registry/Redirect server.
<DT><A href="sipXpublisher/" shape="rect">sipXpublisher</A>
<DD>A server to handle SIP SUBSCRIBE/NOTIFY handling with a flexible plugin
architecture for different event types.
<DT><A href="sipXvxml/" shape="rect">sipXvxml</A>
<DD>Combines a VXML scripting engine with the sipXtack to support the creation
of IVR and other VXML applications. Includes auto-attendant and voice mail
applications.
<DT><A href="sipXconfig/" shape="rect">sipXconfig</A>
<DD>A SIP configuration server, supporting configuration of all of the above,
and SIP UAs.
<DT><A href="sipXpbx/" shape="rect">sipXpbx</A>
<DD>A full PBX solution; combines sipXproxy, sipXregistry, sipXpublisher,
sipXvxml, and sipXconfig.
<DT><A href="sipXtest/" shape="rect">sipXtest</A>
<DD>SIP testing tools and frameworks. </DD></DL>
<H2>Component Projects</H2>
<P>The projects below each provide one or more components (libraries, scripts,
definitions) that are used by other projects; these are not generally directly
usable other than by developers. </P>
<DL>
<DT><A href="sipXtackLib/" shape="rect">sipXtackLib</A>
<DD>A SIP protocol implementation
<DT><A href="sipXcallLib/" shape="rect">sipXcallLib</A>
<DD>Telephony call control.
<DT><A href="sipXmediaLib/" shape="rect">sipXmediaLib</A>
<DD>Media streaming support (Codecs, RTP, RTCP).
<DT><A href="sipXcommserverLib/" shape="rect">sipXcommserverLib</A>
<DD>Common code shared by sipXproxy, sipXregistry, and sipXpublisher.
<DT><A href="sipXportLib/" shape="rect">sipXportLib</A>
<DD>Common utility and platform abstraction functions (used by all of the
other sipX family projects). </DD></DL>
<H2>Documentation</H2>
<H3>System Level Architectural Views</H3>
<P>The following slides provide some high level views on how the sipX components
work together in a system. </P>
<UL>
<LI><A href="sipX/doc/sys-overview/sys-overview.html" shape="rect">System
Overview</A>
<LI><A href="sipX/doc/sys-scaling/sys-scaling.html" shape="rect">System
Scalability Approach</A> </LI></UL>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>-----Original Message----- <BR><B>From:</B>
asterisk-users-admin@lists.digium.com on behalf of Steven M. Sokol
<BR><B>Sent:</B> Tue 3/30/2004 1:06 AM <BR><B>To:</B>
asterisk-users@lists.digium.com <BR><B>Cc:</B> <BR><B>Subject:</B>
[Asterisk-Users] VON Update - Pingtel Creates new SIP Open Source
Group<BR><BR></DIV></FONT>
<P><FONT size=2>The VON show has started off with a number of interesting
announcements.<BR>First among these is a big announcement from Pingtel that
they have created<BR>a not-for-profit corporation called SIPFoundry.
This new company includes<BR>Pingtel (which has recently open sourced their
SIPExchange PBX), Vovida and<BR>somebody else.<BR><BR>Martin indicated in his
presentation that the key goal of the new group is<BR>to leverage the open
source SIP implementations to prevent legacy vendors<BR>(read Nortel, Avaya,
Siemens, etc.) from using the "Embrace and Extend"<BR>model to co-opt and
proprietize SIP. Pingtel (which makes SIP hardware)<BR>wants to keep the
SIP market open and interoperable.<BR><BR>They have a web site (which I can't
seem to reach from the wireless network<BR>here at the show) for the new
company/project:<BR><BR><A
href="http://www.sipfoundry.org">http://www.sipfoundry.org</A><BR><BR>I spoke
with Martin _____ who gave the Pingtel presentation and is an<BR>officer of
both Pingtel and the new SipForge organization. He indicated he<BR>would
like to speak with Mark regarding the possibility of integrating
the<BR>Asterisk community with the SIP Forge community. He indicated
that Asterisk<BR>was not initially brought into the discussion only due to
limited<BR>time/resources (and to a lesser degree because Asterisk is not
SIP-centric).<BR><BR>Can somebody out there take a look at the SIP Forge site
and let us all know<BR>what the crux of the organization is set to be?
They are having an open<BR>roll-out meeting tomorrow evening which should
spell out some of the goals<BR>of the organization and the
partners.<BR><BR>Above all Martin wanted me to understand that he did not view
the new open<BR>source organization as a competitor to Asterisk. What do
you think?<BR><BR>More on-the-scene reports to
come.<BR><BR>Thanks,<BR><BR>Steve<BR><BR><BR>_______________________________________________<BR>Asterisk-Users
mailing list<BR>Asterisk-Users@lists.digium.com<BR><A
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><BR>To
UNSUBSCRIBE or update options visit:<BR> <A
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><BR></FONT></P></BLOCKQUOTE>
</BODY>
</HTML><table><tr><td bgcolor=#ffffff><font color=#000000><pre>Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.
</pre></font></td></tr></table>