oSIP is very readable. Kaiduan, great - it's what I need. Implementation which really fits to RFC. Klaus Darilion wrote that linphone is based on osip. So I will try it first.
Tae-Sam Kim, I have Vovida sources on my hard disk and can upload if You have ftp but it's really huge (about 7MB gzipped). If You want - mail me but I think it's better to start with the other ones pointed us by Andrea, Klaus and Kaiduan. Greetings&thanks Piotr Kaiduan wrote: > Hi, all, > > I have some working knowledge with VOVIDA, oSIP, SER, > KPhone and RTC . The following is my understanding: > > VOVIDA: > A Very very huge library and sip stack, also many > full-blown server, like UA, Marshal server, Redirect > Server, Provision Server, B2BUA, SNMP server. > It doesnot comply with RFC 3261. > > Resiprocate: > > A new sip stack designed by the same guys in VOVIDA, > it fully comply with RFC 3261, but it is just a SIP > stack. > > SER: > > A very fast and small SIP proxy server, using many > special skills. It's SIP stack cannot be used in other > place and other application. > > KPhone's SIP stack: > > Purly based on QT library, no multi-thread support. > > oSIP: > > A great sip stack, very efficient, small footprint, > and very very readable. You can read the sourcecode > and the collate it with the standard. > > On Windows, you can use RTC to design your own client. > RTC is a high level of SIP stack + media stack, very > easy to use and powerful. > > Hope that helps, > > kaiduan _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
