On Thu, Aug 25, 2011 at 1:09 AM, Doug Beach <[email protected]> wrote:
> takeshi,
>
> Thank you, between what you had said and talking to my coworkers today, I
> was able to figure out my error.
>
> I have another question. I was looking here:
> http://sipp.sourceforge.net/doc/reference.html#Structure+of+client+%28UAC+like%29+XML+scenarios,
> at the keyword list, specifically at the [remote_port] keyword. I am
> confused with the description, I can pass in the Remote IP port on the
> command line OR add an offset [remote_port+3]. The offset part is in the
> code correct?
>
I actually never used this combination of remote_port+offset. But yes, the
offset is set in the scenario file.
> The offset isn't entered at the command line, right?
>
Correct.
> The tester just types in what remote port to communicate with just like how
> the Remote IP address is entered.
>
>
> this the remote IP address
> | this is the remote port
> | | local IP
> | | |
> local port
> | |
> | |
> sipp -sf test.xml 10.0.47.34 5061 -i 10.0.47.40 -p 5060
>
> Correct?
>
Not quite. The naming is right but you must put a colon between remote_ip
and remote_port.
> Just type in the remote IP and remote port? There are no options I need to
> include?
>
The first lines of "sipp -h" shows this:
Usage:
sipp remote_host[:remote_port] [options]
So you should call it like this:
sipp -sf test.xml 10.0.47.34:5061 -i 10.0.47.40 -p 5060
Obs: however I usually put all options before the required parameters, like
this:
sipp -sf test.xml -i 10.0.47.40 -p 5060 10.0.47.34:5061
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
