| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
| See inline for my comments. On Jun 16, 2006, at 06.40, Kundan Kumar wrote: hi..... If you examine the code, you will see that reSIProcate is under the VOVIDA license at present. 2) is RTP stack available ?? How is it used ?? 3)is it compatible in Linux kernel 2.6 ?? Yes. And MANY MANY other systems. reSIProcate only needs a subset of a POSIX networking environment and a relatively modern C++ compiler to work. 4)which driver is used ?? I don't know how to answer this, since the question is unclear - please rephrase. 5)plz tell about memory allocation. is it static or dynamic ?? Both. ReSIProcate has a few statics, but uses the heap fairly heavily thanks to the STL. Also, thanks to the STL contract-based design, this behaviour can be overridden by clients either by supplying wholesale replacements for the containers , or instantiating them with their own allocators. 6)also tell about timer/jitter. which one will appropriate for reSIProcate?? Neither - there is no media handling within reSIProcate. You would need to augment reSIProcate with an RTP component if that is what you want to do with reSIProcate. 7)bug reports??? Yes, we have some. The used to be tracked in Jira at sipfoundry.org, but as of late they are on the development mailing list. When the tools at SIP Foundry re-settle, we will likely start using the bug system more extensively. 8)which type of debugger is used??how?? 9)which card is used in reSIProcate stack implementation ?? Again - I do not understand this question. Please elaborate.
I have now replied to u. |