-
Notifications
You must be signed in to change notification settings - Fork 0
/
about.htm
136 lines (91 loc) · 13.2 KB
/
about.htm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<title>About PJSIP</title>
<link rel="stylesheet" href="style/style3.css">
</head>
<body class="std">
<!--#include file="header.htm" -->
<!--#include file="leftnav.htm" -->
<div class="main">
<div class="content">
<h2>About PJSIP</h2>
<!--
<table border="0">
<tr>
<td><a class="fancy" href="#what">What is PJSIP</a></td>
<td> </td>
<td><a class="fancy" href="#who">Who is PJSIP</a></td>
<td> </td>
<td><a class="fancy" href="#why">Why PJSIP</a></td>
<td> </td>
<td><a class="fancy" href="#history">History of PJSIP</a></td>
</tr>
</table>
<p> </p>
-->
<a name="what"></a>
<h3>What is PJSIP</h3>
<p>PJSIP is a free and Open Source multimedia communication library implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. It combines signaling protocol (SIP) with multimedia framework and NAT traversal functionality into high level multimedia communication API that is portable and suitable for almost any type of systems ranging from desktops, embedded systems, to mobile handsets.</p>
<p>See complete list of PJSIP features in <a href="http://trac.pjsip.org/repos/wiki/PJSIP-Datasheet">PJSIP Datasheet <IMG SRC="images/extlink.gif" /></a>.</p>
<p> </p>
<A name="who"></a>
<h3>Who is PJSIP</h3>
<p>PJSIP is developed and maintained by <a href="http://www.teluu.com">Teluu Ltd. <IMG SRC="images/extlink.gif"/></a>, with the help of Internet developers around the world. Teluu was incorporated in late 2006 in the UK initially as PJSIP LLP by Benny Prijono and Perry Ismangil, and soon joined by Nanang Izzuddin, and then Sauw Ming as developers. Our newest team member is Riza Sulistyo.</p>
<p>All of us do everything from writing the documentation, wiki, and creating this website, updating the blog and Trac site, to accounting, answering support, and responding to mailing list questions. We do write code too.</p>
<p> </p>
<A name="why"></a>
<h3>Why PJSIP</h3>
<a name="comprehensive"></a>
<h4>Complete and Integrated</h4>
<p>PJSIP attempts to provide you, the developer, with everything you need to build real-time multimedia communication application. All three main components of real-time multimedia application, i.e. signaling, media features, and NAT traversal, have been taken care of by PJSIP. Leave those to us and you can concentrate on the application logic.</p>
<p>See complete list of PJSIP features in <a href="http://trac.pjsip.org/repos/wiki/PJSIP-Datasheet">PJSIP Datasheet <IMG SRC="images/extlink.gif"/></a>.</p>
<a name="portable"></a>
<h4>Very Portable</h4>
<p>Write your application once, and it will run on any flavor of <a href="http://trac.pjsip.org/repos/wiki/Getting-Started">Windows</a>, <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/Windows-Mobile">Windows Mobile/CE</a> up to WM 6, <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/Autoconf">Mac OS X</a> both PPC and Intel, <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/Autoconf">Linux</a> on any processor types, many flavor of Unix systems, <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/Symbian">Nokia/Symbian</a> 3rd and 5th Edition devices, <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/iPhone">Apple iOS</a> on iPhone, iPad, and iPod, BlackBerry 10, and <a href="http://trac.pjsip.org/repos/wiki/Getting-Started/Android">Android</a> (planned in v2.2). </p>
<p>PJSIP has also been used in embedded systems, with people reported successful use on embedded OS/RTOS such as uC-Linux, QNX, and RTEMS across different type of processors. PJSIP runs on a 20Mhz MIPS processor appliance.</p>
<a name="compact"></a>
<h4>Compact, Small Footprint</h4>
<p>A voice call application starts from as little as 150KB using the lower level libraries, or few hundred KB using the higher level PJSUA-LIB API, which take heap usage from couple of hundred KB for two calls. Footprint will of course vary with the features that are used, but hopefully this gives a broad indication.</p>
<p>For more information about PJSIP footprint, see the <a href="http://trac.pjsip.org/repos/wiki/FAQ#Footprint">footprint discussion in our FAQ <IMG SRC="images/extlink.gif" /></a>.</p>
<a name="documentation"></a>
<h4>Good Documentation</h4>
<p>We also make significant effort to write documentation. On top of the reference documentation of the API, we've written many articles on the (Trac) wiki site to help your development. All PJSIP documentation is indexed in <a href="http://trac.pjsip.org/repos">the Trac site <IMG SRC="images/extlink.gif"/></a>.</p>
<h4>Maturing</h4>
<p>We are not the first, but we've been around for some time. The software has seen a lot of real-life problems and many tricks have been implemented to make things work. Experience counts.</p>
<a name="opensource"></a>
<h4>Professional Open Source</h4>
<p>Last but not least, PJSIP is Open Source Software (OSS). Well it's actually dual-licensed. Being Open Source has enabled PJSIP to be used by thousand of developers around the world, and probably scrutinized by that many too. Finding PJSIP developer is getting easier, and as Open Source Software, PJSIP code will never disappear, even when we are gone. </p>
<p>On the other hand, we're also offering proprietary license that is bundled with support for those who can't open source their products or who want to get service directly from the developers of PJSIP. We believe this model is a win-win-win solution for everyone; businesses get professional product they're looking for, we survive to continue the development of pjsip, which in turn will be presented back as OSS to the community.</p>
<p>Regardless of licensing, we have a completely open development model. We only have one source tree. You can see our development plan and progress in <a href="http://trac.pjsip.org/repos">our Trac site <IMG SRC="images/extlink.gif"/></a>.</p>
<p>Learn more about our <a href="licensing.htm">Licensing here</a>.</p>
<p> </p>
<A name="history"></a>
<h3>History of PJSIP</h3>
<h4>The First Releases</h4>
<p>The first public release of PJSIP is on Feb 2005 as <a href="/release/0.2.0">version 0.2</a>. The .tar.gz file is 239 KB, which is tiny compared to 6.5 MB of version 2.0, but it is already a fully functional SIP, SDP, and media library to make a working voice call, and it is portable as it runs on Windows and Linux platforms. Indeed these are the principles that we try to hold in PJSIP: complete, integrated, small footprint, and portable. And good documentation too, as we already had online Doxygen documentation by this time.</p>
<p>The first version was released as 0.2 because actually the library was started long before that. PJSIP was created by Benny Prijono, me, and in case anyone ask (and some have), the "PJ" abbreviation comes from my surname. The very first component of PJSIP is the parser, which was created to participate in internal parser contest in <a href="http://www.switchlab.com/">Switchlab, Ltd.</a>, the company that I worked for, in August 2002. By 2003, PJSIP looked to be mature enough to be used in a production hardware IP phone developed by my company (see below), to replace the old, RFC 2543 compliant, in house SIP stack that was used by the product, which I also wrote. So that was PJSIP version 0.1.</p>
<p align="center">
<img src="images/vectone_genie.png" alt="vectone genie"/><BR>
<font size="-1">Vectone Genie, first PJSIP product [circa 2003]. Image courtessy of <a href="http://www.vectone.com/">Vectone Ltd.</a></font>
</p>
<p>Since it's first public release, nine releases were made in the space of four months: <a href="/release/0.2.1">0.2.1</a>, <a href="/release/0.2.5">0.2.5</a>, and so on up to <a href="/release/0.2.9.2">0.2.9.2</a> in June 2005, featuring registration, instant messaging, and presence (SIP SIMPLE). But then it hit a wall. As new SIP RFCs were studied, it was found that PJSIP design was not up to speed with the latest development of SIP (remember that PJSIP was started about the same time RFC 3261 was released). One thing that was clearly missing in PJSIP was the concept of dialog usage, where one dialog may be shared by more than one sessions. So it was decided to go back to the drawing board.</p>
<h4>Starting It with Version 0.5</h4>
<p>It was actually like that. Before any new code was written, a "PJSIP Design" document was written, and this is what then became the good old <a href="/release/0.5.4/PJSIP-Dev-Guide.pdf">PJSIP Developer's Guide (PDF)</a> book. Around this time, I also decided to take my opportunity to work full time for PJSIP. The development took significant time, in fact it was only eight months later in Feb 2006 that the new version was released. That version was called <a href="/release/0.5.0">0.5.0</a>, skipping 0.3 and 0.4 altogether due to major features in the new version.</p>
<p>After 0.5, new releases followed quickly, and there were fourteen releases in the following twelve months. Being "version shy", all were numbered "0.5", so a year later the version number only went as high as <a href="/release/0.5.10">0.5.10</a>. During this period, PJSIP LLP was incorporated in Nov 2006, along with Perry Ismangil, a former classmate in college. With Perry on board, things were getting more organized. For example, we started to use Trac, since <a href="http://trac.pjsip.org/repos/milestone/release-0.5.9">0.5.9</a>. He started the <a href="http://blog.pjsip.org">PJSIP Blog</a>. And we attended several conferences, to bring more exposure to PJSIP.</p>
<h4>Symbian and PJNATH</h4>
<p>The next major release was version <a href="http://trac.pjsip.org/repos/milestone/release-0.7.0">0.7.0</a>, released in June 2007. Two major features in this release were <a href="http://blog.pjsip.org/2007/05/04/open-source-sip-stack-media-stun-and-ice-for-symbian-os/">Symbian support</a> and the introduction of a new library, PJNATH. PJNATH stands for PJ NAT Helper, and it contains our implementation of STUN, TURN, and ICE. It's <a href="http://blog.pjsip.org/2007/04/06/introducing-pjnath-open-source-ice-stun-and-turn/">the first Open Source ICE library in the world</a>, and it's now an integral part of PJSIP communication suite. We're quite pleased to have that.</p>
<p>The Open Source community seemed to be receiving PJSIP quite well too, <a href="http://trac.pjsip.org/repos/wiki/Projects_Using_PJSIP">many wonderful projects <IMG SRC="images/extlink.gif" /></a> that use pjsip were sprouting into existance. Among the notable pioneers is Samuel Vinson who ported PJSIP to Nintendo DS in <a href="http://svsip.free.fr/spip.php?rubrique9">SvSIP project</a> as early as in Sep 2007 and gained quite <a href="http://blog.pjsip.org/2007/09/15/making-voip-on-nintendo-ds-a-reality-new-open-source-sip-client-available/">some coverage</a> from the press, <a href="http://blog.pjsip.org/2008/01/01/you-can-now-make-phone-calls-from-your-ipod-touch/">iPod touch port</a> in Dec 2007, and then to <a href="http://blog.pjsip.org/2009/02/19/native-iphone-sip-client-based-on-pjsip-available-on-app-store-open-source-and-not-tied-to-any-provider/">iPhone</a> with his <a href="http://code.google.com/p/siphon/">Siphon project</a> in Feb 2009, which makes it the world's first free SIP/VoIP application for iPhone and iPod Touch 1 and 2. We're glad to be part of it.</p>
<p>Nanang Izzuddin joined the development team in early 2008. He brought along Symbian experience and will become Windows and Symbian maintainer in the team.</p>
<h4>Version 1.0</h4>
<p>The next major milestone was <a href="http://trac.pjsip.org/repos/milestone/release-1.0">version 1.0</a>, which was released more than a year later on Oct 2008. Although many features were implemented, along the way in <a href="http://trac.pjsip.org/repos/milestone/release-0.8.0">version 0.8</a> and <a href="http://trac.pjsip.org/repos/milestone/release-0.9.0">0.9</a> too, this version was more of a psychological barrier rather than technical one, as I previously felt that there's got to be something grand and trustworthy for something to be released as 1.0. But we got over that..</p>
<p>Fast forward to 2010, Sauw Ming joined PJSIP team in Dec 2009, he then single-handedly tackled the iPhone port, something that we've always wanted to do and which the community has done it years before.</p>
<h4>Version 2.0 and Beyond</h4>
<p>Fast forward to today, 22 May 2012, we just released a major milestone, <a href="http://trac.pjsip.org/repos/milestone/release-2.0">PJSIP version 2.0</a> (yay!). And a new website as well. The major feature being introduced is video, and it took us almost two years to develop this, and we can only hope that the community will receive it warmly.</p>
<p>And that's all we can hope for, for the future. But rest assured that we're not complacent with what we have now. In the future, we want PJSIP to be available to even more platforms. More mobile friendly and fine-tuned for it. We're not happy with the current high level API and we want it to be even higher level and easier to use and develop. We want the API to be accessible to even more languages. We're not happy with the documentation. We need more features, more RFCs. And so on. Only time will tell if and how we will achieve these.</p>
</div>
</div> <!-- #main -->
<!--#include file="footer.htm" -->
</body>
</html>