oSIP is an implementation of SIP.
SIP stands for the Session Initiation Protocol and is described by the rfc3261 (wich deprecates rfc2543). This library aims to provide multimedia and telecom software developers an easy and powerful interface to initiate and control SIP based sessions in their applications. SIP is a open standard replacement from IETF for H323.
antisip is my own company. It was started in january 2005 to provide services around SIP and freesoftware. We offer support, training, bug fixes, help and software. Please, come and visit us!
Both eXosip and partysip has been tested at several SIPit and compliance with most vendors has been verified.
The GNU oSIP library is written in C and get no dependencies except the standard C library. oSIP is thread safe and will generally be used in a multi-threaded application. Nevertheless, this is optional.
oSIP is little in size and code and thus could be use to implement IP soft-phone as well as embedded SIP software. oSIP is not limited to endpoint agents, and can also be used to implement "SIP proxy".
oSIP does not intend to provide a high layer API for controlling "SIP Session" at this step. Instead, it currently provides an API for the SIP message parser, SDP message parser, and library to handle "SIP transactions" as defined by the SIP document.
oSIP CVS is located on savannah: http://savannah.gnu.org/projects/osip/
oSIP can be found on http://ftp.gnu.org/gnu/osip/ or one of the mirrors.
If the above links does not work, new versions of osip can be found there
The new documentation (2.2.0) has been produced with DOXYGEN (7th of September 2004). It contains various "How-to" in the module page which you will find usefull if you are using osip for the first time. There is also some general notes on the main page that describes history and available features of the GNU oSIP stack.
Old documentation is still available in ps and pdf format:
The new one can be rebuilt with the DoxyGen tools.
Latest SIP RFC: http://www.ietf.org/rfc/rfc3261.txt
Reliability of Provisional Responses in the Session Initiation Protocol (SIP: http://www.ietf.org/rfc/rfc3262.txt
Session Initiation Protocol (SIP): Locating SIP Servers http://www.ietf.org/rfc/rfc3263.txt
An Offer/Answer Model with the Session Description Protocol (SDP) http://www.ietf.org/rfc/rfc3264.txt
Session Initiation Protocol (SIP)-Specific Event Notification http://www.ietf.org/rfc/rfc3265.txt
SIP forum: http://www.sipforum.com
IETF's SIP page: http://www.ietf.org/html.charters/sip-charter.html
SIP Working group Supplemental Home Page: http://www.softarmor.com/sipwg/
SIP rfc (deprecated): http://www.ietf.org/rfc/rfc2543.txt
Mailing list archive: http://www.atosc.org/pipermail/public/osip/
You can subscribe to the mailing list with by sending a mail to <firstname.lastname@example.org> with the subject set to "subscribe". Messages can be posted directly to the mailing list to <email@example.com>.
Aymeric MOIZARD <firstname.lastname@example.org>
Antisip (me again) <email@example.com>
Return to GNU's home page.
Please send FSF & GNU inquiries & questions to firstname.lastname@example.org. There are also other ways to contact the FSF.
Please send comments on these web pages to email@example.com, send other questions to firstname.lastname@example.org.
Copyright (C) 2002 Aymeric MOIZARD.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
Updated: $Date: 2005/02/17 15:44:13 $ $Author: aymeric $