Consider the following scenario : SIPp ----------SUBSCRIBE-----------> SUT SIPp <---------200------------------ SUT SIPp <---------NOTIFY--------------- SUT SIPp ------------200---------------> SUT
This fails at step 2 where SIPP receives a 403 instead of a 200. That's not the problem. The problem is that SIPp sends a BYE to the SUT which then sends a 480 (a distraction from the original intent). Consider this case: SIPp ---------- MESSAGE -----------> SUT SIPp <--------- 200 --------------- SUT SIPp <--------- MESSAGE ------------ SUT SIPp ---------- 200 --------------> SUT In load testing this, the SUT gets overloaded and does not respond in time sometimes. Here again, SIPp takes it upon itself to send a BYE. The SUT which is already overloaded, then replies with a 405 because it doesn't understand what a BYE is. The BYE is NOT specified in my xml file. Why does SIPp assume it knows better than the xml file ? Can I turn off this automatic BYE behavior and just mark that as a failed call. Thanks, -Vinit ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
