On 24 September 2013 22:01, Dan Knopp <dkn...@imsworkx.com> wrote: > SIPP then proceeds to re transmit the 202 repeatedly until re-transmits have > been exceeded at which point the scenario fails.
You've specified 'retrans="500"' on the 202 Accepted, which is why it's getting retransmitted - setting the "retrans" attribute on a SIP response doesn't make very much sense because there often isn't any way for SIPp to tell that it should stop retransmitting. (Unfortunately, because SIPp doesn't parse the message you give it to send out, it can't distinguish between requests and responses - users just have to be careful. Maybe this is something I could improve by checking the first few characters of the outbound data.) Rob ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
