Hello all,

I have some small questions for you:


The first one: I just tested using UDP port 7 (served by inetd) instead
of the built in RTP echo feature. Both apparently do the same thing.

Has anybody some information about the performance difference between
both solutions on a single host, or any other contribution to help
choosing between both options.

I know one advantage of the UDP echo service: you can run it on any
server, without even a login or anything, thus leaving the host with
sipp practically uncharged and available for the signalling work.



And the second one for a more select public (at least the question):

can I still send the diffs for the probabilistic branching (next="x"
chance="0;y") on the 08-11-2006 code or for which version should I make
the diffs?

And more generally, what source code should be used for
corrections/enhancements/additions?

- Any version it was developed/tested on,
- the last stable version (I guess a lot of users start from that one),
- the latest available unstable version (but this has probably changed
before the development is done + tested)?

I also noticed that my little patch for the "fflush(screenf)" was never
integrated: is there some way/procedure (heavy word;-) to send diffs and
get a clear response, being e.g. a) rejected, b) please adapt/continue
working on this with remarks, c) accepted+incorporated in version xxx.


 Best regards,

  MarcVD

(-: from Marc VAN DIEST (BELGACOM ANS/NTA) +32 2 244 5078 ;-)



**** DISCLAIMER ****
http://www.belgacom.be/maildisclaimer
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to