|
|
|
|
|
|
|
|
|
Frequently Asked Questions about SIP 2. Where can I learn more about SIP?
1. What is the size of the executable User Agent? 2. Are threads required? How many threads are needed? How many threads per transaction/call? 3. How many SIP messages can be handled per second? 4. How much memory is allocated on per call basis?
Answers
1. What is SIP? Sip (Session Initiation Protocol) is a Client Server protocol modeled after HTTP and described in RFC 3261. 2. Where can I learn more about SIP? The SIP web page at the Columbia University is a good place to start learning about SIP. It offers SIP tutorial, latest news and links to many other SIP related web pages. SIP is an evolving protocol and the work on its standardization is ongoing at two working groups at IETF: SIP working Group and SIPPING (Session Initialization Proposal Investigation). 1. What is the size of the executable User Agent? The size of the executable varies a lot with the compiler, the optimization, inclusion of optional debug information etc. It is not possible to give a single number that would describe the memory footprint. Please contact us at support@tntss.com and tell us what compiler you are using so that we can give you some example of SIP UA memory utilization. 2. Are threads required? How many threads are needed? How many threads per transaction/call? The thread pool size is compile time configurable and can vary from 1 (minimum required, of course) to whatever a system can handle. More threads mean more messages may be handled concurrently. One thread mean that each message runs to completion before the next one can be picked from the queue. 3. How many SIP messages can be handled per second? Again, this number depends too deeply on the processor speed and other factors beyond the control of the SIP stack. It may also depend on SIP stack configuration (e.g. the number of threads that the SIP stack is allowed to use, etc). Please contact us (support@tntss.com) for the performance numbers that you may expect for your particular configuration. |
|
|
||||||||||||
Copyright 2002-2006 TNT Systems Inc. |