I observed that SIPP sends too few retransmission of the 200 OK response. I used netcat to send a single request, which I traced before, via UDP to sipp running with "-sn uas".
Wireshark and sipp traced and logged only 9 retransmissions. So I tried to modify with -max_invite_retrans or -max_non_invite_retrans. But these parameter does not have any influence. My question is where in the source code can I modify this parameter? And why does sipp out of the box not send the correct number of retransmissions as specified in the RFC ? (sipp send 9 retransmissions for Non-INVITE, whereas RFC3261 introduces 10, the same hold for INVITE transactions, where sipp send 5 retransmission and the RFC requests 6) Thanks for your help! greets -- Marco Happenhofer, Mag. Dipl.-Ing. Institut fuer Breitbandkommunikation Technische Universitaet Wien A-1040 Wien, Favoritenstr. 9-11/388 Tel: +43 1 58801 38833 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
