savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] savannah.gnu.org: submission of The GNU oSIP library


From: jack
Subject: [Savannah-hackers] savannah.gnu.org: submission of The GNU oSIP library
Date: Fri, 25 Jan 2002 08:44:35 -0500

A package was submitted to savannah.gnu.org.
This mail was sent to address@hidden, address@hidden


Moizard <address@hidden> described the package as follows:
License: lgpl
Other License: 
Package: The GNU oSIP library
System name: osip
This package wants to apply for inclusion in the GNU project

oSIP is an LGPL implementation of SIP, the Session Initiation Protocol, written 
in C language. oSIP is a low level SIP stack which aims to provide multimedia 
and telecom software developers an easy and powerful interface to initiate and 
control SIP based sessions in their applications.  oSIP only depends on the C 
library and should be ANSI compliant (optionnaly, there are dependancies on the 
pthread library to ease developpements of multi-threaded SIP software. Linux is 
the kernel used for developpements, but it is also maintained on Windows. oSIP 
is also knows to compile on a various flavor of unix but each version is not 
tested on those operating sytems.

SIP is not only a signalling protocol for VoIP, but also for any multimedia 
sesions. SIP is the protocol choosed by the third generation (3G) network. It 
has very nice nearly defined extensions for presence managements and instant 
messaging as they will be part of the next generation architectures and 
services provided by future operators. As an example, the next release of UMTS 
(rel5) which should be out by march uses SIP as the signalling protocol. Also, 
SIP is a light and full featured replacement for H323 (signalling part) that 
perfectly fits embeded devices. 

SIP is a HTTP and MAIL like protocol. To make a phone call, you\'ll get the 
same interface than with emails. You\'ll find in SIP messages the usual 
following headers:

From: sip:address@hidden
To: sip:address@hidden
Subject: Let\'s have a phone call about oSIP.

SIP messages are routed in the network via SIP proxy server. Those SIP servers 
(attached to a domain) receive registrations for their users and are able to 
root calls towards the current callees\' location. This enable terminal 
mobility as well as personnal mobility. Media are negociated by endpoints 
allowing audio, video, whiteboard sharing and any mutlimedia sessions to be used
depending on the codec supported by both endpoints.

It already exists and you can see it at http://osip.atosc.org
oSIP is already considered stable since 0.7.1 and is nearly
fully compliant with a very few exceptions.

The library is used by linphone (GPL) http://www.linphone.org/ which CVS is 
located on the non-gnu side of savannah. linphone is a SIP softphone.

I\'m also building a redirect server called osrd (GPL). The goal of this 
project is to provide personnal mobility. The CVS is also located on the 
non-gnu side of savannah. Next step will provide presence facilities compliant 
with the UMTS release 5 and Latest Windows Messenger on XP which is now SIP 
based. oSIP will help to build clients wich will interoperate with microsoft 
new generation products as they have already choosed SIP.

We are now needing a proxy server with NAT capabilites allowing a large 
deployement of the SIP technology. Actually no freesoftware can provide that. 
This will be the next step.

As oSIP is LGPL, most oSIP users comes from the industry and are developping 
proprietary applications. oSIP is highly used by R&D labs to evaluate the SIP 
capabilities and test their existing applications. Contributions mainly comes 
from this industry. (the mailing list includes
76 guys).

The stack has been evaluated by David Sugar and the last issue was to get a 
copyright disclaimer from my employer. I have received it yesterday and I\'m 
ready to send it to the fsf. Let me know where to send it.

Thanks

I just recei





reply via email to

[Prev in Thread] Current Thread [Next in Thread]