Hi Charles, Thanks for the clarification. I have some (may be very basic) queries:
- What is the basic difference between transaction/request AND calls? - Why sipp is not considering sending of INVITE as a call establishment process? - How does people typically deal with such issue OR is it that I have unique situation here? Thanks for all the help. -Manish Charles P Wright wrote: > There is no way to limit transactions or requests; only calls (either with > -l or -users). If your call has only one concurrent transaction (probably > the only way for SIPp to work correctly); then the number of calls is an > upper bound on transactions. You can disable retransmissions with -nr to > prevent more than one request in the same transaction; but that is not > going to give you an accurate workload. > > If a call fails (i.e. the INVITE is never replied to); then that call is > replaced with a new one that sends register. You can limit the total > number of calls with -m 100. > > Charles > > Manish Sapariya <[EMAIL PROTECTED]> wrote on 09/22/2008 06:16:19 AM: > >> Hi All, >> >> I am trying to create a work load where in I want to have 100 max >> established calls after the system has reached count of 100 calls. >> >> My caller scenario is approximately as follows: >> >> =========== >> Send Register >> Expect proxy auth >> Send Register with auth >> Expect 200 OK >> Send Invite >> Expect Proxy auth >> Send Invite with auth >> expect OK >> play pcap file >> wait for the duration of pcap file >> Send Bye >> Expect OK >> ============= >> >> If my server under test sends the response to both register and Invite >> within time for all 100 requests, everything works just fine. >> >> However, if for some reason, my server fails to send reply to some >> of the invite packets, then sipp keeps on sending register packets >> irrespective of how many total register packet it has sent. In this >> way it keeps bombarding my server with register packets, and server >> fails to send the reply to the invite packet. >> >> I am sure there is a problem with server, however question to the >> list is that, Is it possible to tell sipp that keep at the max >> 100 outstanding register request or invite request. >> >> I tried using -l and -users option. However both of this do not >> take un-acknowledged register and invite request into account. >> >> Please let me know if I need to provide more info or clarification. >> I can share the scenario and the exact command line it that helps. >> >> Thanks and Regards, >> Manish >> >> >> > ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge >> Build the coolest Linux based applications with Moblin SDK & win great > prizes >> Grand prize is a trip for two to an Open Source event anywhere in the > world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Sipp-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/sipp-users > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
