From SIPp

Ideas / Requests for SIPp

This page is there to list ideas / enhancement requests for SIPp. Please create a Wiki account, log-in and add your ideas below (adding your signature (--~~~~) will help contacting you back for more details. If you are up to it, you can also take one of the idea, indicate that you are working on it on the SIPp users mailing list, and provide your contribution!

Ideas

1. Media
   1. Ability to record 1 out of n RTP stream in wav or mp3 format --Ojacques 05:20, 15 March 2007 (PDT)
   2. Ability to decode RTP audio stream for in band DTMF detection and action --Ojacques 05:20, 15 March 2007 (PDT)
   3. Ability to use true RTP stack (like ortp or pjmedia) to be able to handle more RTP streams --Ojacques 05:20, 15 March 2007 (PDT)
2. SIP Support
   1. While parsing the scenario, SIPp should mark the requests that begin new transactions and assign a branch offset to them, which is carried forward to requests that are part of the same transaction (e.g., INVITE starts a branch, and CANCEL uses it).
3. Misc
   1. Support of clustering testing (sharing of configuration, scenarios, statistics and execution among a cluster) --Ojacques 05:20, 15 March 2007 (PDT)
   2. Ability to forward 1 out of n call to a SIP phone for monitoring purpose (listen only mode) --Ojacques 05:20, 15 March 2007 (PDT)
   3. Possibility to url-encode string variables in order to fill the Replace parameter when doing a transfer. --renaud 11:13, 20 November 2007 (PDT)
   4. Eclipse: creation of SIPp scenarios, run tests and gather results from within Eclipse (TPTP) --Ojacques 05:20, 15 March 2007 (PDT)
   5. Merging the current tree with the Multiscenario-SIPp (SVN-Repository)
   6. The ability to log messages for 1 out of N calls (or possibly even just those calls that failed), so that the message log does not grow huge, but problems can still be diagnosed.
   7. A CSV version of the screen.log, which has all the per-message statistics, but is easy to parse and graph in external programs.
4. Flexibility
   1. Improved default behavior, such that the actual call values (e.g., not "service") are used when generating automatic replies. Also the default behavior should be selectable at a finer-level of granularity (each behavior should have its own flag). Moreover, the scenario should be able to override the default messages.
   2. I'd like SIPp to have support for specify the encoding of pieces of xml scenarios (included in tags). I need to insert, in INVITE messages, encapsulated ISUP messages in order to simulate SIP-T scenarios, but I only have them in HEX encoding. How can I specify that some pieces od code are not in ASCII encoding but in HEX encoding?
5. Ease-of-Use
   1. Personal configuration file support for commonly used options to eliminate the need to specify them on the command line
   2. Integrate and link with a standard XML parser library (such as expat) and with more strict scenario syntax verification (e.g., fail on unknown elements)
   3. Variable and Label Naming (at the scenario file level, internally integers can be used for performance)
   4. Updated screen display that includes the last error and a command-line processor (as in Seagull)