Well I agree that its not an easy task but its achievable. If you are spending a good quality time in understanding open source SIP stacks and writing applications on top of it, you may as well try to figure out how it is designed and developed in that process. At the worst if I may not end up developing a SIP stack but at least I will end up in gaining good knowledge about SIP and its implementation. Yup! It needs to be tested rigorously as is with any software. Once again Thank you all for taking time and responding to my email.
On Thu, May 21, 2009 at 1:01 AM, Maxim Sobolev <[email protected]>wrote: > Paul Kyzivat wrote: > >> >> cool goose wrote: >> >>> Thanks All for pointing me towards some resources. I have never written >>> any >>> protocol stacks before except for few small SIP tools. This would be my >>> first time writing a SIP stack and that's where I felt a need for some >>> literature or books on designing protocol stacks. Anyways, if I run into >>> something I will definitely let you guys now. >>> >> >> With all due respect, unless you are a super-programmer, *and* have a year >> or two to work on it, you ought to be looking for an existing stack to use >> rather than build your own. >> > > As one who wrote SIP stack from scratch I totally agree with Paul. Not only > will you spend lot of time coding it, but also need to put in great deal of > extensive testing with different equipment and software in order to find and > fix all corner cases. 1-2 man-years is a fair estimate. > > Regards, > -- > Maksym Sobolyev > Sippy Software, Inc. > Internet Telephony (VoIP) Experts > T/F: +1-646-651-1110 > Web: http://www.sippysoft.com > MSN: [email protected] > Skype: SippySoft > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
